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

Choosing "No History" option in Changeset still brings back history

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Minor
    • Resolution: Fixed
    • clearcase-plugin
    • Jenkins 1.598, Clearcase plugin 1.5.3, Windows 2008 R2, JDK 1.6.0_45 64bit, Clearcase 8.0.1.1

    Description

      I recently was required to create a build that only runs quarterly for the production release of our product. I set the Changeset radio button in the UCM Clearcase version of the Clearcase plugin to No History but when the build is executed, I still receive 3 months of file changes which adds a substantial amount of time to the build.
      What I have found is the method needsLsHistoryForGetChanges in the file AbstractHistoryAction.java always has the changeset variable set to null which causes the method to always return true.

      Attachments

        Activity

          People

            vlatombe Vincent Latombe
            amochoru Alan Mochoruk
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: