What is Jenkins?

Jenkins is a widely adopted open-source automation server designed to facilitate continuous integration (CI) and continuous delivery/deployment (CD) in software development. Jenkins automates repetitive tasks such as building, testing, and deploying code, enabling development teams to improve code quality, accelerate release cycles, and enhance collaboration.

Originally released in 2011 as a fork of the Hudson project, Jenkins has evolved into the de facto CI/CD tool due to its rich plugin ecosystem, extensibility, and ease of integration with other tools. It provides a web-based interface for managing pipelines and jobs, supporting diverse programming languages, build tools, version control systems, and deployment environments.

By automating the entire software delivery pipeline—from code commit to production deployment—Jenkins helps organizations adopt DevOps practices, reduce manual errors, and achieve rapid feedback cycles.

Major Use Cases of Jenkins

Jenkins serves multiple critical roles across the software development lifecycle. Some of the key use cases include:

1. Continuous Integration (CI)

Jenkins automates the process of integrating code changes from multiple developers into a shared repository multiple times a day. Upon each commit, Jenkins triggers builds and runs automated tests, helping teams identify integration issues early and prevent “integration hell.”

2. Continuous Delivery (CD) and Continuous Deployment

Beyond integration, Jenkins automates packaging, staging, and deployment of applications. Continuous Delivery ensures the software can be released to production at any time, while Continuous Deployment automatically pushes every change passing tests into production.

3. Automated Testing

Integration with testing frameworks enables Jenkins to run unit tests, integration tests, UI tests, performance tests, and security scans automatically as part of the pipeline. It helps maintain code quality by catching defects early.

4. Build Automation

Jenkins automates compiling source code, managing dependencies, packaging binaries, and generating documentation. It supports a wide range of build tools like Maven, Gradle, Ant, and npm.

5. Infrastructure as Code and Configuration Management

Jenkins pipelines can trigger infrastructure provisioning and configuration management workflows using tools like Terraform, Ansible, Puppet, or Chef, enabling automated environment setup and scaling.

6. Multi-Platform and Cross-Language Support

Jenkins supports building and testing applications across different operating systems (Windows, Linux, macOS) and programming languages (Java, Python, Go, Ruby, .NET), making it suitable for heterogeneous environments.

7. DevOps and Pipeline as Code

Using Jenkinsfile (a Groovy-based DSL), teams define complex CI/CD pipelines as code, version-controlled alongside application code, enabling reproducible and auditable workflows.

How Jenkins Works Along with Architecture

Jenkins’ architecture is modular and scalable, designed around a master-agent model to efficiently manage workloads and distribute builds.

Core Components

• Jenkins Master The master is the central orchestrator. It provides the user interface (web UI), schedules build jobs, dispatches build tasks to agents, manages plugins, and maintains build results and logs. The master also handles configuration, security, and API requests.
• Build Agents (Slaves) Agents are worker nodes connected to the master that execute build jobs. Agents can run on different machines, operating systems, or cloud providers, enabling distributed and parallel build execution. This architecture enhances scalability and fault tolerance.

Build Pipeline Architecture

1. Job Definition Users configure jobs or pipelines on the Jenkins master either through the UI or via Jenkinsfile scripts stored in source control. Jobs specify source code repositories, build triggers, build steps, test suites, post-build actions, and notifications.
2. Trigger Mechanism Builds can be triggered automatically on events such as code commits (via webhooks), scheduled times (cron), or manually by users. Jenkins also supports pipeline triggers from other jobs or external systems.
3. Task Scheduling and Execution The master assigns builds to available agents based on labels, resource availability, or predefined criteria. Agents pull source code from repositories, execute build commands, run tests, package artifacts, and perform deployments.
4. Result Aggregation and Reporting Build results and logs are sent back to the master, which updates dashboards, archives artifacts, and notifies stakeholders through email, Slack, or other messaging services.

Plugin Ecosystem

Jenkins’ extensibility comes from a vast ecosystem of plugins (~1800+) that integrate with source control (Git, SVN), build tools (Maven, Gradle), testing frameworks (JUnit, Selenium), container platforms (Docker, Kubernetes), deployment tools, notifications, and security systems.

Basic Workflow of Jenkins

The typical Jenkins workflow in a modern CI/CD pipeline follows these steps:

1. Source Code Commit

Developers push code changes to a version control system such as GitHub, Bitbucket, or GitLab.

2. Build Trigger

A webhook or polling mechanism in Jenkins detects the commit and triggers a build job or pipeline.

3. Code Checkout

Jenkins checks out the latest code to a clean workspace on a build agent.

4. Build Execution

The agent compiles the code, resolves dependencies, and builds executables or packages.

5. Automated Testing

Automated tests run on the build artifacts to validate functionality, integration, performance, or security.

6. Artifact Archiving

Build artifacts such as binaries, Docker images, or reports are archived on Jenkins or uploaded to artifact repositories like Nexus or Artifactory.

7. Deployment (Optional)

If tests pass, Jenkins can deploy the build to staging, QA, or production environments using shell scripts, configuration management tools, or cloud APIs.

8. Notifications and Reporting

Developers and stakeholders receive notifications of build status via email, Slack, or dashboard updates, allowing rapid response to failures.

Step-by-Step Getting Started Guide for Jenkins

Step 1: Install Jenkins

• Linux Installation (Ubuntu Example): wget -q -O - https://pkg.jenkins.io/debian/jenkins.io.key | sudo apt-key add - sudo sh -c 'echo deb https://pkg.jenkins.io/debian binary/ > /etc/apt/sources.list.d/jenkins.list' sudo apt update sudo apt install jenkins sudo systemctl start jenkins sudo systemctl enable jenkins
• Windows/macOS:
  Download and install Jenkins from https://jenkins.io/download/.
• Docker: docker run -p 8080:8080 -p 50000:50000 jenkins/jenkins:lts

Step 2: Access Jenkins UI

• Open http://localhost:8080 in your browser.
• Retrieve the initial admin password from /var/lib/jenkins/secrets/initialAdminPassword.
• Install suggested plugins via setup wizard.
• Create an admin user.

Step 3: Configure Jenkins

• Set up global tools like JDK, Git, Maven, and Docker.
• Configure credentials for source control and deployment systems.
• Set security and access control policies.

Step 4: Create Your First Job

• Click “New Item.”
• Choose “Freestyle Project” or “Pipeline.”
• Configure SCM repository URL.
• Add build steps (e.g., Maven build, shell scripts).
• Configure build triggers (e.g., Poll SCM, webhook).

Step 5: Run and Monitor Builds

• Start builds manually or by pushing code.
• Monitor build progress via console logs.
• Review test reports and archived artifacts.

Step 6: Define Pipeline as Code

• Create a Jenkinsfile in your repo with pipeline stages: pipeline { agent any stages { stage('Build') { steps { sh 'mvn clean package' } } stage('Test') { steps { sh 'mvn test' } } stage('Deploy') { steps { sh './deploy.sh' } } } }
• Create a pipeline job in Jenkins linked to your repository to run this file.

Step 7: Scale with Agents and Plugins

• Add build agents (via SSH, Docker, Kubernetes).
• Install plugins for notifications, code analysis, container support.

The post Jenkins: A Comprehensive Guide to Architecture, Use Cases, Workflow, and Getting Started appeared first on scmGalaxy.

A Jenkins Admin can execute groovy scripts remotely by sending an HTTP POST request to /script/ url or /scriptText/.

curl example via bash

curl -d "script=<your_script_here>" https://jenkins/script
# or to get output as a plain text result (no HTML)
curl -d "script=<your_script_here>" https://jenkins/scriptText

curl submitting groovy file via bash

curl --data-urlencode "script=$(< ./somescript.groovy)" https://jenkins/scriptText

curl submitting groovy file providing username and password via bash

curl --user 'username:password' --data-urlencode "script=$(< ./somescript.groovy)" https://jenkins/scriptText

Jenkins CLI offers the possibility to execute groovy scripts remotely using groovy command or execute groovy interactivelly via groovysh.

java -jar jenkins-cli.jar -noCertificateCheck -s https://10.0.0.91/ groovy disableEnableJobsMatchingPattern.groovy jobPattern=build_git_auto disableOrEnable=disable --username 12345 --password banana

Reference
https://wiki.jenkins.io/display/JENKINS/Jenkins+Script+Console

The post How to execute grovvy script remotely on Jenkins server? appeared first on scmGalaxy.

Here are the List of way using you can apply grovy code in Jenkins

Method -1: Groovy plugin
This plugin adds the ability to directly execute Groovy code.
More info – https://wiki.jenkins.io/display/JENKINS/Groovy+plugin

Method -2: Jenkins script console
The inbuilt script console is a very useful and powerful Jenkins extension and ideally suits certain types of tasks. This simple but powerful built-in web console allows you to run Groovy scripts on your Jenkins instance (or its slave nodes) from directly within the user interface, and is installed as standard.

To access the console, either navigate to Manage Jenkins and then select Script Console, or simply append /script to your Jenkins host and port, like this for example: http://jenkinshost:8080/script
Running Script Console on the master
This feature can be accessed from “Manage Jenkins” > “Script Console”. Or visit the sub-URL /script on your Jenkins instance.

Running Script Console on agents
Visit “Manage Jenkins” > “Manage Nodes”. Select any node to view the status page. In the menu on the left, a menu item is available to open a “Script Console” on that specific agent.

More info – https://wiki.jenkins.io/display/JENKINS/Jenkins+Script+Console

Method -3: Scriptler Plugins
Scriptler allows you to store/edit groovy scripts and execute it on any of the slaves/nodes… no need to copy/paste groovy code anymore.
More Info – https://wiki.jenkins.io/display/JENKINS/Scriptler+Plugin

Reference

https://wiki.jenkins.io/display/JENKINS/Jenkins+Script+Console

The post How to run/execute groovy script in Jenkins? appeared first on scmGalaxy.

Here are the list of Groovy Script which can be used in Jenkins to automate the JOBs and CI process. Please add your list in the comment sections as well.

Main Source – 

• https://github.com/scmgalaxy/jenkins-groovy-script-example
• https://github.com/cloudbees/jenkins-scripts
• https://wiki.jenkins.io/display/JENKINS/Jenkins+Script+Console
• https://pghalliday.com/jenkins/groovy/sonar/chef/configuration/management/2014/09/21/some-useful-
• jenkins-groovy-scripts.html
• https://github.com/cloudbees/jenkins-scripts
• https://github.com/jenkinsci/jenkins-scripts
• https://gist.github.com/dnozay/e7afcf7a7dd8f73a4e05
• https://github.com/samrocketman/jenkins-bootstrap-shared
• https://github.com/samrocketman/jenkins-script-console-scripts

Example Groovy Script 

• Activate Chuck Norris Plugin — This script activates Chuck Norris plugin for all jobs in your Jenkins server
• Add a Maven Installation, Tool Installation, Modify System Config
• Add a new label to slaves meeting a condition — This script shows how to alter the slave nodes’ label membership. In this case we create a new label if the existing label contains a string. It has been tested from the Jenkins command window.
• Add notification plugin to every job — This script will add the Notification Plugin to every job.
• Allow broken build claiming on every jobs — With the following simple script, you can activate the option on every jobs of your server in just one go.
• Batch-Update Mercurial branch that is checked out — Updates for multiple jobs which branch will be checked out from Hg
• Bulk rename projects
• Change JVM Options in all Maven tasks of Freestyle Jobs — This script find all Maven Tasks registered in freestyle jobs and replace JVM Options by a new value.
• Change publish over SSH configuration
• Change SCMTrigger for each project to disable during the night and the week-end — This script lets you easily change all jobs running every minutes so that it gets disabled between 21:00 and 07:00 and on Saturday and Sunday.
• Change Version-Number in SVN-path
• Clone all projects in a View — This script enumerates all projects belonging to a specific view and clones them.
• Convert standard mail notifications to use the Mail-Ext Publisher plugin — This script replace mail notifications in all projects by Mail-Ext publisher plugin and re-uses existing recipients.
• Delete .tmp files left in workspace-files — This scripts deletes all the tmp files left in workspace-files directory after the build. On windows servers, this seems pretty common so we run this script on daily basis.
• Delete workspace for all disabled jobs — Deletes the workspace for all disabled jobs to save space
• Disable all jobs — This script disables all jobs in your Jenkins server
• Display Information About Nodes — This scripts displays a bunch of information about all the slave nodes.
• Display job parameters — This scripts displays the parameters for all the jobs along with their default values (if applicable).
• Display jobs group by the build steps they use
• Display list of projects that were built more than 1 day ago. — This script to display list of projects that were built more than 1 day ago.
• Display mail notifications recipients — This script displays for all jobs the list of mail recipients used for notifications.
• Display monitors status — Jenkins uses monitors to validate various behaviors. If you dismiss one, Jenkins will never propose you to reactivate it. This script allows you to check the status of all monitors and to reactive them.
• Display timer triggers — This scripts displays the timer triggers for all the jobs in order to better arrange them.
• Display Tools Location on All Nodes — This script can help to get Jenkins tools localtion on all your slaves
• Enable Timestamper plugin on all jobs — With the following simple script, you can activate the option on every jobs of your server in just one go.
• Failed Jobs — This scripts displays a list of all failed jobs. Addon: restart them.
• Find builds currently running that has been executing for more than N seconds
• Grant Cancel Permission for user and group that have Build permission — This script will go through all groups and users in both Global security and per job security settings.
• Invalidate Jenkins HTTP sessions — This script can monitor and invalidate HTTP sessions if there are many open ones on your server.
• Manually run log rotation on all jobs — Runs log rotation on all jobs to free space
• Monitor and Restart Offline Slaves — This script can monitor and restart offline nodes if they are not disconnected manually.
• Monitoring Scripts — Several scripts to display data about http sessions, threads, memory, JVM or MBeans, when using the Monitoring plugin.
• Parameterized System Groovy script — This script will demonstrate how to get parameters in a system groovy script.
• Preselect username in Maven Release Build
• Printing a list of credentials and their IDs
• Remove all disabled modules in Maven jobs — To remove all disabled modules in Maven jobs
• Remove Deployed Artifacts Actions — This script is used to remove the Deployed Artifacts list that is uselessly stored for each build by the Artifact Deployer Plugin.
• Remove Git Plugin BuildsByBranch BuildData — This script is used to remove the static list of BuildsByBranch that is uselessly stored for each build by the Git Plugin.
• Set GitBlitRepositoryBrowser with custum settings on all repos — This scripts allows to update the repo browser. Can be adapted to any other browser, not only gitblit.
• Update maven jobs to use the post build task to deploy artifacts — This script updates all maven jobs having a deploy goal by install and activate the post build step to deploy artifacts at the end of the build
• Update SVN Browser
• Wipe out workspaces of all jobs — This script wipes out the workspaces of all jobs on your Jenkins server
• Wipe workspaces for a set of jobs on all nodes — The script wipes workspaces of certain jobs on all nodes

The post Database of Groovy Script for Jenkins Automation appeared first on scmGalaxy.

Jenkins is continuous integration tools which help to integrate other tools to automate the software development activity and repetitive tasks. Jenkins has 2 releases. One, Community version which open source and free and another one is Jenkins Enterprise which is from Cloud bees for enterprise. Jenkins is extremely powerful with vast amount of plug-in supported. Jenkins is one of the most active open source projects so learning and finding the information is easily available on the internet. Jenkins uses master/slave architecture to manage distributed builds.
Jenkins Architecture

Jenkins Architecture is based on the distributed. This has 2 components.

• Jenkins Server
• Jenkins Node/Slave/Build Server

Jenkins server is a web dashboard which is nothing but powered from a war file, default run on 8080 ports. Using Dashboard, You can configure the Jobs/Projects but the build takes place in Nodes/Slave. By default one Nodes/Slave is configured and running in Jenkins Server. You can add more Nodes/Slave as well using IP address, user name, Password using the ssh/jnlp/webstart methods.

Your main Jenkins server is the master. In short, the master’s job is to handle scheduling build jobs, dispatching builds to the slaves for the actual execution, monitor the slaves (possibly taking them online and offline as required) and recording and presenting the build results. Even in a distributed architecture, a master instance of Jenkins can also execute build jobs directly.

The job of the slaves is to do as they are configured in the Jenkins Server, which involves executing build jobs dispatched by the master. You can configure a project to always run on a particular slave machine, or a particular type of slave machine, or simply let Jenkins pick the next available slave.
Jenkins is developed using Java and Java is platform independent thus Jenkins servers and nodes/slave can be configured in any servers including Windows, Linux and Mac.

The post Jenkins Architecture Explained!!! appeared first on scmGalaxy.

My Recommendation – Jenkins

The post Difference between jenkins and Urbancode build appeared first on scmGalaxy.

Agenda

• Scala – A Scalable language
• Scala Download
• Scala Software Requirement
• Scala IDEs
• Scala Install Configuration
• Scala First Program
• Compile and Run
• Building Scala Projects using Jenkins
• Sbt downloand and configure

The post Build Scala Project using sbt and Jenkins appeared first on scmGalaxy.

Enabling jenkins integration with silk central test manager

The post Enabling Jenkins integration with Silk Central Test Manager appeared first on scmGalaxy.

At my workplace we create weekly branches for releases. I tried p4 integ and p4 submit inside Jenkins so I could schedule branching. I used export to setup P4PORT and P4CLIENT. It dies saying files not in client view. Can you schedule Jenkins to create branches?

Thanks,
Rakhee

rajeshkumar replied the topic: Re: Does Jenkins let you create branches?
Hi,

At present perforce jenkins plugins just support following operations…
Polling
Synchronizing
Browsing latest changes
Labeling builds (tagging)
you can create your custom script to do so.However, the error which you are getting should be somthing related to your p4 client view. re-check your client view mapping and branch mapping. both should be in client view.
Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn

The post Does Jenkins let you create branches? appeared first on scmGalaxy.

[workspace] $ “C:\Program Files\Perforce\p4.exe” login -p
[workspace] $ /usr/bin/p4 login -p

Solution:

This must be related to value of P4USER, P4PORT, P4PASSWD or P4TICKET variable is not getting passed to Jenkins.
Try following..
Restart Machine or Restart Services OR Set P4USER, P4PORT, P4PASSWD or P4TICKET and Restart Jenkins Services again.
Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn

The post /usr/bin/p4 error in windows machine with jenkins appeared first on scmGalaxy.

rajeshkumar replied the topic: How to Change Jenkins HTTP port number?
For Windows (service installation)
Edit jenkins.xml or hudson.xml

Navigate to the directory where you installed Jenkins/Hudson and you will see the XML at the root. Open it and look for tag, there will be all the command arguments to be used when starting up Jenkins or Hudson.
One of those arguments is –httpPort, typically:
–httpPort=8080.
Change 8080 to whatever port number you want.

WAR File, deployed in GlassFish
You will need to change the default HTTP port in GlassFish.

Natively installed in linux
At least for RHEL, you should be able to find the /etc/sysconfig/hudson, which typically has the following line, among other configuration ones:
HUDSON_PORT=”8080″.
Change 8080 to whatever port number you want.

Other linux distributions (using wrapper)
At the time of writing, Arch Linux’s AUR Jenkins version uses wrapper to launch itself from the .war file.

Edit /opt/jenkins/conf/wrapper.conf, find wrapper.app.parameter.2=–httpPort=8070 (typically).
Change 8070 to whatever port number you want.

This wrapper solution applies to any system using wrapper, not only linux.
Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn

The post How to Change Jenkins HTTP port number? appeared first on scmGalaxy.

The post Jenkins Plugins forJob Configuration change email notification appeared first on scmGalaxy.

The post Jenkins Plugins for Job Configuration change email notification appeared first on scmGalaxy.

The post Upgrade Hudson Nodes To Jenkins appeared first on scmGalaxy.

The post Upgrade Hudson Nodes To Jenkins appeared first on scmGalaxy.

SEVERE: org.xmlpull.v1.XmlPullParserException: only whitespace content allowed before start tag and not # (position: START_DOCUMENT seen #… @1:1)
Feb 25, 2014 2:12:56 AM hudson.plugins.testng.parser.ResultsParser log
SEVERE: org.xmlpull.v1.XmlPullParserException: only whitespace content allowed before start tag and not # (position: START_DOCUMENT seen #… @1:1)
Feb 25, 2014 2:12:56 AM hudson.plugins.testng.parser.ResultsParser log
SEVERE: org.xmlpull.v1.XmlPullParserException: only whitespace content allowed before start tag and not # (position: START_DOCUMENT seen #… @1:1)
Feb 25, 2014 2:12:57 AM hudson.plugins.testng.parser.ResultsParser log
SEVERE: org.xmlpull.v1.XmlPullParserException: only whitespace content allowed before start tag and not # (position: START_DOCUMENT seen #… @1:1)
Feb 25, 2014 2:12:57 AM hudson.plugins.testng.parser.ResultsParser log
SEVERE: org.xmlpull.v1.XmlPullParserException: only whitespace content allowed before start tag and not # (position: START_DOCUMENT seen #… @1:1)

Issues 2: Post upgrade, you will find under “Manage Jenkins” sections

You have data stored in an older format and/or unreadable data

Issues 3: Post upgrade, you will find under “Manage Jenkins” sections
It appears that your reverse proxy set up is broken.
Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn

rajeshkumar replied the topic: Jenkins Upgrade and Solution!!!
Solution for Issues 2
To the right of that messages is a “Manage” button.. click that, and it
explains in great detail what this is about.

Once you will click on it, You may find information as below;

Manage Old Data

When there are changes in how data is stored on disk, Jenkins uses the following strategy: data is migrated to the new structure when it is loaded, but the file is not resaved in the new format. This allows for downgrading Jenkins if needed. However, it can also leave data on disk in the old format indefinitely. The table below lists files containing such data, and the Jenkins version(s) where the data structure was changed.

Sometimes errors occur while reading data (if a plugin adds some data and that plugin is later disabled, if migration code is not written for structure changes, or if Jenkins is downgraded after it has already written data not readable by the older version). These errors are logged, but the unreadable data is then skipped over, allowing Jenkins to startup and function properly.

Type Name Version

The form below may be used to resave these files in the current format. Doing so means a downgrade to a Jenkins release older than the selected version will not be able to read the data stored in the new format. Note that simply using Jenkins to create and configure jobs and run builds can save data that may not be readable by older Jenkins releases, even when this form is not used. Also if any unreadable data errors are reported in the right side of the table above, note that this data will be lost when the file is resaved.

Eventually the code supporting these data migrations may be removed. Compatibility will be retained for at least 150 releases since the structure change. Versions older than this are in bold above, and it is recommended to resave these files.
No old data was found.

Unreadable Data

It is acceptable to leave unreadable data in these files, as Jenkins will safely ignore it. To avoid the log messages at Jenkins startup you can permanently delete the unreadable data by resaving these files using the button below.
Type Name Error
hudson.maven.MavenModuleSet US-Harmony-E2E-C4-Regression MissingFieldException: No field ‘perModuleEmail’ found in class ‘hudson.maven.MavenModuleSet’
hudson.maven.MavenModuleSet DY-Classic-QA-US-trunk MissingFieldException: No field ‘perModuleEmail’ found in class ‘hudson.maven.MavenModuleSet’
hudson.maven.MavenModuleSet UK-Classic-E2E-C1-Regression MissingFieldException: No field ‘perModuleEmail’ found in class ‘hudson.maven.MavenModuleSet’
hudson.maven.MavenModuleSet CI-QE-FTU-Regression MissingFieldException: No field ‘perModuleEmail’ found in class ‘hudson.maven.MavenModuleSet’
hudson.maven.MavenModuleSet US-Classic-E2E-C4-Regression MissingFieldException: No field ‘perModuleEmail’ found in class ‘hudson.maven.MavenModuleSet’
hudson.maven.MavenModuleSet CI-QE-IPD-Smoke MissingFieldException: No field ‘perModuleEmail’ found in class ‘hudson.maven.MavenModuleSet’
Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn

rajeshkumar replied the topic: Jenkins Upgrade and Solution!!!
Solution 3: Post upgrade, you will find under “Manage Jenkins” sections
It appears that your reverse proxy set up is broken.

If you see the error message “It appears that your reverse proxy set up is broken” in the “Manage Jenkins” page, here’s what’s happening.

For a reverse proxy to work correctly, it needs to rewrite both the request and the response. Request rewriting involves receiving an inbound HTTP call and then make a forwarding request to Jenkins (sometimes with some HTTP headers modified, sometimes not.) Failing to configure the request rewriting is easy to catch, because you just won’t see any pages at all.

But proper reverse proxying also involves rewriting response. The primary place where this needs to happen is the “Location” header in the response, which is used during redirects. Jenkins would send back “Location: actual.server:8080/jenkins/foobar ” and the reverse proxy needs to rewrite this to “Location: nice.name/jenkins/foobar “. Unfortunately, failing to configure this correctly is harder to catch.

So Jenkins has a proactive monitoring to make sure this is configured correctly. It uses XmlHttpRequest to request a specific URL in Jenkins (via relative path, so this will always get through provided the request is properly rewritten), which will then redirect the user to another page in Jenkins (this works correctly only if you got the reponse rewriting configured correctly), which then returns 200.

This error message indicates that this test is failing. The most likely cause is that you got the response rewriting incorrectly done. See Running Jenkins behind Apache for additional tips about reverse proxy. While the page talks primarily about Apache, it has some information that applies to other reverse proxies.

For further diagnosis, try wget –no-check-certificate –debug -O /dev/null your.reverse.proxy/jenkins/administrativ…oxySetupMonitor/test (assuming your Jenkins should be visible at your.reverse.proxy/jenkins/ )

or using cURL:

curl -iL your.reverse.proxy/jenkins/administrativ…oxySetupMonitor/test
Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn

The post Jenkins Upgrade and Solution!!! appeared first on scmGalaxy.

-Rajesh

The post CLOC Jenkins PLUGINS? appeared first on scmGalaxy.

Sol
# yum clean dbcache
# yum update

and you are done.
Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn

The post Solution for database disk image is malformed during jenkins install appeared first on scmGalaxy.

BUILD_STATUS=$(curl --user USER:TOKEN_VALUE --silent $BUILD_URLapi/json | jq -r '.result')
echo $BUILD_STATUS

Using jenkins Plugins
Plugins Name – Conditional Build Step

For Implementations, Please check here.
https://stackoverflow.com/questions/11125598/getting-the-build-status-in-post-build-script

Using Python & Json

</pre>
#!/usr/bin/python
#
# author: ajs
# license: bsd
# copyright: re2

import json
import sys
import urllib
import urllib2

jenkinsUrl = "https://jenkins.example.com/job/"

if len( sys.argv ) > 1 :
jobName = sys.argv[1]
jobNameURL = urllib.quote(jobName)
else :
sys.exit(1)

try:
jenkinsStream = urllib2.urlopen( jenkinsUrl + jobNameURL + "/lastBuild/api/json" )
except urllib2.HTTPError, e:
print "URL Error: " + str(e.code)
print " (job name [" + jobName + "] probably wrong)"
sys.exit(2)

try:
buildStatusJson = json.load( jenkinsStream )
except:
print "Failed to parse json"
sys.exit(3)

if buildStatusJson.has_key( "result" ):
print "[" + jobName + "] build status: " + buildStatusJson["result"]
if buildStatusJson["result"] != "SUCCESS" :
exit(4)
else:
sys.exit(5)

sys.exit(0)

Reference -
<a href="http://serverfault.com/questions/309848/how-can...49988bb53ee820fe202a">serverfault.com/questions/309848/how-can...49988bb53ee820fe202a</a>
<pre>

The post Script to check the build status of a Jenkins job appeared first on scmGalaxy.

The post Jenkins plugin list sometimes shows up empty appeared first on scmGalaxy.