Every now and then I’ve had to set up Jenkins (usually locally) either to test an idea out or because I’m waiting for one to be set up by the “Environments” team. Setting up Jenkins is pretty straight forward but it does have a foot print and can be troublesome further down the track if you don’t tidy up or forget about what resource its taking up. For example, Jenkins uses port 8080 by default. However this is a common port that is used by other web apps which mean you could end up with a conflict. (which is easy to fix if you remember installing Jenkins months ago or that it’s the app that’s using the port.)
One way of avoiding these sorts of problem is by setting up Jenkins in a virtual machine. This means you can quickly get everything up and running and tear it down quickly. And with the current tools this is easier to do than ever.