Let's edit the application sources and add our own stuff to customize it to our needs. On a basic Tomcat web application, customization is not the adequate term as the code skeleton doesn't provide much, and we have to configure our favorite web framework and utility classes; but at least, we have a base project structure to get started quickly. If you're familiar with Maven archetype , this is mostly comparable at this stage.
After making some changes to our app, let's commit and push it to CloudBees:
git.add git commit -m "I made some changes" git push origin master
Note
If you are not familiar with a distributed SCM such as Git, you just need to know that sending changes to a CloudBees-hosted repository is a two-step process:
Commit the repository to group file changes into an atomic commit object
Push it to send pending local commits to the remote repository
Now, let's have a look at our DEV@cloudJenkins instance. You'll notice that the build queue...