Is there something we can do to get a higher priority for this idea ? I can image to to sponsor the development effort.

Hi Clemens Gmeiner feel free to contact me off-list if you would like to sponsor this issue.

Cheers
Bruno

Otherwise, if you are in no hurry, it is really not a very complex issue. It would just need to wait until I have time to work on this one (probably near December, unless I have some other project that needs work). I think I also need to update the testlink-java-api for 1.9.19, and was planning on doing that after November, which normally includes going through pending issues.

Hi Clemens Gmeiner,

Closed the issue as Not A Defect. Turns out this feature was implemented long time ago. Took me a moment to find it in the code, and a bit longer to test it.

1. Added a node to Jenkins called "localhost" using the slave.jar
2. Added a fake TestLink installation in global configuration
3. Created a job in Jenkins and for platform name, used "$NODE_NAME"

We are "expanding" (i.e. converting $NODE_NAME to whatever value is bound in Jenkins environment) the following environment variables in the plugin:

• project name
• test plan name
• platform name
• build name
• build notes

See here for code: https://github.com/jenkinsci/testlink-plugin/blob/1235c466a7b460c39f4fba46051082c1d9c214ff/src/main/java/hudson/plugins/testlink/TestLinkBuilder.java#L189-L197

Which means, when you configure these variables in a Jenkins job for the plugin, you can use any of the variables available in Jenkins. So any of this list: https://wiki.jenkins.io/display/JENKINS/Building+a+software+project#Buildingasoftwareproject-belowJenkinsSetEnvironmentVariables

Or any variable defined in plugins that increments this list.

Few screenshots of a quick test with a debugger in Eclipse.

In case I missed something, or it doesn't really solves the issue described here, feel free to point out what is missing and re-open this issue.

Cheers
Bruno