1. What is a Jenkins pipeline?

a) A coding script used to automate software development
b) A graphical user interface for managing Jenkins jobs
c) A tool used to manage Jenkins plugins
d) All of the above

Answer: a)

2. What is the difference between declarative and scripted pipelines?

a) Declarative pipelines use a predefined set of steps, while scripted pipelines allow users to write custom scripts.
b) Declarative pipelines use a graphical user interface, while scripted pipelines are coded by hand.
c) Declarative pipelines support parallelism and stage-level error handling, while scripted pipelines do not.
d) Declarative pipelines are deprecated in favor of scripted pipelines.

Answer: a)

3. What is the purpose of the “agent” directive in a Jenkins pipeline?

a) To specify the location where the pipeline is run
b) To define the steps that make up the pipeline
c) To specify the credentials used to run the pipeline
d) To set environment variables for the pipeline

Answer: a)

4. How do you define a parameter in a Jenkins pipeline?

a) Using the “parameters” directive
b) Using the “property” directive
c) Using the “input” directive
d) Parameters cannot be defined in a Jenkins pipeline

Answer: a)

5. What is a Jenkinsfile?

a) A file that defines a Jenkins pipeline
b) A file that stores Jenkins plugin configurations
c) A file that contains the results of a Jenkins build
d) A file that defines Jenkins global variables

Answer: a)

6. How do you specify a conditional statement in a Jenkins pipeline?

a) Using the “if” directive
b) Using the “when” directive
c) Using the “switch” directive
d) Conditional statements cannot be used in a Jenkins pipeline

Answer: a)

7. What is the purpose of the “input” directive in a Jenkins pipeline?

a) To pause the pipeline and wait for user input
b) To define parameters for the pipeline
c) To specify the location where the pipeline is run
d) To set environment variables for the pipeline

Answer: a)

8. How do you trigger a downstream job in a Jenkins pipeline?

a) Using the “build” directive
b) Using the “trigger” directive
c) Using the “stage” directive
d) Downstream jobs cannot be triggered in a Jenkins pipeline

Answer: a)

9. What is the purpose of the “stage” directive in a Jenkins pipeline?

a) To define steps that make up the pipeline
b) To group pipeline steps into stages
c) To define environment variables for the pipeline
d) To specify the location where the pipeline is run

Answer: b)

10. What is the purpose of the “when” directive in a Jenkins pipeline?

a) To define parallelism in the pipeline
b) To specify conditions that must be met before a step can run
c) To trigger downstream jobs
d) To define custom functions used in the pipeline

Answer: b)

11. How do you define environment variables in a Jenkins pipeline?

a) Using the “properties” directive
b) Using the “pipeline” directive
c) Using the “env” directive
d) Environment variables cannot be defined in a Jenkins pipeline

Answer: c)

12. What is the “stash” and “unstash” commands in Jenkins?

a) Commands used for version control in Jenkins
b) Commands used to archive files in Jenkins
c) Commands used to share files between nodes in a Jenkins pipeline
d) Commands used to install plugins in Jenkins

Answer: c)

13. What is the purpose of the “noStash” directive in a Jenkins pipeline?

a) To ignore archived files during the pipeline run
b) To force files to be archived during the pipeline run
c) To exclude specific stages from the pipeline run
d) The “noStash” directive is not a valid directive in a Jenkins pipeline

Answer: a)

14. What is the “sh” and “bat” commands in Jenkins?

a) Commands used to switch between operating systems in Jenkins
b) Commands used to execute shell scripts and batch files in Jenkins
c) Commands used to archive files in Jenkins
d) Commands used to share files between nodes in a Jenkins pipeline

Answer: b)

15. How do you create a custom function in a Jenkins pipeline?

a) Using the “function” directive
b) Using the “script” directive
c) Custom functions cannot be used in a Jenkins pipeline
d) Using the “plugin” directive

Answer: b)

16. What is the “timeout” directive in a Jenkins pipeline?

a) A directive used to specify the maximum time a step can run before timing out
b) A directive used to pause the pipeline for a specified amount of time
c) A directive used to specify the maximum time the pipeline can run before timing out
d) The “timeout” directive is not a valid directive in a Jenkins pipeline

Answer: a)

17. How do you trigger a Jenkins pipeline using a webhook?

a) Using the Jenkins API
b) Using the “webhook” directive
c) Using a Jenkins plugin
d) Triggering a Jenkins pipeline via webhook is not possible

Answer: a)

18. What is a “floating point” in a Jenkins pipeline?

a) A directive used for floating point arithmetic
b) A Jenkins plugin used for real-time monitoring
c) A Jenkins feature used for dynamic scaling of resources
d) Floating point is not a valid concept in a Jenkins pipeline

Answer: d)

19. What is the purpose of the “post” directive in a Jenkins pipeline?

a) To define cleanup steps that should be run after the pipeline completes
b) To define steps that make up the pipeline
c) To group pipeline steps into stages
d) The “post” directive is not a valid directive in a Jenkins pipeline

Answer: a)

20. What is the purpose of the “tools” directive in a Jenkins pipeline?

a) To specify the tools needed for the pipeline
b) To define custom functions used in the pipeline
c) To group pipeline steps into stages
d) Tools cannot be specified in a Jenkins pipeline

Answer: a)

21. What is the “archiveArtifacts” command in Jenkins?

a) A command used to archive artifacts generated during the pipeline run
b) A command used to deploy artifacts to a remote location
c) A command used to run tests on artifacts generated during the pipeline run
d) The “archiveArtifacts” command is not a valid command in Jenkins

Answer: a)

22. What is the “environment” directive in a Jenkins pipeline?

a) A directive used to define environment variables used by the pipeline
b) A directive used to set the location where the pipeline is run
c) A directive used to specify the tools needed for the pipeline
d) The “environment” directive is not a valid directive in a Jenkins pipeline

Answer: a)

23. What is the “parallel” directive in a Jenkins pipeline?

a) A directive used to define parallelism in the pipeline
b) A directive used to set environment variables for the pipeline
c) A directive used to group pipeline steps into stages
d) The “parallel” directive is not a valid directive in a Jenkins pipeline

Answer: a)

24. What is the “buildDiscarder” directive in a Jenkins pipeline?

a) A directive used to define how long builds should be stored in the pipeline history
b) A directive used to trigger downstream jobs
c) A directive used to archive artifacts generated during the pipeline run
d) The “buildDiscarder” directive is not a valid directive in a Jenkins pipeline

Answer: a)

25. How do you define a global variable in a Jenkins pipeline?

a) Using the “globals” directive
b) Using the “properties” directive
c) Using the “global” directive
d) Global variables cannot be defined in a Jenkins pipeline

Answer: d)

26. What is the “retry” command in Jenkins?

a) A command used to retry a failed step in the pipeline
b) A command used to retry the entire pipeline
c) A command used to retry a downstream job
d) The “retry” command is not a valid command in Jenkins

Answer: a)

27. What is the purpose of the “parameters” directive in a Jenkins pipeline?

a) To define parameters used by the pipeline
b) To specify the location where the pipeline is run
c) To group pipeline steps into stages
d) The “parameters” directive is not a valid directive in a Jenkins pipeline

Answer: a)

28. What is the “cron” command in Jenkins?

a) A command used to trigger a pipeline at a specified time
b) A command used to set environment variables for the pipeline
c) A command used to pause the pipeline for a specified amount of time
d) The “cron” command is not a valid command in Jenkins

Answer: a)

29. What is the “fileExists” command in Jenkins?

a) A command used to test whether a file exists
b) A command used to create a file
c) A command used to archive a file
d) The “fileExists” command is not a valid command in Jenkins

Answer: a)

30. What is the “timestamps” command in Jenkins?

a) A command used to add timestamps to pipeline output
b) A command used to set the location where the pipeline is run
c) A command used to trigger downstream jobs
d) The “timestamps” command is not a valid command in Jenkins

Answer: a)

31. What is the “node” directive in a Jenkins pipeline?

a) A directive used to specify the node where the pipeline is run
b) A directive used to group pipeline steps into stages
c) A directive used to define custom functions used in the pipeline
d) The “node” directive is not a valid directive in a Jenkins pipeline

Answer: a)

32. What is the “params” variable in a Jenkins pipeline?

a) A variable that contains the parameters passed to the pipeline
b) A variable used to store custom programming functions
c) A variable used to store environment variables
d) The “params” variable is not a valid variable in a Jenkins pipeline

Answer: a)

33. What is the “dir” command in Jenkins?

a) A command used to change the working directory in the pipeline
b) A command used to deploy artifacts to a remote location
c) A command used to trigger downstream jobs
d) The “dir” command is not a valid command in Jenkins

Answer: a)

34. What is the “stashSize” directive in a Jenkins pipeline?

a) A directive used to specify the maximum size of archived files
b) A directive used to specify the number of files to archive
c) A directive used to set environment variables for the pipeline
d) The “stashSize” directive is not a valid directive in a Jenkins pipeline

Answer: a)

35. What is the purpose of the “retryWhen” directive in a Jenkins pipeline?

a) To specify the conditions under which a step should be retried
b) To specify the maximum number of times a step should be retried
c) To specify the duration between retries of a failed step
d) The “retryWhen” directive is not a valid directive in a Jenkins pipeline

Answer: a)

36. What is the purpose of the “results” directive in a Jenkins pipeline?

a) To specify the location where the pipeline is run
b) To set environment variables for the pipeline
c) To define cleanup steps that should be run after the pipeline completes
d) The “results” directive is not a valid directive in a Jenkins pipeline

Answer: c)

37. What is the “confirm” command in Jenkins?

a) A command used to pause the pipeline and wait for user input
b) A command used to run tests on artifacts generated during the pipeline run
c) A command used to intelligently retry failed steps in the pipeline
d) The “confirm” command is not a valid command in Jenkins

Answer: a)

38. What is the “mail” command in Jenkins?

a) A command used to send email notifications at a specified stage of the pipeline
b) A command used to archive artifacts generated during the pipeline run
c) A command used to run tests on artifacts generated during the pipeline run
d) The “mail” command is not a valid command in Jenkins

Answer: a)

39. What is the “git” command in Jenkins?

a) A command used to integrate with Git for version control
b) A command used to deploy artifacts to a remote location
c) A command used to archive artifacts generated during the pipeline run
d) The “git” command is not a valid command in Jenkins

Answer: a)

40. What is the purpose of the “inputMessage” directive in a Jenkins pipeline?

a) To define the message displayed when the pipeline is paused for user input
b) To define the message included in email notifications
c) To define a custom error message for failed pipeline steps
d) The “inputMessage” directive is not a valid directive in a Jenkins pipeline

Answer: a)

41. What is the “postBuild” directive in Jenkins?

a) A directive used to define cleanup steps that should be run after the pipeline completes
b) A directive used to specify the location where the pipeline is run
c) A directive used to define custom functions used in the pipeline
d) The “postBuild” directive is not a valid directive in Jenkins

Answer: a)

42. What is the “ignoreErrors” command in Jenkins?

a) A command used to ignore errors during the pipeline run
b) A command used to archive artifacts generated during the pipeline run
c) A command used to pause the pipeline for a specified amount of time
d) The “ignoreErrors” command is not a valid command in Jenkins

Answer: a)

43. What is the “step” command in Jenkins?

a) A command used to define steps in the pipeline
b) A command used to store environment variables
c) A command used to pause the pipeline for a specified amount of time
d) The “step” command is not a valid command in Jenkins

Answer: a)

44. What is the purpose of the “withAnt” directive in a Jenkins pipeline?

a) To specify the Ant version used by the pipeline
b) To set environment variables for the pipeline
c) To archive artifacts generated during the pipeline run
d) The “withAnt” directive is not a valid directive in a Jenkins pipeline

Answer: a)

45. What is the “batLabel” command in Jenkins?

a) A command used to trigger a downstream job on a specified label
b) A command used to deploy artifacts to a remote location
c) A command used to run batch files in the pipeline
d) The “batLabel” command is not a valid command in Jenkins

Answer: c)

46. What is the “try” command in Jenkins?

a) A command used to retry failed steps in the pipeline
b) A command used to run tests on artifacts generated during the pipeline run
c) A command used to archive artifacts generated during the pipeline run
d) The “try” command is not a valid command in Jenkins

Answer: a)

47. What is the purpose of the “unstable” result in Jenkins?

a) To indicate that the pipeline completed but with some issues
b) To indicate that the pipeline failed
c) To indicate that the pipeline has not yet completed
d) The “unstable” result is not a valid concept in Jenkins

Answer: a)

48. What is the “file” command in Jenkins?

a) A command used to create a file in the pipeline
b) A command used to patch a file during the pipeline run
c) A command used to delete a file during the pipeline run
d) The “file” command is not a valid command in Jenkins

Answer: a)

49. What is the purpose of the “stashExists” command in Jenkins?

a) To test whether a specific stash exists
b) To create a stash
c) To store a stash on a remote node
d) The “stashExists” command is not a valid command in Jenkins

Answer: a)

50. What is the purpose of the “properties” directive in a Jenkins pipeline?

a) To set environment variables for the pipeline
b) To define custom functions used in the pipeline
c) To define parameters used by the pipeline
d) To define cleanup steps that should be run after the pipeline completes

Answer: a)

The post Top 50 Jenkin Pipeline Interview Questions with Answers 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.

Enabling jenkins integration with silk central test manager

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

if [ -n "$job_status" ] then     # Run your script commands here else   echo "BUILD FAILURE: Other build is unsuccessful or status could not be obtained."   exit 1 fi

The post Jenkins Remote access API Example | Jenkins Tutorial appeared first on scmGalaxy.

Environment variables and properties defined in jenkins

Jenkins Set Environment Variables

When a Jenkins job executes, it sets some environment variables that you may use in your shell script, batch command, Ant script or Maven POM 1. The following table contains a list of all of these environment variables.

Promoted Build Plugin Environment Variables

If you are using the Promoted Build Plugin, you will have access to the following environment variables. This allows you to access information about your Jenkins build since certain environment variables stated above (such as BUILD_TAG now refer to the Promoted Build Plugin’s job.

System Properties

Environment Variables

Plugins

Useful Plugins

https://wiki.jenkins-ci.org/display/JENKINS/EnvInject+Plugin

Reference

https://wiki.jenkins-ci.org/display/JENKINS/Building+a+software+project
http://jenkins:8080/systemInfo

The post Environment variables and properties defined in jenkins | Jenkins Tutorial appeared first on scmGalaxy.

The post Complete guide to use Jenkins CLI / Command line | Jenkins Tutorials appeared first on scmGalaxy.

If you are using wget 1.11 against Jenkins version 1.586 and above with the JENKINS-25169 fix, you might need to use the following options:
wget –auth-no-challenge –http-user=user –http-password=apiToken –secure-protocol=TLSv1 http://jenkins.yourcompany.com/job/your_job/build?token=TOKEN

If you are using wget 1.11, you might need to use the following options:
wget –auth-no-challenge –http-user=user –http-password=apiToken http://jenkins.yourcompany.com/job/your_job/build?token=TOKEN

With wget 1.10.x the following is enough (but will not work with 1.11.x) :
wget http://user:apiToken@jenkins.yourcompany.com/job/your_job/build?token=TOKEN

If you are a Windows User!

‘gitbash’ is a program combined of git and bash. A bash is shell that runs commands once you type the name of command and press enter.

Download  the git bash from here https://git-scm.com/download/win and install it.

The post How to Trigger builds remotely in Jenkins? | Jenkins Tutorials | scmGalaxy appeared first on scmGalaxy.

The post Generate Jenkins Job Configuration Automatically | Jenkins Tutorials appeared first on scmGalaxy.

$ apt-get install docker (Ubuntu)
$ yum install docker  (RHEL/CENTOS)

$ docker pull jenkins 

$ docker run -d -p 8080:8080 -p 50000:50000 jenkins 

$ docker run -d -p 8080:8080 -p 50000:50000 -u root -v $PWD/jenkins:/var/jenkins_home jenkins 

docker run -d -p 49001:8080 -v $PWD/jenkins:/var/jenkins_home -t jenkins -u root 

$ mkdir jenkins
$ chown 1000 jenkins
$ docker run -d -p 49001:8080 -v $PWD/jenkins:/var/jenkins_home -t jenkins

$ docker exec name tail -f /var/log/jenkins/jenkins.log
Where name = --name 

The post How to Install Jenkins using Docker | Step by step guide | scmGalaxy appeared first on scmGalaxy.

The post Jenkins useful websites references | Jenkins Resources | scmGalaxy appeared first on scmGalaxy.

The post How to attach the jenkins build log as part of the email body? appeared first on scmGalaxy.

How Do I Backup Jenkins Jobs using Grunt?

Backup Jenkins configuration to S3

bash-backup-script for jenkins‘ job-configs via user-crontab

Backup and restore Jenkins using jenkins plugins

The post Jenkins Backup and Restore Process | Jenkins Tutorial appeared first on scmGalaxy.

Way 1 – 

Put following lines as part of Default Content text box

${BUILD_LOG, maxLines=9999, escapeHtml=false}

this works for free style projects

Way 2 – If you want send only specific line using regex

${BUILD_LOG_REGEX, regex=”\\b(Buildfile|BUILD)\\b”, linesAfter=1}

${BUILD_LOG_REGEX, regex=”^.*?BUILD FAILED.*?$”, linesBefore=0, linesAfter=10, maxMatches=5, showTruncatedLines=false, escapeHtml=true}

${BUILD_LOG_REGEX, regex=”\\b(FC0)\\b”, linesAfter=1}

${BUILD_LOG_REGEX, regex=”^.*?BUILD FAILED.*?$”, linesBefore=0, linesAfter=10, maxMatches=5, showTruncatedLines=false, escapeHtml=true}

${BUILD_LOG_REGEX, regex=”^.*?FC0.*?$”, maxMatches=95, showTruncatedLines=false, escapeHtml=false, matchedLineHtmlStyle=true}

This will show exactly which is expected lines as part of the regEx.

More Info

http://wiki.hudson-ci.org/display/HUDSON/Email-ext+plugin

http://stackoverflow.com/questions/9439450/how-will-i-filter-out-only-errors-in-jenkins-email-ext-build-log-regex

http://champasoft.blogspot.nl/2012/11/jenkins-pattern-for-e-mailing-log.html

The post How to attach the jenkins build log as part of the email body? appeared first on scmGalaxy.

Solution 1

In Windows: Go to environment variable and add following variables

export JAVA_OPTS=”-XX:MaxPermSize=512m -Xms512m -Xmx1024m”
export GRADLE_OPTS=”-XX:MaxPermSize=512m”
export SONAR_RUNNER_OPTS=”-Xmx512m -XX:MaxPermSize=512m”

In Linux:
In my ~/.bash_profile file, I have set the following 3 variables. Note there are other variables in this file as well i.e. JAVA_HOME, ANT_HOME, SONAR_HOME, SONAR_RUNNER_HOME, etc:

export JAVA_OPTS=”-XX:MaxPermSize=512m -Xms512m -Xmx1024m”
export GRADLE_OPTS=”-XX:MaxPermSize=512m”
export SONAR_RUNNER_OPTS=”-Xmx512m -XX:MaxPermSize=512m”

Solution 2
You can set the -Xmx or -XX:MaxPermSize in your Jenkins global configuration. To do this, navigate to Jenkins global configuration page (Manage Jenkins -> Configure System)

Name – JAVA_OPTS
Value – “-XX:MaxPermSize=512m -Xms512m -Xmx1024m”

You can set similarlity for maven, gradle, sonar as well under “Maven Project Configuration” or grade project configuration.

Name – GRADLE_OPTS
Value – “-XX:MaxPermSize=512m”

Solution 3

They way you can modify this value depends on the distribution and depending on the slave type

Master

In RedHat, for example, you can do it under /etc/sysconfig/jenkins using the variable JENKINS_JAVA_OPTIONS… i.e JENKINS_JAVA_OPTIONS=”-XX:MaxPermSize=512m”.
In Ubuntu, the Jenkins configuration file is under /etc/default/jenkins and the variable to configure is JAVA_ARGS … i.e JAVA_ARGS=”-XX:MaxPermSize=512m”.

Slave

Sometimes slave machines will require permgen to be increased. Depending on the type of slave that is configured will require a different method for setting any java argument.

With SSH Slaves, the java process is started using an SSH command, so the “-XX:MaxPermSize=512m” can be set in the JVM Options in the Node configuration page.
With JNLP Slaves launching as a service on linux, you can add the VM arguments to the startup scripts (usually in /etc/sysconfig/jenkins or /etc/default/jenkins as part of the JAVA_ARGS variable)
With JNLP Slaves launching as a service on Windows requires modifications to be made on the jenkins.xml file which is located on slave machine in the JENKINS_HOME directory.

Reference
http://stackoverflow.com/questions/18000841/jenkins-java-lang-outofmemoryerror-permgen-space
https://wiki.jenkins-ci.org/display/JENKINS/Builds+failing+with+OutOfMemoryErrors
https://cloudbees.zendesk.com/hc/en-us/articles/204264000-Why-do-I-receive-java-lang-OutOfMemoryError-PermGen-space
http://stackoverflow.com/questions/14762162/how-do-i-give-jenkins-more-heap-space-when-its-running-as-a-daemon-on-ubuntu
http://stackoverflow.com/questions/18000841/jenkins-java-lang-outofmemoryerror-permgen-space
http://javarevisited.blogspot.nl/2011/09/javalangoutofmemoryerror-permgen-space.html
https://plumbr.eu/outofmemoryerror/permgen-space

The post How to Resolve jenkins java.lang.outofmemoryerror permgen space issues? appeared first on scmGalaxy.

Jenkins Troubleshooting

Jenkins is one of the important CI tools which many organization used as part of their Build and DevOps infrasture. I am going to consolidate all the troubshooting techniques which can be used in order to find any issues related in jenkins.

Step 1. Take a look at Log generated by the jenkins and plugins via http://jenkins-master/log

Note: Here you can also create your own logger and and set your custom log levels such as (severe, warning, info, config, file, finer, finest, all)

Step 2. Also, you can look at /var/log/jenkins/jenkins.log via doing “tail -f /var/log/jenkins/jenkins.log” and check carefully whats breaking it.

Log file in windows – jenkins.err.log & jenkins.out.log

Slave log file in windows – logs\slaves

Step 3. Check the system log file

Step 4. Few Jenkins plugins which can you help you
https://wiki.jenkins-ci.org/display/JENKINS/Monitoring

Step 4. Make sure your Jenkins & installed plugins version is installed with most uptodate stable release.

Some Common issues:
Issues 1. If Jenkins hangs, follow https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+is+hanging

Issues 2 Site is down with no 404 messages
Cause- Jenkins had an Out of Memory (OOM) error causing the server to kill the jenkins instance
Solution: Restart server; Review heap logs to identify root cause of error

Issues 3 Site is up however no jobs are displayed
Cause 1: AWS Server rebooted but data volume did not mount properly
Solution: mount <device> <path> on the instance

Issues 4 – java.lang.outofmemoryerror permgen space issues

Solution – http://www.scmgalaxy.com/scm/build-workflow-management/jenkins/jenkins-java-lang-outofmemoryerror-permgen-space-issues.html

The post Jenkins Troubleshooting Guide appeared first on scmGalaxy.

Grep will return 0 while the build is running:

$ curl http://myjenkins/job/myjob/lastBuild/api/json | grep –color result\”:null

$ echo $?

Trigger a Jenkins Job from command line

$ wget http://yourserver/job/MyJobname/build?delay=0sec

$ wget -O – $HUDSON_URL/job/JOBNAME/build

Trigger a Jenkins Job without authentication

$ curl http://jenkins:8080/job/my%20job/build

Trigger a Jenkins Job with authentication

$ curl –user dbacher:$MY_API_TOKEN http://jenkins:8080/job/my%20job/build

$ curl –user <your_jenkins_username>:<your_jenkins_API_key> http://<jenkins_server_url>/job/<your_jenkins_job_name>/build

Running commands against a secure Jenkins (basic auth or ssh keys)

$ java -jar jenkins-cli.jar -s http://myjenkins help –username me –password mypassword

$ java -jar jenkins-cli.jar -s http://myjenkins help -i ~/.ssh/id_rsa

Triggering a job build against a secure Jenkins (avoiding a 1.5 year old open bug!)

$ java -jar jenkins-cli.jar -s http://myjenkins build ‘My Awesome Jenkins Job’ -i ~/.ssh/id_rsa

$ java -jar jenkins-cli.jar -s http://myjenkins build ‘My Awesome Jenkins Job’ -i ~/.ssh/id_rsa -s -v

Passing parameters when triggering a job build

$ java -jar jenkins-cli.jar -s http://myjenkins build ‘Deploy XYZ App’ -i ~/.ssh/id_rsa -s -v -p target_env=api.cloudfoundry.com -p branch=master

Reference

http://starkandwayne.com/articles/2013/04/12/jenkins-builds-from-cli/

http://www.scmgalaxy.com/index.php?option=com_k2&view=item&id=890:ways-to-login-jenkins-using-command-line&Itemid=120

Appendix

1. How to get your_jenkins_API_key?

• Login to your Jenkins.
• Click on the username in the top right.
• Click on Configure.
• Click on ‘Show API Token’ button.
• You got it.

The post Jenkins Command line Reference for login and trigger a job appeared first on scmGalaxy.