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

          Code changed in jenkins
          User: Vincent Latombe
          Path:
          src/main/java/hudson/plugins/clearcase/ClearCaseUcmSCM.java
          http://jenkins-ci.org/commit/clearcase-plugin/8acaacc8bce6d17ade9f7406cfa0c5dd3b5bc59f
          Log:
          JENKINS-27104 Choosing "No History" option in Changeset still brings
          back history

          Adding missing mapping of ChangesetLevel to the UcmWorkflow

          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Vincent Latombe Path: src/main/java/hudson/plugins/clearcase/ClearCaseUcmSCM.java http://jenkins-ci.org/commit/clearcase-plugin/8acaacc8bce6d17ade9f7406cfa0c5dd3b5bc59f Log: JENKINS-27104 Choosing "No History" option in Changeset still brings back history Adding missing mapping of ChangesetLevel to the UcmWorkflow

          Code changed in jenkins
          User: Vincent Latombe
          Path:
          src/main/java/hudson/plugins/clearcase/ClearCaseUcmSCM.java
          http://jenkins-ci.org/commit/clearcase-plugin/41a84b4ba596f7c8290803f642732949d575c113
          Log:
          JENKINS-27104 Choosing "No History" option in Changeset still brings
          back history

          Adding missing mapping of ChangesetLevel to the UcmWorkflow

          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Vincent Latombe Path: src/main/java/hudson/plugins/clearcase/ClearCaseUcmSCM.java http://jenkins-ci.org/commit/clearcase-plugin/41a84b4ba596f7c8290803f642732949d575c113 Log: JENKINS-27104 Choosing "No History" option in Changeset still brings back history Adding missing mapping of ChangesetLevel to the UcmWorkflow

          Code changed in jenkins
          User: Vincent Latombe
          Path:
          src/main/java/hudson/plugins/clearcase/ClearCaseUcmSCM.java
          http://jenkins-ci.org/commit/clearcase-plugin/71d602927a7b783a5683a652f2c3eb17fad35117
          Log:
          JENKINS-27104 Choosing "No History" option in Changeset still brings back history

          Adding missing mapping of ChangesetLevel to the UcmWorkflow

          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Vincent Latombe Path: src/main/java/hudson/plugins/clearcase/ClearCaseUcmSCM.java http://jenkins-ci.org/commit/clearcase-plugin/71d602927a7b783a5683a652f2c3eb17fad35117 Log: JENKINS-27104 Choosing "No History" option in Changeset still brings back history Adding missing mapping of ChangesetLevel to the UcmWorkflow

          Released in 1.6

          vlatombe Vincent Latombe added a comment - Released in 1.6

          People

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

            Dates

              Created:
              Updated:
              Resolved: