Skip to main content
Version: 1.0

Jenkins Getting Started

Jenkins is a self-contained, open source automation server which can be used to automate all sorts of tasks related to building, testing, and delivering or deploying software.

If you have installed Websoft9 Jenkins, the following steps is for your quick start

Preparation​

  1. Get the Internet IP of your Server on Cloud
  2. Check your Inbound of Security Group Rule of Cloud Console to ensure the TCP:80 is allowed
  3. Connect your Server and get default username and password of Jenkins
  4. Complete Five steps for Domain if you want to use Domain for Jenkins

Jenkins Initialization​

Steps for you​

  1. Using local browser to visit the URL http://DNS or http://Server's Internet IP, you will enter initial wizard of Jenkins

  2. Input the password as prompted(Don't have password?)

  3. Login the Jenkins console

  4. Install plugins

  5. Create user for Jenkins

More useful Jenkins guide, please refer to Jenkins Documentation

Having trouble?​

Below is for you to solve problem, and you can contact Websoft9 Support or refer to Troubleshoot + FAQ to get more.

Jenkins QuickStart​

This task【Build Github repository by Jenkins】 is for your Jenkins QuickStart

  1. Set up Personal access tokens on GitHub for Jenkins connection

  2. In Jenkins global system settings, connect to GitHub

  3. Create a build task: enter the task name, enter the Github project URL, account password and other information according to the process

  4. After the corresponding Github project is modified, push the submission; Jenkins completes the automated build and deployment

Jenkins Setup​

Install plugin​

Login to Jenkins, open：【【Manage Jenkins】>【Plugins Manager】 to manage and install all plugins

Configure SMTP​

  1. Install the Jenkins plugin Email Extension

  2. Prepare your SMTP parameter

  3. Log in Jenkins Console, open 【Manage Jenkins】>【Configure System】, set you SMTP Jenkins SMTP

  4. Test it

Jenkins reference sheet​

The below items and General parameter sheet is maybe useful for you manage Jenkins

Run docker ps, view all containers when Jenkins is running:

CONTAINER ID   IMAGE                       COMMAND                  CREATED             STATUS          PORTS                                                                                      NAMES
22e92eb0e4b5   jenkins/jenkins:lts-jdk11   "/usr/bin/tini -- /u…"   About an hour ago   Up 53 minutes   0.0.0.0:50000->50000/tcp, :::50000->50000/tcp, 0.0.0.0:9001->8080/tcp, :::9001->8080/tcp   jenkins

Port​

No special port

Version​

docker exec -i jenkins cat /var/jenkins_home/config.xml |grep version |sed -n 2p |tr -d "</>version"

Service​

sudo docker start | stop | restart | stats jenkins

CLI​

Jenkins has a built-in command line interface that allows users and administrators to access Jenkins from a script or shell environment.

java -jar jenkins-cli.jar [-s JENKINS_URL] [global options...] command [command options...] [arguments...]

API​

Jenkins provides machine-consumable remote access API to its functionalities

curl JENKINS_URL/job/JOB_NAME/buildWithParameters \
  --user USER:TOKEN \
  --data id=123 --data verbosity=high