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

Access to build's own changelog from script

    XMLWordPrintable

Details

    • New Feature
    • Status: Resolved (View Workflow)
    • Major
    • Resolution: Fixed
    • pipeline
    • None

    Description

      Workflow scripts would often like to behave differently depending on the SCM changelog(s) for the current build (or perhaps a downstream build). You can use currentBuild.rawBuild.changeSets but this is not accessible from the sandbox.

      Attachments

        Issue Links

          depends on

          Task - A task that needs to be done. JENKINS-24141 SCM with non-AbstractProject, revisited

          • Major - Major loss of function.
          • Closed
          is related to

          Improvement - An improvement or enhancement to an existing feature or task. JENKINS-26100 SCM steps should return revision state

          • Major - Major loss of function.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-42214 Field entries for hudson.scm.EditType fields in "jenkins-whitelist" must be static

          • Critical - Crashes, loss of data, severe memory leak.
          • Resolved

          New Feature - A new feature of the product, which has yet to be developed. JENKINS-27092 create a step to abort the build with a NOT_BUILT status

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Reopened
          links to

          Web Link CloudBees Internal OSS-499

          Web Link workflow-support PR 5

          Activity

            Ascending order - Click to sort in descending order
            View 4 older comments
            jglick Jesse Glick added a comment -

            Correct.

            jglick Jesse Glick added a comment - Correct.
            jamesdumay James Dumay added a comment - - edited

            jglick / hrmpw / abayer is there any reason why the change log is sandboxed? Could we offer it in some other way? e.g. request it as a JSON blob or well known array structure?

            jamesdumay James Dumay added a comment - - edited jglick / hrmpw / abayer is there any reason why the change log is sandboxed? Could we offer it in some other way? e.g. request it as a JSON blob or well known array structure?
            hrmpw Patrick Wolf added a comment -

            jglick / abayer / jamesdumay the Global Library is not sandboxed now would it be possible to put this snippet into a global library function and run it? Would currentBuild be available in a global library call?

            Likewise, plugins are not subject to the sandbox so this might be able to be solved with the "step in pipeline" work that Andrew and KK are looking at.

            hrmpw Patrick Wolf added a comment - jglick / abayer / jamesdumay the Global Library is not sandboxed now would it be possible to put this snippet into a global library function and run it? Would currentBuild be available in a global library call? Likewise, plugins are not subject to the sandbox so this might be able to be solved with the "step in pipeline" work that Andrew and KK are looking at.
            jamesdumay James Dumay added a comment -

            hrmpw thanks for that. abayer you think there is an easier way we can make this work in your new work?

            jamesdumay James Dumay added a comment - hrmpw thanks for that. abayer you think there is an easier way we can make this work in your new work?
            mreinhardt Martin Reinhardt added a comment -

            When trying to run this:

            node("mac") {
  env.JAVA_HOME = tool 'JDK 8'
  def buildNumber = env.BUILD_NUMBER
  def build = currentBuild
  
....

      summarizeBuild(${build})
      ...

}

@NonCPS
def summarizeBuild(b) {
  b.changeSets.collect { cs ->
    /kind=${cs.kind}; entries=/ + cs.collect { entry ->
      /${entry.commitId} by ${entry.author.id} ~ ${entry.author.fullName} on ${new Date(entry.timestamp)}: ${entry.msg}:  /+ entry.affectedFiles.collect { file ->
        /${file.editType.name} ${file.path}/
      }.join('; ')
    }.join(', ')
  }.join(' & ')
}

            I always get this error:

            java.io.NotSerializableException: hudson.plugins.git.GitChangeSetList
	at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:860)
	at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:569)
	at org.jboss.marshalling.river.BlockMarshaller.doWriteObject(BlockMarshaller.java:65)
	at org.jboss.marshalling.river.BlockMarshaller.writeObject(BlockMarshaller.java:56

            Did anybody have a valid example?

            mreinhardt Martin Reinhardt added a comment - When trying to run this: node( "mac" ) { env.JAVA_HOME = tool 'JDK 8' def buildNumber = env.BUILD_NUMBER def build = currentBuild .... summarizeBuild(${build}) ... } @NonCPS def summarizeBuild(b) { b.changeSets.collect { cs -> /kind=${cs.kind}; entries=/ + cs.collect { entry -> /${entry.commitId} by ${entry.author.id} ~ ${entry.author.fullName} on ${ new Date(entry.timestamp)}: ${entry.msg}: /+ entry.affectedFiles.collect { file -> /${file.editType.name} ${file.path}/ }.join( '; ' ) }.join( ', ' ) }.join( ' & ' ) } I always get this error: java.io.NotSerializableException: hudson.plugins.git.GitChangeSetList at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:860) at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:569) at org.jboss.marshalling.river.BlockMarshaller.doWriteObject(BlockMarshaller.java:65) at org.jboss.marshalling.river.BlockMarshaller.writeObject(BlockMarshaller.java:56 Did anybody have a valid example?

            People

              jglick Jesse Glick
              jglick Jesse Glick
              Votes:
              5 Vote for this issue
              Watchers:
              15 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: