DEV Community

Jenkins Pipelines and their dirty secrets 3.

Richard Lenkovits on August 02, 2017

Tips and Tricks of Pipelines How did this chapter come to be? I was basically just pasting here stuff during work. There are many subtle...

Read full post

YangFeng • Nov 29 '17

Hi, Pencillr. Thanks for sharing very useful tips about pipeline in your article. Do you have any idea about getting all names of stage before they have been executed? I mean, how to get all the defined stages' name in the beginning of Jenkinfile?

Richard Lenkovits • Nov 29 '17

Hi, thank you. I don't know of any way that would get you the name of the stages before the stages run, in the Jenkinsfile. Although you could do several things to have the stage names beforehand.
First, you could instantiate a list with the names of the stages at the beginning, and you could reference the elements of it at the stage declaration.

YangFeng • Nov 30 '17

Thanks for your reply. I think I understand what you mean, a parameters{} block or a input method is feasible.

mdali_11 • Nov 27 '18 • Edited

Is there a way to check the whether Build A is running or not, If Build A running
Build B should be wait until this Build A has to complete, and then Build B has to complete its build, the pipeline to check the Build A is in Build B.....

vamsi krishna • Apr 16 '18

Hi Pencillr, Thanks alot for the post. I have one requirement where I have to trigger 2nd stage in pipeline at different time and date after the initial stage. Can you please help me if you have any suggestions?

Benjamin Paz • Aug 13 '18

Did you ever figure out how to trigger 2nd stage in pipeline?

I also have a requirement to trigger just a stage in Jenkinsfile pipeline. This stage should only run daily but all other stages triggered by a code push. Any ideas?

Paweł Kowalski • Dec 21 '18

Have the same case, no luck so far.

Casey Vega • Feb 5 '19 • Edited

Use what is known as a parameterized pipeline. You can set default environment variables for code runs.

when you want to change the behavior of the pipeline stage you can modify the parameter. If you set the toggle parameter to false in the UI, or by calling the build via URL, it will now skip the first stage because it's not true

Calling via URL:
http://server/job/project/buildWithParameters?toggle=false

pipeline {
  agent any
  parameters {
    booleanParam(name: 'toggle', defaultValue: true)
  }
  stages {
    stage('optional stage') {
      when (toggle: true) {
        sh `make clean`
      }
    }
  }
}

Danis Nya • Nov 20 '18

Hi, Pencillr!
Thanks a lot for your tips, it is really useful. I have two question:

When i execute my stages in parallel, job do not stopped when 1 of 2 stages is fail. How can i fix it?
How can i sorted my logs in parallel execution?

Best regards.

Lewis Evans • Sep 9 '19 • Edited

for #1. you can do

parallel (
    "Unit Test" : {
        build("unit-test-job")
    },
    "Component Test" : {
        build("component-test-job")
    },
    "Build" : {
        build("build-job")
    },
    failFast: true
)

for #2. Not sure you can do that unless you run sequentially

Monika1312 • Dec 3 '18

Hi Pencillr, Thanks for this post.
I have one question.
I understood the use of propagate: false but how to show the stage as fail/red when something is actually failed. My job is failed and shows as green and I don't want to go and click every time inside the stage result.

Benjamin Paz • Aug 13 '18

Hi Pencillr, I would like to trigger just a pipeline stage in Jenkinsfile. This stage should only run daily but all other stages triggered by a code push. Any ideas?

Gustavo • Feb 27 '20

Great and very useful tips.
Thank you, Richard!!!