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

Option to suppress changelong when getting Pipeline Jenkinsfile from GitHub SCM

      When pulling pipeline script from SCM, there is no way to suppress the changelog which is makes it difficult if not impossible to easily distinguish changelog items between changes to the script file and changes to the actual app source the pipeline is building.

      In this particular case I have a generic pipeline script stored in a controlled GitHub repository along with app specific properties files which are loaded to control what gets executed in the pipeline script. The pipeline script then pulls the actual application source code for the build from within it.

      No need for the changelog of the build to include entries from changes to the generic pipeline script nor the properties files. Only want it to include app code source changes.

          [JENKINS-40340] Option to suppress changelong when getting Pipeline Jenkinsfile from GitHub SCM

          Cory Grubbs added a comment -

          Can somebody provide an update/eta on this?

          Cory Grubbs added a comment - Can somebody provide an update/eta on this?

          Cory Grubbs added a comment -

          Is there a problem with this request that is causing it to not be picked up?

          Cory Grubbs added a comment - Is there a problem with this request that is causing it to not be picked up?

          Jesse Glick added a comment -

          Solved implicitly by JENKINS-33273.

          Jesse Glick added a comment - Solved implicitly by JENKINS-33273 .

          Cory Grubbs added a comment -

          Please clarify how this is solve implicitly by JENKINS-33273.

          I get that there are 3 checkouts in my current process(1. get the jenkinsfile, 2. get the app specific properties file, 3. get the application source code)

          All I'm looking for is ability to suppress changelog information for the first 2 so that the list of changes in the build ONLY includes changes that have been made to the application source code.

          Cory Grubbs added a comment - Please clarify how this is solve implicitly by JENKINS-33273 . I get that there are 3 checkouts in my current process(1. get the jenkinsfile, 2. get the app specific properties file, 3. get the application source code) All I'm looking for is ability to suppress changelog information for the first 2 so that the list of changes in the build ONLY includes changes that have been made to the application source code.

          Jesse Glick added a comment -

          Only in that currently it does not load a changelog, more by accident than design.

          Jesse Glick added a comment - Only in that currently it does not load a changelog, more by accident than design.

          Jesse Glick added a comment -

          I have a generic pipeline script stored in a controlled GitHub repository along with app specific properties files which are loaded to control what gets executed in the pipeline script. The pipeline script then pulls the actual application source code for the build from within it.

          So why are you using a multibranch project at all? Simpler to use a standalone project with script from SCM. The expectation of a multibranch project with Jenkinsfile is that in a typical build you will soon be calling checkout scm at least once.

          Jesse Glick added a comment - I have a generic pipeline script stored in a controlled GitHub repository along with app specific properties files which are loaded to control what gets executed in the pipeline script. The pipeline script then pulls the actual application source code for the build from within it. So why are you using a multibranch project at all? Simpler to use a standalone project with script from SCM. The expectation of a multibranch project with Jenkinsfile is that in a typical build you will soon be calling checkout scm at least once.

          Cory Grubbs added a comment -

          I'm not using the mulit-branch plugin. You're the one that changed my issue to the multi-branch plugin. I originally filed it under the workflow-aggregator plugin which is what I am using.

          Cory Grubbs added a comment - I'm not using the mulit-branch plugin. You're the one that changed my issue to the multi-branch plugin. I originally filed it under the workflow-aggregator plugin which is what I am using.

          Jesse Glick added a comment -

          Ah then this is just a duplicate of JENKINS-38659.

          (BTW the component is then workflow-cps-plugin.)

          Jesse Glick added a comment - Ah then this is just a duplicate of JENKINS-38659 . (BTW the component is then workflow-cps-plugin .)

          Cory Grubbs added a comment -

          I don't know if it's a duplicate of that issue or not but this is definitely a higher priority issue than Minor for me due to the mass confusion it is causing. I'll defer to you what the plugin is as all I can tell you is I downloaded and installed the workflow-aggregator plugin along with its dependencies. I wouldn't expect it to be that difficult to update the plugin so that whenever the Jenkinsfile is pulled from Scm there is an additional checkbox to ignore changelog which results in no changelog getting generated when the Jenkinsfile is retrieved.

          Cory Grubbs added a comment - I don't know if it's a duplicate of that issue or not but this is definitely a higher priority issue than Minor for me due to the mass confusion it is causing. I'll defer to you what the plugin is as all I can tell you is I downloaded and installed the workflow-aggregator plugin along with its dependencies. I wouldn't expect it to be that difficult to update the plugin so that whenever the Jenkinsfile is pulled from Scm there is an additional checkbox to ignore changelog which results in no changelog getting generated when the Jenkinsfile is retrieved.

            Unassigned Unassigned
            cgrubbs Cory Grubbs
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: