|
||||||||
|
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 |
||||||||
|
||||||||
|
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 |
||||||||
It is also broke on a Windows single Jenkins instance setup using snapshot views.
Jenkins 1.477 Plugin version 1.3.7. ClearCase version 7.1.1.0
The first time I ran the job, it used a command of:
cleartool mkview -snapshot -tag myviewname -vws null\myviewname.vws
I don’t normally specify the view location when I do a mkview, so I added -stgloc –auto in the “additional mkview paramenters” and the plugin put it on twice.
cleartool mkview -snapshot -tag myviewname -stgloc -auto -stgloc -auto myviewname
So, I removed -stgloc –auto, and this time it generated
cleartool mkview -snapshot -tag myviewname -stgloc -auto myviewname
Which worked. But not for long. After a reboot I was back where I started with “-vws null...”
I looked through the source of ClearToolExec.java, and I think the problem is in mkview(MkViewParameters parameters).
I don’t want it to automatically add a view storage location when I create a snapshot view. I don’t need it. A simple “cleartool mkview -snapshot -tag myviewname myviewname“ works for me.
My workaround is to add “-tcomment test-host” to the additional mkview parameters of the job. The “-host” part of the comment fakes ClearToolExec.java into thinking I specified a view storage host and it skips the cmd.add(parameters.getViewStorage().getCommandArguments()); in the switch statement.