-
Improvement
-
Resolution: Won't Fix
-
Minor
-
Centos
Instead to have a static box for filling the Testlink Job Configuration, it would be quite useful if you could implement the dropdownlist for each field configuration:
Testlink Version
Test Project Name
Test Plan Name
Then choosing the Testlink version the field "test project name" will show the list of projects for that testlink version, and once you have chosen it the field testplan name will show the list of test plans for that test project.
Please find attached a couple of snapshot (only TestLink Version and Test Project Name)
Regards
[JENKINS-13175] Testlink Job Configuration using dropdownlist instead static box
Just a quick note here. I believe what we want, the Mantis plug-in already does 
Tonight I will work on TL XML-RPC API, then I will have a look on the methods that we need.
Cheers, Bruno
I've stopped the work here, as I'm working on TestLink at moment. There will be a release of 1.9.4 in July/August, so I'll try to include the necessary methods in the XML-RPC before so. Will update this issue as soon as I've finished testing with TestLink 1.9.4 alpha (the alpha tests start in June/July).
Cheers
Hi Victor, unfortunately it would require a lot of JavaScript hack, as well as handling multiple comboboxes. Feel free to submit a pull request if you are able to work on this feature, but you would have to update the test plans according to the test project selected, and update it if the user changed the project combobox.
The issue will be archived, and can be reopen in the future, if anyone is willing to give it a try. Thanks!
Hmmmm, great idea Victor!
I will have to look at TestLink XML-RPC API to check if it has all the methods. We need a method for retrieving all test projects, one for all test plans of certain test project, and so on.
Give me some time to analyse this possibility and I'll see if we can include this in the next release.
What about the build name? In certain cases, I believe the user would like to have the possibility to define a custom build name using environment variables. In most of my jobs I use some simple name plus the build ID, this helps me track the job in Jenkins if needed.
Thank you!