|
||||||||
|
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Actually for this defect this is a workaround that at least works.
Of course I'm aware of hierarchical VOB tags (which we also use).
In our case we do polling and (Unix) view cleanup on Unix and call the
compile job on the Windows slave, which uses the same view.
Although they have different tags, the compile spec from Unix works on the Windows client.
(ClearCase works with oids, so the Unix view works with Unix compiled rules also on Windows!)
As our PCs are diskless and have no local storage, they use Unix views anyway.
However, if there is one I'd appreciate any other workaround that helps.
This comment was also intended as hint to analyze the issue which seems
to be specifically related to the master/slave platform change.