|
||||||||
|
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.
@tonylampada2
I like your suggestion. However, to help isolate the impact of such configuration options it may be safer to provide them at the job level rather than in the global Jenkins configuration.
Also, I think there could be a 4th option as well: by revision. For example, if someone uses a single repository for all their projects, there is one global revision number shared across all projects and this revision number is guaranteed to be unique. Therefore, building by revision is effectively the same as build by timestamp and yet it avoids the problem of clock skew.