[
https://issues.jenkins-ci.org/browse/JENKINS-7122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Latombe closed JENKINS-7122.
------------------------------------
> Disable lshistory
> ------------------
>
> Key: JENKINS-7122
> URL: https://issues.jenkins-ci.org/browse/JENKINS-7122
> Project: Jenkins
> Issue Type: Improvement
> Components: clearcase
> Affects Versions: current
> Reporter: Jose Sa
> Assignee: Vincent Latombe
> Priority: Critical
>
> Using the corrent method for Change detection (lshistory) works when the
> config spec is based on some branch/LATEST rules, which is the correct
> settings for Continuous Integration.
> However for maintenance projects where the Config Spec is based on specific
> LABELS the lshistory is not adequate since the LATEST changes in the branch
> may not reflect the changes made on the config spec used since last build.
> Therefore there should be also the option to disable any change detection
> (disable run lshistory), unless of course you know some other way of trackign
> changes on builds based on Floating Labels.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
