Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-64576

Missing information reported in status page when triggered parametrized build ( Build Section) is a pipeline job

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Minor
    • Resolution: Unresolved
    • Labels:
      None
    • Environment:
      Jenkins Version: 2.263.1
      Parametrized trigger Plugin Version : 2.39
    • Similar Issues:

      Description

      Let's compare how are reported a pipeline job and a freestyle job when they are triggered as parametrized build in the build section.

      In my example I have a freestyle job :

      test-parametrizedPlugin-main-job that calls 2 jobs one freestyle and one pipeline :

      • test-parametrizedPlugin-called-pipeline-job
      • test-parametrizedPlugin-called-freestyle-job

      In the status page of the job we see that the Subprojects part is OK but not the Downstream Projects part, the pipeline job is missing

      And if we look in the status page of the run we see that the Subprojects part for the pipeline job is missing

      Note that the 2 jobs were correctly started as we can see in the console log

        Attachments

          Activity

          merlindam Damien Merlin created issue -
          merlindam Damien Merlin made changes -
          Field Original Value New Value
          Attachment image-2021-01-08-17-59-57-586.png [ 53774 ]
          merlindam Damien Merlin made changes -
          Attachment image-2021-01-08-18-01-33-502.png [ 53775 ]
          merlindam Damien Merlin made changes -
          Description Let's compare how are reported a pipeline job and a freestyle job when they are triggered as parametrized build in the build section.

          In my example I have a job :

          test-parametrizedPlugin-main-job that calls jobs :
           * test-parametrizedPlugin-called-pipeline-job
           * test-parametrizedPlugin-called-freestyle-job

          !image-2021-01-08-17-37-12-357.png!!image-2021-01-08-17-36-24-862.png!

          In the status page of the job we see that the {color:#57d9a3}*Subprojects* {color}part is OK but not the *{color:#FF0000}Downstream Projects{color}* part

          !image-2021-01-08-17-44-05-561.png!

          And if we look in the status page of the run we see that the *{color:#de350b}Subprojects{color}* part for the pipeline job is missing

          !image-2021-01-08-17-49-39-541.png!
          Let's compare how are reported a pipeline job and a freestyle job when they are triggered as parametrized build in the build section.

          In my example I have a job :

          test-parametrizedPlugin-main-job that calls jobs :
           * test-parametrizedPlugin-called-pipeline-job
           * test-parametrizedPlugin-called-freestyle-job

          !image-2021-01-08-17-37-12-357.png!!image-2021-01-08-17-36-24-862.png!

          In the status page of the job we see that the {color:#57d9a3}*Subprojects* {color}part is OK but not the *{color:#ff0000}Downstream Projects{color}* part

          !image-2021-01-08-17-44-05-561.png!

          And if we look in the status page of the run we see that the *{color:#de350b}Subprojects{color}* part for the pipeline job is missing

          !image-2021-01-08-17-49-39-541.png!

          Note that the 2 jobs were correctly started as we can see in the console log

          !image-2021-01-08-18-01-33-502.png!
          merlindam Damien Merlin made changes -
          Description Let's compare how are reported a pipeline job and a freestyle job when they are triggered as parametrized build in the build section.

          In my example I have a job :

          test-parametrizedPlugin-main-job that calls jobs :
           * test-parametrizedPlugin-called-pipeline-job
           * test-parametrizedPlugin-called-freestyle-job

          !image-2021-01-08-17-37-12-357.png!!image-2021-01-08-17-36-24-862.png!

          In the status page of the job we see that the {color:#57d9a3}*Subprojects* {color}part is OK but not the *{color:#ff0000}Downstream Projects{color}* part

          !image-2021-01-08-17-44-05-561.png!

          And if we look in the status page of the run we see that the *{color:#de350b}Subprojects{color}* part for the pipeline job is missing

          !image-2021-01-08-17-49-39-541.png!

          Note that the 2 jobs were correctly started as we can see in the console log

          !image-2021-01-08-18-01-33-502.png!
          Let's compare how are reported a pipeline job and a freestyle job when they are triggered as parametrized build in the build section.

          In my example I have a freestyle job :

          test-parametrizedPlugin-main-job that calls 2 jobs one freestyle and one pipeline :
           * test-parametrizedPlugin-called-pipeline-job
           * test-parametrizedPlugin-called-freestyle-job

          !image-2021-01-08-17-37-12-357.png!!image-2021-01-08-17-36-24-862.png!

          In the status page of the job we see that the {color:#57d9a3}*Subprojects* {color}part is OK but not the *{color:#ff0000}Downstream Projects{color}* part

          !image-2021-01-08-17-44-05-561.png!

          And if we look in the status page of the run we see that the *{color:#de350b}Subprojects{color}* part for the pipeline job is missing

          !image-2021-01-08-17-49-39-541.png!

          Note that the 2 jobs were correctly started as we can see in the console log

          !image-2021-01-08-18-01-33-502.png!
          merlindam Damien Merlin made changes -
          Summary Missing information reported in status page when triggered parametrized build ( Build Section) is a pipeline Missing information reported in status page when triggered parametrized build ( Build Section) is a pipeline job
          merlindam Damien Merlin made changes -
          Description Let's compare how are reported a pipeline job and a freestyle job when they are triggered as parametrized build in the build section.

          In my example I have a freestyle job :

          test-parametrizedPlugin-main-job that calls 2 jobs one freestyle and one pipeline :
           * test-parametrizedPlugin-called-pipeline-job
           * test-parametrizedPlugin-called-freestyle-job

          !image-2021-01-08-17-37-12-357.png!!image-2021-01-08-17-36-24-862.png!

          In the status page of the job we see that the {color:#57d9a3}*Subprojects* {color}part is OK but not the *{color:#ff0000}Downstream Projects{color}* part

          !image-2021-01-08-17-44-05-561.png!

          And if we look in the status page of the run we see that the *{color:#de350b}Subprojects{color}* part for the pipeline job is missing

          !image-2021-01-08-17-49-39-541.png!

          Note that the 2 jobs were correctly started as we can see in the console log

          !image-2021-01-08-18-01-33-502.png!
          Let's compare how are reported a pipeline job and a freestyle job when they are triggered as parametrized build in the build section.

          In my example I have a freestyle job :

          test-parametrizedPlugin-main-job that calls 2 jobs one freestyle and one pipeline :
           * test-parametrizedPlugin-called-pipeline-job
           * test-parametrizedPlugin-called-freestyle-job

          !image-2021-01-08-17-37-12-357.png!!image-2021-01-08-17-36-24-862.png!

          In the status page of the job we see that the {color:#57d9a3}*Subprojects* {color}part is OK but not the *{color:#ff0000}Downstream Projects{color}* part, the pipeline job is missing

          !image-2021-01-08-17-44-05-561.png!

          And if we look in the status page of the run we see that the *{color:#de350b}Subprojects{color}* part for the pipeline job is missing

          !image-2021-01-08-17-49-39-541.png!

          Note that the 2 jobs were correctly started as we can see in the console log

          !image-2021-01-08-18-01-33-502.png!

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            merlindam Damien Merlin
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated: