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

Manual build of tag breaks scm poll on trunk for parameterized builds

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      I'm using a parameterized build with

      Usually jenkins polls scm (subversion) for changes.
      If poll detects a change on trunk, then jenkins will update it's working copy from subversion repository trunk and executes a build - fine.

      When I choose

      • Build Now
      • SVN_TAG: 1.1
      • Build

      Jenkins checks out https://svn.server.domain/a/tags/1.1 and executes a build - still fine.

      Subsequent scm polls of jenkins are directed to this tag, which is usually not changed.

      Jenkins does not poll for changes of trunk, until a user requests a manual build of trunk.

      This ist not desired in our environment.

      Proposed behaviour of jenkins:

      • after user has executed a manual build of tag 1.1 (in general: with setting some parameters for the parameterized build)
      • jenkins resets these parameters to the default values
      • subsequent scm polls use default values for all parameters, expecially SVN_TAG in the use case described above.

        Attachments

          Issue Links

            Activity

            Hide
            fasjenkins Christoph Kuhnke added a comment -

            Hello Manuel,
            first of all many thanks for your efforts.
            I'm sorry: we cannot try latest version of Subversion Plugin, since we are also using SCM sync plugin and Subversion plugin >= 2.0 seems to be incompatible, see JENKINS-21640.

            Show
            fasjenkins Christoph Kuhnke added a comment - Hello Manuel, first of all many thanks for your efforts. I'm sorry: we cannot try latest version of Subversion Plugin, since we are also using SCM sync plugin and Subversion plugin >= 2.0 seems to be incompatible, see JENKINS-21640 .
            Hide
            recena Manuel Recena Soto added a comment -

            Christoph Kuhnke, I could not reproduce the bug described here using latest release of Subversion Plugin. We should close this ticket or to specific clearly that it happens on a very old version of Subversion Plugin.

            Show
            recena Manuel Recena Soto added a comment - Christoph Kuhnke , I could not reproduce the bug described here using latest release of Subversion Plugin. We should close this ticket or to specific clearly that it happens on a very old version of Subversion Plugin.
            Hide
            fasjenkins Christoph Kuhnke added a comment -

            I agree.
            Thanks for your efforts.
            I will repeat evaluation, as soon as we can use latest version of Subversion Plugin.

            Show
            fasjenkins Christoph Kuhnke added a comment - I agree. Thanks for your efforts. I will repeat evaluation, as soon as we can use latest version of Subversion Plugin.
            Hide
            recena Manuel Recena Soto added a comment -

            Christoph Kuhnke Thanks for you feedback.

            Show
            recena Manuel Recena Soto added a comment - Christoph Kuhnke Thanks for you feedback.
            Hide
            recena Manuel Recena Soto added a comment -

            This bug seems solved in latest release of Subversion Plugin.

            Show
            recena Manuel Recena Soto added a comment - This bug seems solved in latest release of Subversion Plugin.

              People

              Assignee:
              recena Manuel Recena Soto
              Reporter:
              fasjenkins Christoph Kuhnke
              Votes:
              2 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: