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.