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

Job failure after changing clearcase load rules

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Minor
    • Resolution: Fixed
    • clearcase-plugin
    • None
    • Hudson 1.355 with ClearCase plugin 1.2 in master/slave configuration running on Windows XP.

    Description

      If I change the load rules of an existing job from

      load /xxx

      to

      load /xxx/yyy

      all subsequent builds fail:

      Started by user anonymous
      Building remotely on NodeX
      [NodeX_olr_build] $ cleartool pwv -root
      C:\Hudson\workspace\olr_build\NodeX_olr_build

      [olr_build] $ cleartool lsview NodeX_olr_build
      NodeX_olr_build \\NodeX\view\viewdb\NodeX_olr_build
      [NodeX_olr_build] $ cleartool lsview -cview -s
      NodeX_olr_build
      [olr_build] $ cleartool catcs -tag NodeX_olr_build

      element * CHECKEDOUT
      element * .../png2010_junb_dev/LATEST
      mkbranch png2010_junb_dev
      element * .../png2010_jun/LATEST
      element * /main/LATEST
      load \png
      Removed load rule : png
      Added load rule : png\olr

      [NodeX_olr_build] $ cleartool setcs ..\configspec8922497310808366108.txt
      cleartool: Warning: 1 objects were eliminated from the new config spec's load rules:
      "\png"
      Continue, and unload these objects? [no] cleartool: Error: Unable to change configuration specification: error detected by ClearCase subsystem.

      FATAL: Base ClearCase failed. exit code=1
      FATAL: java.io.IOException: cleartool did not return the expected exit code. Command line="setcs ..\configspec8922497310808366108.txt", actual exit code=1
      Recording test results

      Email was triggered for: Failure
      Sending email for trigger: Failure
      Sending email to: olr-dev@mailman.xxx.com
      Finished: FAILURE

      The work around is to wipe out the workspace and rerun the job.

      However, this can be avoided if the -force option is provided with the setcs command, which avoids the warning and prompt to the (non-existent) user.

      Attachments

        Activity

          vlatombe Vincent Latombe added a comment - - edited

          Hello,

          • Unfortunately "-force" flag is not available for old Clearcase versions
          • However, I just checked the source code and there is a way to workaround this by providing "yes" in the default stream input (I thought it was using it, but it turns out it is not)
          vlatombe Vincent Latombe added a comment - - edited Hello, Unfortunately "-force" flag is not available for old Clearcase versions However, I just checked the source code and there is a way to workaround this by providing "yes" in the default stream input (I thought it was using it, but it turns out it is not)

          First patch about this, to be tested (don't have enough time right now)

          vlatombe Vincent Latombe added a comment - First patch about this, to be tested (don't have enough time right now)

          Code changed in hudson
          User: : vlatombe
          Path:
          trunk/hudson/plugins/clearcase/src/main/java/hudson/plugins/clearcase/ClearToolExec.java
          trunk/hudson/plugins/clearcase/src/main/java/hudson/plugins/clearcase/ClearToolSnapshot.java
          trunk/hudson/plugins/clearcase/src/test/java/hudson/plugins/clearcase/ClearToolSnapshotTest.java
          http://jenkins-ci.org/commit/31414
          Log:
          [Fixed JENKINS-6591] Job failure after changing clearcase load rules

          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in hudson User: : vlatombe Path: trunk/hudson/plugins/clearcase/src/main/java/hudson/plugins/clearcase/ClearToolExec.java trunk/hudson/plugins/clearcase/src/main/java/hudson/plugins/clearcase/ClearToolSnapshot.java trunk/hudson/plugins/clearcase/src/test/java/hudson/plugins/clearcase/ClearToolSnapshotTest.java http://jenkins-ci.org/commit/31414 Log: [Fixed JENKINS-6591] Job failure after changing clearcase load rules

          Committed in trunk. Will be available in 1.2.1

          vlatombe Vincent Latombe added a comment - Committed in trunk. Will be available in 1.2.1

          People

            vlatombe Vincent Latombe
            rsteele rsteele
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: