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

SVN changelog per build not taking into account locations of script vs. checkout step

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Major Major
    • None
    • CentOS 7.1
      Jenkins ver. 1.631
      Workflow plugin 1.10.1

      For the sake of argument let's say you have simple single stage build

      #1 build is triggered - executing stage 1
      #2 build is triggered - waiting for #1 (there were SVN changes #22, #23)
      #3 build is triggered - Superseds #2, waiting for #1 (there were SVN changes #24, #25)

      Build #2 was never executed, so SVN update was actually never triggered (General SCM step is inside the stage this build was waiting for). But still the revisions #22, #23 are in changelog of build #2.

      Build #3 actually did the SVN update. In console output I can see that files from revision #22 and #23 were updated. But ONLY revision #24, #25 are part of the changelog.

      This cannot be intended behaviour right?

            Unassigned Unassigned
            vehovmar Martin Vehovsky
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: