To install a Jenkins server in Azure on Windows 2016 or 2019, the easiest and quickest way is to use our marketplace images that are available to download and come fully configured with Jenkins. Jenkins is the leading open source Continuous Integration and Continuous Delivery (CI/CD) server that enables the automation of building, testing, and shipping software projects. This solution is a Windows Server running Jenkins with all plugins needed to deploy any service into Azure and is fully configured for quick and easy deployment.
Jenkins Windows Server in Azure Cloud
Setup Jenkins on Server 2016 in Azure
Setup Jenkins on Server 2019 in Azure
Also Checkout Other Jenkins Cloud Deployments:
Table of Contents
Using Jenkins Windows on Azure Cloud
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:
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:
Log in with Jenkins Admin 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:
Start / Stop/ Restart 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.
To stop:
jenkins.exe stop
To start Jenkins on Windows Cloud:
jenkins.exe start
To restart Jenkins server on Windows:
jenkins.exe restart
Configuring the pre loaded plugins
Plugins are the primary means of enhancing the functionality of a Jenkins environment to assist the organization needs.
They can be installed on a Jenkins controller and you can integrate various build tools, cloud providers, analysis tools, and much more.
To configure or view documentation on using the plugins, within Jenkins go to ‘Manage Jenkins / Manage Plugins / Installed ‘
Default Jenkins Plugins
Here’s a list with all of the default plugins, suggested for Jenkins:
- 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 Windows Firewall Ports
The default Jenkins installation runs on Ports 8080 and 8443.
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
Jenkins Windows Support/Documentation
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 as soon as we can.
