[JIRA] (JENKINS-7122) Disable lshistory
Title: Message Title Stuart Rowe assigned an issue to Stuart Rowe Jenkins / JENKINS-7122 Disable lshistory Change By: Stuart Rowe Assignee: Vincent Latombe Stuart Rowe Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.137219.1280759392000.2079.1560806580230%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-7122) Disable lshistory
Title: Message Title Stuart Rowe assigned an issue to Vincent Latombe Sorry, not sure how I managed to assign this to myself. Jenkins / JENKINS-7122 Disable lshistory Change By: Stuart Rowe Assignee: Stuart Rowe Vincent Latombe Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.137219.1280759392000.2082.1560806580263%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-7122) Disable lshistory
[ 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
