Adopting changes from issue 26100
24 views
Skip to first unread message
Lakshmi Narasimhan
Dec 6, 2017, 2:15:36 AM12/6/17
to Jenkins Developers
I am trying to adopt the changes required in RTCScm due to changes in Jenkins core API. Links to the Jira issue (https://issues.jenkins-ci.org/browse/JENKINS-26100) and Team Concert Plugin
There is a new method buildEnvironment(Run<?,?.. that needs to be overriden in RTCScm. and this is available in Jenkins Core API 2.60.
Currently Team Concert Plugin is at 1.580.1. I want to keep the Jenkins version the same and just implement the buildEnvironment method in RTCScm. The expectation is that in Jenkins 2.60 and above, the checkout step would find the new method in RTCScm and get the map with the required data. Would this work?
There is a new method buildEnvironment(Run<?,?.. that needs to be overriden in RTCScm. and this is available in Jenkins Core API 2.60.
Currently Team Concert Plugin is at 1.580.1. I want to keep the Jenkins version the same and just implement the buildEnvironment method in RTCScm. The expectation is that in Jenkins 2.60 and above, the checkout step would find the new method in RTCScm and get the map with the required data. Would this work?
Lakshmi Narasimhan
Dec 6, 2017, 7:42:01 AM12/6/17
to Jenkins Developers
I am able to get this working without moving the Jenkins version. Since the method didn't have new types in it's signature, the plugin compiled fine . When deployed in Jenkins 2.6, checkout step returned a map with the required environment variables.
Jesse Glick
Dec 6, 2017, 2:32:21 PM12/6/17
to Jenkins Dev
Right, Java recognizes overloads by signature, not by any bytecode marker, so your trick can work here.
Reply all
Reply to author
Forward
0 new messages