|
||||||||
|
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/d/optout.
I started working on this improvement and it turns out it's a significant impact to make the plugin compatible with both nodelabelparameter and parameterized-trigger. I hope we're not opening a Pandora box![]()
I have already covered the label's page and the main dashboard page, still have to work on the computer's page.
Stefan, I have a few questions for you.
Do you have a test or staging instance where you could help me to test the plugin before I release it? I created test data based on your comments but I don't use these plugins so it may not be comprehensive.
Also, besides the scenario you detailed in your screenshots, is there any other possible interaction (via labels) between labellinkedjobsplugin, nodelabelparameter, and parameterized-trigger?
I will attach screenshots of my current progress once Jira let me do so. Disk seems full at the moment.
Finally I found a limitation that will remain for now : nodelabelparameter allows use of TokenMacro. From my initial research, TokenMacro requires an AbstractBuild to expand tokens, and I only have access to AbstractProject in my plugin. In other words, I can't trigger a build for all jobs to expand macros to build the label's pages... to be continued.