- 
    
Bug
 - 
    Resolution: Duplicate
 - 
    
Major
 - 
    None
 
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."
 
- duplicates
 - 
                    
JENKINS-10628 SCM build trigger not working correctly with variables in SVN URL
-         
 - Resolved
 
 -