Where to observe application deployed by Jenkins? - maven

Question from a first-time Jenkins user. So I hope you wouldn't mind if the question is too silly.
I have installed jenkins on a Ubuntu machine, and is accessible at localhost:8080. I have successfully configured it to work with Maven2 and Git as well. Next, I created a job/project (A Java/Spring application), and got it to build without error on Jenkins as well.
Now my question is, where do I see this application running? :)
Best Regards
James

To deploy : http://mojo.codehaus.org/tomcat-maven-plugin/plugin-info.html to do it with maven or https://wiki.jenkins-ci.org/display/JENKINS/Deploy+Plugin to do it with jenkins

You can see the console output in the running job if you click the running job and look for the link on the left hand side.

Building and deploying are two different things. Jenkins can do the latter for you too but you need to have it configured in your maven project. Typically this is accomplished (for tomcat) using the tomcat maven plugin

Related

How to run Scala project on local Apache - Windows

I received a Scala project to be run locally.
I'm on Windows, I've installed MySql (needed by the project), Apache 2.4 configured and started on port 9000 as suggested on Play Framework website, installed sbt and scala.
Now.. I got lost.. I don't understand how am I supposed to publish/deploy the project locally?
Which directory is supposed to be the www Apache directory?
How am I supposed to tell sbt that I'm running Apache?
I cant find any hint around.
Any structured suggestion to help my nut crawling on a bit?
Thank you!
Not sure if that would be helpful, but you've mentioned play framework. If your project is made with play, you should be able just to execute sbt run in your project directory, and then your application should be accessible via http://localhost:9000.
Details here: https://www.playframework.com/getting-started

How to get logs from a Jenkins plug-in during Maven based development?

I am developing a Jenkins plug-in and want to see some logging. I am using the Maven environment and running
mvn hpi:run
to launch Jenkins and my plug-in. I have enabled the Jenkins logger configuration to catch my logs - but I see no logs less severe than INFO.
So I guess that I need to configure something to drop my debugging logs into wherever (syslog?) Jenkins pulls them from (I am asking Jenkins to pull all logs).
Can someone please explain how to do this via Maven? I have seen the 'How to set jenkins log level from maven?' article and tried those techniques but this seemed to cause Jenkins to hang, with messages about console restarts.
Please be very specific as I'm a relative Java newbie and would rather you treated me like an idiot than gave me only half an answer, assuming I knew the rest ;-). Thanks!

Jenkins - Build, Deploy and Promote

Recently, I started learning how to use Jenkins CI. So I am a little bit of a noob at jenkins. I am about to start to try and do the following:
I have setup a maven multi-module job on jenkins, which builds, tests, and finally creates 4 seperate war applications. I archive the war artifacts as part of this job. These war files will only ever be built once, they contain multiple environment properties, and the war file along with each environments server will manage the profile it runs in, eg dev, test, staging, prod, etc
I have another job on jenkins which will deal with the deployment to multiple environments.
This second job, uses the copy artifact plugin, and uses a post build action to deploy to a dev environment.
The job in step 2 will hopefully be able to have multiple promotions, allowing deployment to multiple environments: test/staging/performance/production etc.
I have searched stackoverflow and google, and all the posts I see, always use the parameterized plugin, specifying a parameter for the environment. This means there is a seperate build for each env which I don't like.
Can anyone tell me if this is the right way to go? Or direct me to some tutorial on how to do this properly.
Looks like what you need is a matrix-project build.
P.S.
A good introduction to Jenkins could be found in Jenkins: The Definitive Guide
After playing around with the jenkins configuration. I have this working very nicely now.
In the deployment job, I didn't see the "Add another promotion process" button, which allows me to promote the same build to multiple environments manually or automatically.

IntelliJ, Maven, JRebel (?), Tomcat and Continuous Integration. How To?

I am new in Java and Continuous Integration. I want to setup a development environment using IntelliJ, Maven, GIT and JRebel (this was strongly recommended by a friend of mine). Tomcat Server is on AWS, not on my local Mac OS X machine. Is it possible to use GIT / JRebel and 'update' the remote project on the fly (after saving the files?). Which modules should I install on my Mac and which on Tomcat? Do I need Jenkins as well?
With JRebel Remoting, it is possible to push the changes to the remote applications, without having to configure any extra ports even. This is applicable if you would like to code something in the IDE, and then just push the changes to the remote application. But if you'd like to run the full test suite, then it is better to do via CI and then you will have quite different process - you will have to wait a bit longer until your changes become visible in the running app.

Build and Deploy Grails App on Jenkins

I've inherited an existing Grails Maven app and have been tasked with looking into automating the build and deployment of it.
It currently uses grails 1.3.7 but will be upgraded to 2.1 soon.
So
1: Is there a way to allow someone log into jenkins and click a button that will automatically create a build?
2: Is there then a follow up task I could use to allow the user deploy the build to a server I have specified beforehand?
Any links to usefull/relevant articles would be great.....I'm fairly new to both grails and jenkins.
1 + 2) Yes. This is pretty much exactly what a Jenkins job does.
Take a look at Continuous Integration with Grails for a quick start, or the Jenkins Wiki for a slightly less quick start.

Resources