How to Install Jenkins on Azure

When I installed Jenkins on Azure, it was definitely easier than installing everything including OS from scratch but some things threw me off. It’s not totally “out of the box” as of April 2019, so here are some of my notes.

  1. Click “Create a resource”.
  2. Enter “jenkins” in the search box and hit enter.
  3. Choose “Jenkins by Microsoft”.
  4. Click Create.
  5. Enter Name and User name. Name should be the name of the Jenkins instance you are about to create. User name should be the administrative user that you will use to ssh into the Jenkins instance. You can name it whatever you want.
  6. Use SSH public key for authentication so choose “SSH public key”. Enter your public key to the text area. * Please read my article about ssh private/public key if you are not familiar with it.
  7. Create a new resource group or choose an existing one. I’m creating a new jenkinssvr group.
  8. Click OK to proceed to the next step.
  9. In the next screen where you can select VM size, click “change size” and you can select the size of VM from the suggested selection. For my testing purpose, I just go with the spec within my $50 credit limit which comes with Visual Studio Professional subscription. I also chose HDD as it’s cheaper than SSD.

    I’m sure there would be a lot thoughts that have to go into selecting the VM specs in real situations but I’m going to just keep it simple here.
  10. Domain name label is basically a name that you can use to reach the VM. You can give it whatever name you want. I also chose OpenJDK for JDK that Jenkins depends on just because I use it at work.
  11. I don’t know what the next option is for but I’m leaving it as default.
  12. Next confirm the summary and click OK.
  13. Finally click Create button. Once you click on the Create button, deployment process starts.
  14. Now let’s access Jenkins! Try to hit the URL like http://yourjenkinsserver.westus.cloudapp.azure.com but it’s not accessible. What gives? Let’s take a detailed look at what’s going on and analyze how we can resolve this issue in the next blog entry.

Author: admin

A software engineer in greater Seattle area

Leave a Reply

Your email address will not be published. Required fields are marked *