Issue Type: Bug Bug
Assignee: Vincent Latombe
Components: clearcase
Created: 06/Feb/14 11:13 AM
Description:

Some days ago we upgraded from clearcase plugin 1.3.6 to 1.4.
We now noticed the following behavior:
Cleartool stops the update if the configspec is defect (such as a file referenced in load rules does not exist in clearcase) - no file gets updated.
But Jenkins continues the build with the old files existing in workspace (we use the "use update" function) and reports a green build (if the last build was green).
This load rule error is fatal and should stop the build.

SAMPLE:
Configspec:
element * CHECKEDOUT
element * /main/LATEST

Loadrules:
\SPCSDev\Tools\jenkins\Testfiles\Samplefile.txt
\SPCSDev\Tools\jenkins\Testfiles\NotexistingFile.txt

==>SampleFile.txt exists in clearcase, NotexistingFile.txt doesnt

Console out:

  1. Actions taken to update the view:
  2. NonfileError: "cleartool: Error: Unable to lookup "NotexistingFile.txt" in "\SPCSDev\Tools\jenkins\Testfiles@@\main\5": No such file or directory."
    NonfileError: "cleartool: Error: Unable to access "\SPCSDev\Tools\jenkins\Testfiles\NotexistingFile.txt": No such file or directory."
    NonfileError: "cleartool: Error: 1 config spec load rule problems encountered."

  3. Update session status:
  4. EndTime: 2014-02-06T12:05:08+01:00
    BytesCopied: 0
    CancelledByUser: FALSE

Result:
Samplefile.txt wasn't updated
Build gets green.

Environment: Jenkins ClearCase Plug-in 1.4
Jenkins ver. 1.532.1
Project: Jenkins
Labels: clearcase
Priority: Major Major
Reporter: Torsten Kühn
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to