Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-7122

Disable lshistory

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Critical Critical
    • clearcase-plugin
    • None

      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.

          [JENKINS-7122] Disable lshistory

          Jose Sa created issue -
          Jose Sa made changes -
          Description Original: Using the correct method for Change detection 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.           		New: 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.
          Vincent Latombe made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          Jose Sa made changes -
          Link New: This issue is related to JENKINS-9215 [ JENKINS-9215 ]
          Vincent Latombe made changes -
          Status Original: Resolved [ 5 ] New: Closed [ 6 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 137219 ] New: JNJira + In-Review [ 204429 ]
          Stuart Rowe made changes -
          Assignee Original: Vincent Latombe [ vlatombe ] New: Stuart Rowe [ stuartrowe ]
          Stuart Rowe made changes -
          Assignee Original: Stuart Rowe [ stuartrowe ] New: Vincent Latombe [ vlatombe ]

            vlatombe Vincent Latombe
            josesa Jose Sa
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: