Subversion no longer passes revision information to other plugins via SubversionTagAction

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      Somewhere between version 1.28 and version 1.32 of the Subversion plugin, the RevisionParameterAction started being ignored. This action is used by upstream builds to limit the revision that will be fetched by downstream builds - to stop downstream builds getting ahead of upstream builds. Specifically, the Parameterized Trigger Plugin and the Tracking SVN Plugin both use this action.

      A vanilla installation of Jenkins 1.428 (which is bundled with Subversion plugin 1.28) works fine. Upgrading the Subversion plugin to 1.32 breaks.

            Assignee:
            huybrechts
            Reporter:
            Danny Yates
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: