• Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Critical Critical
    • subversion-plugin
    • None
    • 1.509.2-LTS

      Problem
      When using Subversion's "list tags" parameter, the default value associated with a "list tags" parameter is the only one taken into account for automatically triggered builds.

      When using the parameter in a subversion repository for the source code, the automatic build (e.g. periodic build) fails when there is no default value defined.

      For example
      Defining VERSION "list tags" parameter without default value
      and using it as "svn+ssh://svn.mycompany.com/repository_root/branches/$VERSION" in the source code makes our automatic build fail!

      The exception from the console log is:

         Location 'svn+ssh://svn.mycompany.com/repository_root/branches/$VERSION' does not exist
         Switching from svn+ssh://svn.mycompany.com/repository_root/branches/1.2.3 to svn+ssh://svn.mycompany.com/repository_root/branches/$VERSION
         Switching to svn+ssh://svn.mycompany.com/repository_root/branches/$VERSION at revision '2013-09-12T01:18:56.750 +0200'
         ERROR: Failed to update svn+ssh://svn.mycompany.com/repository_root/branches/$VERSION
      

      Proposal
      I expect the plugin to look in all (matching) "tags" and use/build the tag which has the latest changes.

      Although, when I select "Sort newest first" or "Sort Z to A", I expect the first "tag" in the sorted list
      to be checked for changes and used in the automatic triggered build.

      Does anyone have other comments on this issue?

      This is an important issue for us, because we use multiple active branches and we want to build every branch automatically when there are changes!

          [JENKINS-19560] Parameterized build only takes DEFAULT value

          Tom Ghyselinck created issue -
          Yoichi Nakayama made changes -
          Issue Type Original: Bug [ 1 ] New: New Feature [ 2 ]
          Yoichi Nakayama made changes -
          Link New: This issue duplicates JENKINS-14155 [ JENKINS-14155 ]
          Tom Ghyselinck made changes -
          Component/s New: parameterized-trigger [ 15592 ]
          Component/s New: parameters [ 15594 ]
          Description Original: When using Subversion's "list tags" parameter, the default value associated with a "list tags" parameter is the only one taken into account for automatically triggered builds.
          When using the parameter in a subversion repository for the source code, the automatic build (e.g. periodic build) fails when there is no default value defined.

          e.g. defining VERSION "list tags" parameter without default value
          and using it as "svn+ssh://svn.mycompany.com/repository_root/branches/$VERSION" in the source code
          makes our automatic build fail!

          The exception from the console log is:
             Location 'svn+ssh://svn.mycompany.com/repository_root/branches/$VERSION' does not exist
             Switching from svn+ssh://svn.mycompany.com/repository_root/branches/1.2.3 to svn+ssh://svn.mycompany.com/repository_root/branches/$VERSION
             Switching to svn+ssh://svn.mycompany.com/repository_root/branches/$VERSION at revision '2013-09-12T01:18:56.750 +0200'
             ERROR: Failed to update svn+ssh://svn.mycompany.com/repository_root/branches/$VERSION

          I expect the plugin to look in all (matching) "tags" and use/build the tag which has the latest changes.
          Although, when I select "Sort newest first" or "Sort Z to A", I expect the first "tag" in the sorted list
          to be checked for changes and used in the automatic triggered build.

          Does anyone have other comments on this issue?
          This is an important issue for us, because we use multiple active branches and we want to build every branch automatically when there are changes!
          New: *Problem*
          When using Subversion's _"list tags"_ parameter, the default value associated with a _"list tags"_ parameter is the only one taken into account for automatically triggered builds.

          When using the parameter in a subversion repository for the source code, the automatic build (e.g. periodic build) fails when there is no default value defined.

          *For example*
          Defining {{VERSION}} _"list tags"_ parameter without default value
          and using it as "{{svn+ssh://svn.mycompany.com/repository_root/branches/$VERSION}}" in the source code makes our automatic build fail!

          The exception from the console log is:
          {code}
             Location 'svn+ssh://svn.mycompany.com/repository_root/branches/$VERSION' does not exist
             Switching from svn+ssh://svn.mycompany.com/repository_root/branches/1.2.3 to svn+ssh://svn.mycompany.com/repository_root/branches/$VERSION
             Switching to svn+ssh://svn.mycompany.com/repository_root/branches/$VERSION at revision '2013-09-12T01:18:56.750 +0200'
             ERROR: Failed to update svn+ssh://svn.mycompany.com/repository_root/branches/$VERSION
          {code}

          *Proposal*
          I expect the plugin to look in all (matching) "tags" and use/build the tag which has the latest changes.

          Although, when I select _*"Sort newest first"*_ or _*"Sort Z to A"*_, I expect the _*first "tag"*_ in the sorted list
          to be _checked for changes_ *and* _used_ in the _automatic triggered build_.

          Does anyone have other comments on this issue?

          This is an important issue for us, because we use multiple active branches and we want to build every branch automatically when there are changes!
          Issue Type Original: New Feature [ 2 ] New: Improvement [ 4 ]
          ikedam made changes -
          Component/s Original: parameterized-trigger [ 15592 ]
          Jenkins IRC Bot made changes -
          Component/s New: core [ 15593 ]
          Component/s Original: parameters [ 15594 ]
          Manuel Recena Soto made changes -
          Assignee New: Manuel Recena Soto [ recena ]
          Manuel Recena Soto made changes -
          Component/s Original: core [ 15593 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 151014 ] New: JNJira + In-Review [ 177840 ]

            recena Manuel Recena Soto
            tom_ghyselinck Tom Ghyselinck
            Votes:
            3 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: