|
||||||||
|
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/d/optout.

Thanks for the insight. I'm just getting into the jenkins world. I am not in dire need of this, it was just a thought that came to mind. I am getting around it by adding a parameter with a uuid that I can more reliably track.
I do think that this would be a core feature, not a plugin. It deals with core components and core apis. Any user who wants to build a job tracking system using the API's will run into the same challenges. I think having something like this would solve that issue.