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

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

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Minor Minor
    • subversion-plugin
    • None

      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.

          [JENKINS-20463] Manual build of tag breaks scm poll on trunk for parameterized builds

          Christoph Kuhnke created issue -
          Yoichi Nakayama made changes -
          Link New: This issue is related to JENKINS-17867 [ JENKINS-17867 ]
          Yoichi Nakayama made changes -
          Link New: This issue duplicates JENKINS-14326 [ JENKINS-14326 ]
          ikedam made changes -
          Component/s Original: parameterized-trigger [ 15592 ]
          Assignee Original: huybrechts [ huybrechts ] New: k2nakamura [ k2nakamura ]

          k2nakamura added a comment -

          It seems to be unrelated to svn-tagging plugin but part of core.

          k2nakamura added a comment - It seems to be unrelated to svn-tagging plugin but part of core.
          Manuel Recena Soto made changes -
          Assignee Original: k2nakamura [ k2nakamura ] New: Manuel Recena Soto [ recena ]

          fasjenkins What versions of Jenkins, Subversion Plugin and EnvInject Plugin are you using?

          Manuel Recena Soto added a comment - fasjenkins What versions of Jenkins, Subversion Plugin and EnvInject Plugin are you using?

          Hello, we are using
          Jenkins ver. 1.580.3, Subversion Plug-in 1.54.
          We have not installed EnvInject Plugin.
          Greets, Christoph.

          Christoph Kuhnke added a comment - Hello, we are using Jenkins ver. 1.580.3, Subversion Plug-in 1.54. We have not installed EnvInject Plugin. Greets, Christoph.

          fasjenkins, Sorry, I meant version of SVN Tag Plugin. I'm asking about this plugin because the issue has two components involved (svn-tag-plugin & subversion-plugin).

          Subversion Plugin has a functionally to build tags but there is people that using SVN Tag Plugin.

          Manuel Recena Soto added a comment - fasjenkins , Sorry, I meant version of SVN Tag Plugin. I'm asking about this plugin because the issue has two components involved (svn-tag-plugin & subversion-plugin). Subversion Plugin has a functionally to build tags but there is people that using SVN Tag Plugin.

          Hi Manuel,

          we have not installed "SVN Tag Plugin".

          Christoph Kuhnke added a comment - Hi Manuel, we have not installed "SVN Tag Plugin".

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

              Created:
              Updated:
              Resolved: