![]() |
|
|
|
|
Change By:
|
Kevin Phillips
(24/Jul/13 2:56 PM)
|
|
Description:
|
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
is
represents
the
revision of the
"last
modification
changed revision
"
to
for
the
repository URL
provided
in the configuration
URL
.
This version number is sufficient in
In
certain
use
cases
but not in every use case. One example
it would be useful to also have access to the "latest" revision as well - ie: the revision
of
this is when
the repository after the most recent checkout or update operation.
I suspect such an enhancement could be made in
a
given SVN URL uses externals to
non-
static revisions of other sources
breaking way as well
.
In this case
For example
,
perhaps
the SVN plugin
incorrectly reports
could provide an option - either globally in
the
last change for
main Jenkins configuration area, or per-job in
the
root URL and ignores the revisions
SCM configuration section
of
all externals.
Ideally this plugin would either provide
each job - to have
the
option or expose as a secondary
SVN_REVISION
Jenkins property
defined by either
the
HEAD
last changed revision
or
the
latest
checkout / repository
revision
instead of /
,
as
well as the last changed revision
desired
.
This
Alternatively, perhaps a new Jenkins property could be introduced, say SVN_LATEST_REVISION, which
would
allow jobs configured with
contain the appropriate value.
NOTE: I suspect that this enhancement could be used as
a
single SVN URL with external dependencies
workaround
to
use
some (but not all) of
the
latest checkout revision as
workflows being discussed on JENKINS-1241. Also given
the
unique ID for
fact that either solution I suggested would be non-breaking it could conceivably be implemented and released on all currently supported versions of
the
checkout
plugin
.
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit
https://groups.google.com/groups/opt_out.
