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

subversion list branch/tags not working with release plugin

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Blocker Blocker
    • None
    • Jenkins version : 2.107.2 and 2.181
      release plugin version : 2.10.1 and 2.10.2

      Hi !

      We use subversion plugin to get list of branches when run "build" and list existing tags into "release build".

      After an update from an old Jenkins version, we can't get list of tags from SVN into "release build". It works into "classic" build process (we used it to choose branch).

      The combo-box is empty, request seems OK (same as simple build, with different property name) but response is an empty JSON object. I think that's on the configuration page the subversion plugin does not register the property.

      We tried to use no regex, same regex/url than on "build" svn parameter, change property name, with no effect.

       

      Thanks for help !

       

      EDIT : Now reproduced at home by installing official dockerfile (found procedure on jenkins wiki https://wiki.jenkins.io/display/JENKINS/Installing+Jenkins+with+Docker ), adding release plugin and it doesn't works with subversion plugin.

          [JENKINS-57856] subversion list branch/tags not working with release plugin

          Oleg Nenashev added a comment -

          I stepped down as a plugin maintainer in 2018. I do not have time for this plugin ATM, sorry

          Oleg Nenashev added a comment - I stepped down as a plugin maintainer in 2018. I do not have time for this plugin ATM, sorry

          Arch Loy added a comment -

          Understand. Thanks for reply

          Is the plugin dead ?

          Arch Loy added a comment - Understand. Thanks for reply Is the plugin dead ?

          Oleg Nenashev added a comment -

          I do not think so. The plugin is up for adoption, and eventually somebody will take the ownership.

          There is also https://jenkins.io/projects/gsoc/2019/artifact-promotion-plugin-for-jenkins-pipeline/ which may eventually lead to a merger of Release Plugin and Promoted Builds, but it is a moon shot ATM. 

          Oleg Nenashev added a comment - I do not think so. The plugin is up for adoption, and eventually somebody will take the ownership. There is also  https://jenkins.io/projects/gsoc/2019/artifact-promotion-plugin-for-jenkins-pipeline/  which may eventually lead to a merger of Release Plugin and Promoted Builds, but it is a moon shot ATM. 

          Arch Loy added a comment -

          'kay. I will try to debug, maybe it's trivial

          Arch Loy added a comment - 'kay. I will try to debug, maybe it's trivial

          Arch Loy added a comment -

          Made some experiments.

          Looking at configuration file, both parameters definitions are same btw "normal" subversion parameter and "release".

          By modifing the configuration file, use the same parameter name. Now it list my branches and tags.

           

          Conclusion : the problem exists on the configuration page. It seems that on configuration, subversion plugin register our parameter. But not correctly when it comes from Release plugin.

          Arch Loy added a comment - Made some experiments. Looking at configuration file, both parameters definitions are same btw "normal" subversion parameter and "release". By modifing the configuration file, use the same parameter name. Now it list my branches and tags.   Conclusion : the problem exists on the configuration page. It seems that on configuration, subversion plugin register our parameter. But not correctly when it comes from Release plugin.

          Arch Loy added a comment -

          After some tests, I found the problem (but not the solution...) :

          The subversion plugin try to find configured property by it's name into Job properties, as seen in the config.xml into <properties>. It's why the release plugin "Override build parameters" works with subversion plugin.

           

          The release plugin register "release" defined properties into an <buildWrapper> (in config.xml) and that's seen by the Job class as an Action (containing properties).

          So, if looking at "properties" of a given Job you can't seen Release properties.

           

          Anyway, where is the bug ? Does Release plugin need to store it's properties differently ? Does jenkins Job class need to be improved ? Does subversion plugin ?

          Hope my investigations help !

          Arch Loy added a comment - After some tests, I found the problem (but not the solution...) : The subversion plugin try to find configured property by it's name into Job properties, as seen in the config.xml into <properties>. It's why the release plugin "Override build parameters" works with subversion plugin.   The release plugin register "release" defined properties into an <buildWrapper> (in config.xml) and that's seen by the Job class as an Action (containing properties). So, if looking at "properties" of a given Job you can't seen Release properties.   Anyway, where is the bug ? Does Release plugin need to store it's properties differently ? Does jenkins Job class need to be improved ? Does subversion plugin ? Hope my investigations help !

            Unassigned Unassigned
            loy Arch Loy
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: