jenkins-pipeline

I'm executing this code: node('my_windows_slave') { sh 'ls' } In my Windows slave I can properly execute sh command: But the pipeline script can't run the .sh file: [Pipeline] sh [D:\workspace\sandbox_pipeline] Running shell script sh: D:\workspace\sandbox_pipeline@tmp\durable-2d7dd2f8\script.sh: command not found What I could notice is that this .sh file is not even created, once I tried with bat and worked fined. Any clue what could be the problem? [UPDATE] Jenkins somehow can't create the SH temporary file. Already checked the log, permissions, everything that came to my mind. I will leave

I'm trying to sync to Perforce in my pipeline script, but from the documentation I don't see a way to set the "workspace behavior", even though the plugin itself seems to have that capability . I want the "workspace" to be equivalent to the setting "Manual (custom view)" I can configure in the UI as described here . What parameters do I need to pass to the p4sync task to achieve that? You will need to use the full checkout DSL, the p4sync DSL is only basic. The easiest way is to use the snippet generator ( Pipeline Syntax link), select checkout: General SCM then Perforce Software from the SCM

I'm trying to get Jenkins' multibranch pipeline job to build tags in a similar manner to branches. In Jenkins 2.73 (not sure when the functionality was added), Multibranch projects can be configured to retrieve both branches and tags from the source repository. Initially I thought this would be perfect for my needs (my Jenkinsfile can now build development or production builds from the same place in Jenkins). Multibranch job with tags discovery configured I have the build process itself up and running quite happily with a scripted pipeline, however my issue is that whilst the branch jobs

I created a new Jenkins pipeline. The pipeline is (currently) parametrized with a single boolean option named VAR_A . My pipeline script is: node ('windows') { echo "$VAR_A" bat 'env' } When I manually build the project with VAR_A checked, "true" is echoed, as expected. The list of environment variables, however, does not show VAR_A=true . I am able to get env to show VAR_A if I wrap the call in a withEnv block: node ('windows') { echo "$VAR_A" withEnv(["VAR_A=$VAR_A"]) { bat 'env' } } I will more parameters than this, so specifying each parameter individually is not desired. Is there a way to

How do I report the stage in which a declarative pipeline failed? In the fail block, I want to get failedStage.name and report it (eventually to slack). pipeline { agent { label 'master'} stages { stage('Ok') { steps { echo 'do thing' } } stage('NotOK') { steps { sh 'make fail' } } } post { always { echo 'ok' } failure { echo 'Failed during Which Stage?' } } } Instead of adding post section in every stage, I found some solution that shouldn't be working in Declarative Pipeline from my point of view, but it does. All is you need is to override stage : def stage(String name, Closure cl) { echo