How to Setup Jenkins on Windows in Azure

To install a Jenkins server in Azure on Windows 2016, the easiest and quickest way is to use our marketplace image that’s available to download.

 

setup Jenkins server in azure

Start using Jenkins in Azure

 

To start using the Jenkins server deployment in Azure after deploying the image from the marketplace, click on the Jenkins desktop icon to launch the application:

 

setup-jenkins-on-azure

 

 

The first time you launch you will see the following screen. Follow the instructions to locate the initial administrator password in order to complete the setup and create a new admin account:

unlock jenkins

 

Jenkins Amin URL

 

By default, your Jenkins runs at http://localhost:8080/. This can be changed by editing jenkins.xml, which is located in the installation directory (C:\Program Files (x86)\Jenkins). This file is also the place to change other boot configuration parameters, such as JVM options, HTTPS setup, etc.

 

There are a few ways to access the Jenkins login page, either locally on the server by accessing http://localhost:8080

 

Or by the servers internal DNS host name on your internal network: http://dnshostname:8080

 

Or by using the public Azure DNS public IP/DNS Name. For example: jenkserver01.westus.cloudapp.azure.com

 

To configure the public DNS host name, you do this within the Azure portal, under the VMs properties. You will need to give the VM a public IP address and can give a DNS hostname:

 

jenkins-public-url-azure

 

Starting / Stopping the Jenkins Windows Service

 

Jenkins is installed as a Windows service, and it is configured to start automatically upon boot. To start/stop them manually, use the services manager from administrative tools, or the sc command line tool.

 

Configuring the pre loaded plugins

 

To configure or view documentation on using the plugins, within Jenkins go to ‘Manage Jenkins / Manage Plugins / Installed

 

Default Jenkins Plugins

 

  • Ant Plugin
  • Apache HttpComponents Client 4.x API Plugin
  • Authentication Tokens API Plugin
  • bouncycastle API Plugin
  • Branch API Plugin
  • Build Timeout
  • Command Agent Launcher Plugin
  • Common API for Blue Ocean
  • Credentials Binding Plugin
  • Credentials Plugin
  • Display URL API
  • Docker Commons Plugin
  • Docker Pipeline
  • Durable Task Plugin
  • Email Extension Plugin
  • Folders Plugin
  • Git client plugin
  • Git plugin
  • GIT server Plugin
  • GitHub API Plugin
  • GitHub Branch Source Plugin
  • GitHub plugin
  • Gradle Plugin
  • Jackson 2 API Plugin
  • JavaScript GUI Lib: ACE Editor bundle plugin
  • JavaScript GUI Lib: Handlebars bundle plugin
  • JavaScript GUI Lib: jQuery bundles (jQuery and jQuery UI) plugin
  • JavaScript GUI Lib: Moment.js bundle plugin
  • JDK Tool Plugin
  • JSch dependency plugin
  • JUnit Plugin
  • Kubernetes Continuous Deploy Plugin
  • LDAP Plugin
  • Lockable Resources plugin
  • Mailer Plugin
  • MapDB API Plugin
  • Matrix Authorization Strategy Plugin
  • Matrix Project Plugin
  • OWASP Markup Formatter Plugin
  • PAM Authentication plugin
  • Pipeline
  • Pipeline Graph Analysis Plugin
  • Pipeline (many plugins installed)
  • SCM API Plugin
  • Script Security Plugin
  • SSH Credentials Plugin
  • SSH Slaves plugin
  • Structs Plugin
  • Subversion Plug-in
  • Timestamper
  • Token Macro Plugin
  • Workspace Cleanup Plugin

 

Jenkins Firewall Ports

 

The Jenkins Windows Azure image comes with port 8080 configured to allow you to access the admin URL both internally and externally.

 

Depending on what you will be using the Jenkins server for, you’ll need to confirm if any firewall ports will need to be open in order for the Jenkins server to reach any resources in your environment.

 

To setup Azure firewall rules refer to – Azure Network Security Groups

 

Support

 

If you have any questions about the setup of Jenkins in Azure using our Windows Jenkins image leave your comments below and we will reply within 24 hours.

Andrew Fitzgerald

Cloud Solution Architect. Helping customers transform their business to the cloud. 20 years experience working in complex infrastructure environments and a Microsoft Certified Solutions Expert on everything Cloud

No Comments

Post a Comment

Comment
Name
Email
Website