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

Parameterized build only takes DEFAULT value

    Details

    • Type: Improvement
    • Status: Open (View Workflow)
    • Priority: Critical
    • Resolution: Unresolved
    • Component/s: subversion-plugin
    • Labels:
      None
    • Environment:
      1.509.2-LTS
    • Similar Issues:

      Description

      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!

        Attachments

          Issue Links

            Activity

            Hide
            tom_ghyselinck Tom Ghyselinck added a comment -

            Anyone???

            This is taking much of our precious time!

            Show
            tom_ghyselinck Tom Ghyselinck added a comment - Anyone??? This is taking much of our precious time!
            Hide
            yoichi Yoichi Nakayama added a comment -

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

            Currently, we don't have such feature.

            Show
            yoichi Yoichi Nakayama added a comment - > I expect the plugin to look in all (matching) "tags" and use/build the tag which has the latest changes. Currently, we don't have such feature.
            Hide
            tom_ghyselinck Tom Ghyselinck added a comment -

            Hi guys,

            Is there any update on selecting some default value?

            We'd very like the option:

            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.

            We still need this fix!

            Show
            tom_ghyselinck Tom Ghyselinck added a comment - Hi guys, Is there any update on selecting some default value? We'd very like the option: 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. We still need this fix!
            Hide
            ikedam ikedam added a comment -

            Parameterized-trigger have nothing to do with polling.

            Show
            ikedam ikedam added a comment - Parameterized-trigger have nothing to do with polling.
            Hide
            tom_ghyselinck Tom Ghyselinck added a comment -

            It's not during polling, it's during checkout.

            The variable $VERSION from the "list subversion tags plugin" is not resolved when no default value is configured.
            ( It is resolved when the default value is filled in! )

            But we want the default value to be selected by the "Sort newest first" and "Sort Z to A" configuration item.

            Note
            When both are selected, I suggest preference for "Sort newest first".
            "Sort Z to A" can then be used in second stage when 2 tags have been modified at the same time.

            Show
            tom_ghyselinck Tom Ghyselinck added a comment - It's not during polling, it's during checkout. The variable $VERSION from the " list subversion tags plugin " is not resolved when no default value is configured. ( It is resolved when the default value is filled in! ) But we want the default value to be selected by the " Sort newest first " and " Sort Z to A " configuration item. Note When both are selected, I suggest preference for " Sort newest first ". " Sort Z to A " can then be used in second stage when 2 tags have been modified at the same time.

              People

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

                Dates

                • Created:
                  Updated: