|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
If build token trigger support is deprecated, why is it still the preferred job trigger mechanism for a continuous integration environment?
Isn't this kind of an essential feature in CI workflows? Also, securing Jenkins in this manner to disallow anonymous access also seems essential in many environments.
I installed the Build Token Root Plugin, but it didn't seem to work. I guess we will go back to polling the SCM.
Seems like regardless, there should be a conclusion to this bug on the Jenkins base distribution.