![]() |
|
|
|
|
Change By:
|
Ryan Hummer
(12/Aug/14 1:20 PM)
|
|
Description:
|
When triggering a job manually or via SCM Polling, the CL the job syncs it is not what the label has it's revision field set to. We use static labels so just the revision field is tagged for the label.
The SCM Polling log correctly identifies all the CL's upto and including the CL that the label is tagged at.
SCM Polling Log:
{quote}Started on Aug 7, 2014 3:18:48 PM
Polling SCM changes on rsmsnbuild114
P4: Polling with client: rsmsnbuild114
P4: Polling with label/change: latest_build_label
... found change: 978011
... <removing all the found CL#'s
... found change: 978233
Done. Took 1 min 0 sec
Changes found{quote}
Log from Job triggered by the SCM Polling:
{quote}15:19:48 Started by an SCM change
15:19:48 [EnvInject] - Loading node environment variables.
15:19:49 Building remotely on rsmsnbuild116 in workspace c:\trees
15:19:54 SCM Task: cleanup workspace: RSMSNBUILD116
15:19:54 SCM Task: syncing files at change: 979452
15:19:54 ... sync c:\trees/...@979452
15:19:54 ... force update false
15:19:54 ... bypass have false{quote}
As you can see the CL of the label is 978233, while the job is actually syncing to 979452. Which is not
desitred
desired
|
|
|
|
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
[email protected].
For more options, visit
https://groups.google.com/d/optout.
