PRs 5 & 6 seem intended to address this?

There are two outstanding pull requests trying to implement workflow integration: pull request 5 and pull request 6.

There is also plan on the Jazz community web site to include support for workflow plugin in RTC Build 6.0.1 (requires free signup).

The initial support for the workflow has been added and the team concert plugin ver 1.9.3 has the work flow support. Refer to link Running documentation for RTC Jenkins plugin workflow support for more details.

Initial support delivered

There are two concerns going around in the customer:

1. There are still open issues (listed under Known Limitations) and the plugin is still under evaluation. Isn't it too early to consider the implementation done and close this issue?

2. The workflow compatibility is a major breakthrough, requires a newer version of Jenkins and, very likely (by our experience) the latest RTC 6.x. Yet, the version increment in the Team Concert plugin was not even minor (from 1.1.9.2 to 1.1.9.3). It's misleading. Some people are updating their plugins thinking it was only a minor bug fix, and suddenly regular freestyle jobs started breaking simply because, as we could guess so far, we use RTC 5.x. Finally, it raises a concern in case the workflow version is not ready for production and there is simply no more room for improvement in the non-workflow version.

We are continuing to work on the workflow support, the equivalent RTC work items are open and actively worked on. Since the initial work is done, resolving the work item would notify users about the support and they can try to use the plugin and file defect for issues.

The changes done to this point to support work flow does not require RTC 6.x, it will work RTC 5.x and the dependency on the workflow template package is optional and not mandatory(we also have made sure that their are no regressions with non-workflow scenarios) thats one of the reasons only minor version is updated. The issue 364161: Remote load rules not working using Jenkins Team Concert Plugin 1.1.9.3 is due to packaging a wrong jar, which we have fixed and not related to workflow support.

Thinking again it would have been less confusing if the version was updated to 1.2.0, will keep this in mind for the future releases

Thanks Kishore! The info about the issue is very valuable. If I understood then, the only way to use Load Rules in RTC 5.x, is to either go back to 1.1.9.2 or go up to 1.1.9.4.

Their was a breaking change in RTC 6.0 (which we realised only at a later stage) which made any version of the Jenkins plugin to fail with RTC 6.0 toolkit when load rules are used. We have fixed the compatibility issue in the current development release and planning to backport it to the RTC 6.0 iFix link 362564: Backport to 6.0 iFix - [361926] Load rules is broken with Jenkins plugin and RTC 6.0 build tool kit
In ver 1.9.3 by mistake the breaking change got added which make the plugin incompatible with RTC 5.x toolkit(for load rules) and work only with RTC 6.x, I have put a fix in ver 1.9.4 which will allow compatibility with RTC 5.x build toolkit. If you are using ver 1.9.3 and RTC 5.x build toolkit the options you have are:
1) Go back to ver 1.9.2
2) Move to 1.9.4.
Note:To update either wait for ver 1.9.4 to reflect in the Jenkins update site or download the plugin from http://maven.jenkins-ci.org:8081/content/repositories/releases/org/jenkins-ci/plugins/teamconcert/1.1.9.4/teamconcert-1.1.9.4.hpi

Hope this clarifies the confusion I created.

Code changed in jenkins
User: Jesse Glick
Path:
COMPATIBILITY.md
http://jenkins-ci.org/commit/workflow-plugin/749c67865b40c293b15aa777ad4f263d23e1e907
Log:
JENKINS-27464 Noting.