-
Improvement
-
Resolution: Unresolved
-
Major
-
None
-
Win7 x64
Jenkins v1.590.1
SVN plugin v1.48
Currently the SVN plugin only provides a single SVN revision number for any given URL (ignoring for the moment the fact you can provide multiple URLs in one configuration). Further, ad-hoc tests reveal that this one SVN revision number represents the "last changed revision" for the provided URL.
In certain cases it would be useful to also have access to the "latest" revision as well - ie: the revision of the repository after the most recent checkout or update operation.
I suspect such an enhancement could be made in a non-breaking way as well. For example, perhaps the SVN plugin could provide an option - either globally in the main Jenkins configuration area, or per-job in the SCM configuration section of each job - to have the SVN_REVISION Jenkins property defined by either the last changed revision or the latest revision, as desired. Alternatively, perhaps a new Jenkins property could be introduced, say SVN_LATEST_REVISION, which would contain the appropriate value.
NOTE: I suspect that this enhancement could be used as a workaround to some (but not all) of the workflows being discussed on JENKINS-1241. Also given the fact that either solution I suggested would be non-breaking it could conceivably be implemented and released on all currently supported versions of the plugin.
[JENKINS-18907] Expose svn 'current' revision in addition to the 'last-changed' revision
Description |
Original:
Currently the SVN plugin only provides a single SVN revision number for any given URL (ignoring for the moment the fact you can provide multiple URLs in one configuration). Further, this one SVN revision number is the revision of the "last modification" to the repository URL provided in the configuration. This version number is sufficient in certain use cases but not in every use case. One example of this is when a given SVN URL uses externals to non-static revisions of other sources. In this case, the SVN plugin incorrectly reports the last change for the root URL and ignores the revisions of all externals. Ideally this plugin would either provide the option or expose as a secondary Jenkins property the HEAD or latest checkout / repository revision instead of / as well as the last changed revision. This would allow jobs configured with a single SVN URL with external dependencies to use the latest checkout revision as the unique ID for the checkout. |
New:
Currently the SVN plugin only provides a single SVN revision number for any given URL (ignoring for the moment the fact you can provide multiple URLs in one configuration). Further, ad-hoc tests reveal that this one SVN revision number represents the "last changed revision" for the provided URL. In certain cases it would be useful to also have access to the "latest" revision as well - ie: the revision of the repository after the most recent checkout or update operation. I suspect such an enhancement could be made in a non-breaking way as well. For example, perhaps the SVN plugin could provide an option - either globally in the main Jenkins configuration area, or per-job in the SCM configuration section of each job - to have the SVN_REVISION Jenkins property defined by either the last changed revision or the latest revision, as desired. Alternatively, perhaps a new Jenkins property could be introduced, say SVN_LATEST_REVISION, which would contain the appropriate value. NOTE: I suspect that this enhancement could be used as a workaround to some (but not all) of the workflows being discussed on JENKINS-1241. Also given the fact that either solution I suggested would be non-breaking it could conceivably be implemented and released on all currently supported versions of the plugin. |
IMO the plugin works as designed as AFAIK it returns pretty much the same, what svn info would return as 'Last Changed Rev'
Externals are a different beast.