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

When creating a new item from copy which has parameter, SVN does not record any revision

      I have a job with a random string parameter using SVN. I copied that job. The new job kept queuing up new builds for every SCM poll even though no changes had been made to the repository. The output messages said:

      Job console output:
      No revision recorded for https://<myrepositoryhere> in the previous build

      SVN polling log:
      Workspace doesn't contain https://<myrepositoryhere>. Need a new build.

      I removed the random string parameter from the new job and the problem disappeared.

          [JENKINS-38271] When creating a new item from copy which has parameter, SVN does not record any revision

          Daniel Beck added a comment -

          What exactly is the bug here? Random string parameter is basically needed to queue up duplicate builds circumventing Jenkins' detection of 'identical' queue items. So it appears to be working as designed both with (random value) parameter, and without – assuming you poll so often that the SCM revisions in the previous build haven't yet been determined when the new build is queued.

          Daniel Beck added a comment - What exactly is the bug here? Random string parameter is basically needed to queue up duplicate builds circumventing Jenkins' detection of 'identical' queue items. So it appears to be working as designed both with (random value) parameter, and without – assuming you poll so often that the SCM revisions in the previous build haven't yet been determined when the new build is queued.

          Marcus Arganso added a comment - - edited

          The bug is that new builds are queued up on every poll. The random string parameter is designed to queue a new build when I click "Build with parameters". Notice that the bug more specifically is that a new build is queued on every poll EVEN THOUGH NO CHANGES HAVE BEEN MADE TO THE REPOSITORY.

          I'm clarifying the problem in the description.

          Marcus Arganso added a comment - - edited The bug is that new builds are queued up on every poll. The random string parameter is designed to queue a new build when I click "Build with parameters". Notice that the bug more specifically is that a new build is queued on every poll EVEN THOUGH NO CHANGES HAVE BEEN MADE TO THE REPOSITORY. I'm clarifying the problem in the description.

          Daniel Beck added a comment -

          The random string parameter is designed to queue a new build when I click "Build with parameters". Notice that the bug more specifically is that a new build is queued on every poll EVEN THOUGH NO CHANGES HAVE BEEN MADE TO THE REPOSITORY.

          Did any of the queued builds start and pass the 'SCM checkout' stage, so that revisions had been recorded? If yes, there's a bug here with Subversion plugin polling.

          If not, everything works as designed:

          • There's no build with known and up to date revisions, so one does get queued.
          • The queue items are all distinct thanks to Random String parameter, so don't get merged into one item.

          If for example no build agent is available to run the build on, this is exactly what I would expect happens.

          Remember, the computer does what you tell it to do, not what you want

          Daniel Beck added a comment - The random string parameter is designed to queue a new build when I click "Build with parameters". Notice that the bug more specifically is that a new build is queued on every poll EVEN THOUGH NO CHANGES HAVE BEEN MADE TO THE REPOSITORY. Did any of the queued builds start and pass the 'SCM checkout' stage, so that revisions had been recorded? If yes, there's a bug here with Subversion plugin polling. If not, everything works as designed: There's no build with known and up to date revisions, so one does get queued. The queue items are all distinct thanks to Random String parameter, so don't get merged into one item. If for example no build agent is available to run the build on, this is exactly what I would expect happens. Remember, the computer does what you tell it to do, not what you want

          Every build performed all the stages. Note that as stated in the description of this problem the SVN polling log stated:

          Workspace doesn't contain https://<myrepositoryhere>. Need a new build.

          Even though the repository was clearly in the workspace.

          Maybe the description of this bug is incorrect and confusing. Removing the random parameter string from my job, saving and re-adding it again solved the problem. Seems strange how the random string parameter could affect SVN but thats what happened.

          Marcus Arganso added a comment - Every build performed all the stages. Note that as stated in the description of this problem the SVN polling log stated: Workspace doesn't contain https://<myrepositoryhere>. Need a new build. Even though the repository was clearly in the workspace. Maybe the description of this bug is incorrect and confusing. Removing the random parameter string from my job, saving and re-adding it again solved the problem. Seems strange how the random string parameter could affect SVN but thats what happened.

            Unassigned Unassigned
            drutten Marcus Arganso
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: