subversion-plugin commit notification (1.43) does not consider global node properties in SCM URLs

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

XMLWordPrintable

      i got several jenkins-jobs which use a global node property environment variable (jenkins global config). (i need this in order to centralize parts of svnURL for several jobs, so i only need to change the property to switch many jobs to a new branch).

      the problem came up with the use of post-commit hooks:
      on commit notification there 2 steps which need to be fixed:

      • in SubversionRepositoryStatus.notifyCommit() the check if the reported change is within/beyond the jobs SCMUrl is based on ModuleLocation.getSVNURL() instead of ModuleLocation.getExpandedLocation(envVarsContainingGlobalNodePropertyEnvVars).getSVNURL()
      • and same applies to SubversionSCM.repositoryLocationsNoLongerExist(), because otherwise the scmPolling would tell "One or more repository locations do not exist anymore for {0}

        , project will be disabled."

            Assignee:
            Unassigned
            Reporter:
            Klaus Azesberger
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: