jenkins-pipeline

I've recently moved to the Pipeline plugin in Jenkins. I've successfully used freestyle jobs before for my project, but now would like to test something new. My project builds for Windows and Linux, in release and in debug mode, and uses a parameter, called device , to configure some C preprocessor macros: globally #define d frame_width and frame_height differ, depending on device value. Here is my Jenkinsfile: def device_config(device) { def device_config = ""; switch(device) { case ~/^dev_[Aa]$/: device_config="""-DGLOBAL_FRAME_WIDTH=640\ -DGLOBAL_FRAME_HEIGHT=480""" break; case ~/^dev_[Ss]$

To explain the issue, consider that I have 2 jenkins jobs. Job1 : PARAM_TEST1 it accepts a parameterized value called 'MYPARAM' Job2: PARAM_TEST2 it also accepts a parameterized value called 'MYPARAM' Sometimes I am in need of running these 2 jobs in sequence - so i created a separate pipeline job as shown below. It works just fine. it also accepts a parameterized value called 'MYPARAM' to simply pass it to the build job steps. pipeline { agent any stages { stage("PARAM 1") { steps { build job: 'PARAM_TEST1', parameters: [string(name: 'MYPARAM', value: "${params.MYPARAM}")] } } stage("PARAM 2"

Is there an environment variable that captures the downstream job's build number ? I am using build step in pipeline as code. Not an environment variable, but an object property: downstreamBuild = build 'myDownstreamJob' downstreamBuildNumber = downstreamBuild.rawBuild.id Note that you will either need to disable the Groovy sandbox or get script approvals in order to use rawBuild . Also, you cannot use wait: false with your build step, since build() returns null when called with wait: false . 来源： https://stackoverflow.com/questions/46352379/capture-build-number-of-downstream-job-in-jenkins

I've created Jenkins Pipline job and want it to be triggered on my GitHub repo push event. I've added repo url to job config and checked "trigger on push option": I've also added GitHub token with needed rights to jenkins configure Github section: In Github repo I've enabled webhook for my Jenkins server: And after all steps still nothing is triggered after push to my GitHub repo. Does anyone have any idea what's going on and why Jenkins doesn't trigger configured pipeline job? Solution mentioned by OP in a comment is correct. Assuming you have a Github webhook for your Jenkins set up

I have a Jenkins pipeline template which uses a Jenkins file in Subversion. The Jenkins file has the svn checkout method to check out the real application. (The svn url of real application is passed from jenkins env variables) I need to do the svn polling of the real application and trigger the job when there is a change in real application. When I use the polling option in jenkins template , it always do the polling of JenkinsFile in Subversion. Is there any way that I can poll the real application? Use a freestyle job to poll (with depth empty) your real application via svn. In this

I have a Pipeline job that checkouts a git repository (let's call is "repoA") and passes it to some other downstream jobs for further processing. The upstream job's script is stored in a different git repo (let's call it "repoB"). This job is configured with the "Poll SCM" option so that any changes to repoA will trigger it. In the pipeline section, I have selected the "Pipeline script from SCM" option and configured it to get the pipeline script from the master branch of repoB. I have also added the option "Don't trigger a build on commit notifications". The behavior that I'm expecting is

We have successfully set up a build pipeline using the Jenkins Multibranch Pipeline Plugin, which works great most of the time, but we have this problem which nags us: The Jenkinsfile contains a set of properties, and these also show up in the UI, but how can I set up default values for individual branches? This is how the properties definitions look like in our Jenkinsfile : properties([ parameters([ string(defaultValue: 'somevalue', description: 'Some description', name: 'SOME_VALUE'), string(defaultValue: 'asdfasdfasdfasdfdasdasdasdasd...', description: 'Client ID', name: 'TEST_CLIENT_ID'),

By using jenkins, I create an item of "Pipeline" type. And I set "Pipeline from SCM" to get Jenkinsfile . You can check my GitHub repository : I want use Jenkins pipeline to build a docker image. Here is the Jenkinsfile: node { sh "docker build -t 192.168.59.224:5000/ubuntu-test ." } The Dockerfile is also very simple: FROM ubuntu:14.04 RUN sudo apt-get update && sudo apt-get install -y wget When I run the project. I got following error: unable to prepare context: unable to evaluate symlinks in Dockerfile path: lstat /var/jenkins_home/workspace/test/Dockerfile: no such file or directory Here