|
||||||||
|
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.

I see what you mean, I've made few experiments and now I have a better idea of what the "queueItem" actually returns.
I might be wrong, but it seems it would be hard to return informations such as "Ok, I scheduled this task, number is 33 and you will find the build at http://my-jenkins/job/MyJob/33/".
This is what I wanted at first but it seems it would be difficult due to the process, which appears to be:
Maybe it would be ok to attribute a GUID to the queued item, and keep that GUID in the build item.
At some point it could provide an 'Jenkins instance'-wide id for a build item, which seems more reliable than a Job Name + Build Number relation.
I will try to provide a proof of concept by the end of the day.