Daniel said 1.561, so this is in the latest LTS, which is great!
Vincent
2014-07-31 14:10 GMT+02:00 Stuart Davidson :
> So that identifier, in the example, is queue id 25. If the job is queued,
> cancelled and queued again, a new identifier (26) will be used. Once a job
> leaves the queue and i
So that identifier, in the example, is queue id 25. If the job is queued,
cancelled and queued again, a new identifier (26) will be used. Once a job
leaves the queue and is building, that queue id is still accessible using
the same restful interface and the build number is now under the
tag.
If t
On 31.07.2014, at 12:36, Stuart Davidson wrote:
> As I understand it, a build could be queued, cancelled, queued again and thus
> end up with the same build id. With this plugin, I'm appending a UUID to the
> build in order to identify a unique run no matter what happened in the queue.
>
> Ho
As I understand it, a build could be queued, cancelled, queued again and
thus end up with the same build id. With this plugin, I'm appending a UUID
to the build in order to identify a unique run no matter what happened in
the queue.
However, you've shown a way of uniquely identifying a build by us
On 31.07.2014, at 12:19, Stuart Davidson wrote:
> I've not touched this in a while Daniel, but I found that if I was queuing
> multiple copies of the same job, I could give it a unique ID - whereas /build
> simply gives you the information it's queuing.
>
> That's not to say that the queue A
I've not touched this in a while Daniel, but I found that if I was queuing
multiple copies of the same job, I could give it a unique ID - whereas
/build simply gives you the information it's queuing.
That's not to say that the queue API has improved to include information
like this - like I say, i
On 21.11.2013, at 20:01, Stuart Davidson wrote:
> The plugin allows you to request a build from the API but it returns a JSON
> snippet with a UUID for the job. This allows you to track the status of a job
> (using another part of the API) even before it has left the queue and has
> been assi
Hi Vincent!
Thanks for getting in touch. Yeah, I always meant to get round to
officially releasing it - the code was here, I was just tidying it up.
If you want to pass my e-mail along, I can talk to them directly and make
sure it does what they are looking for.
Stu
On 31 July 2014 10:23, Vinc
Hi Stuart,
some pinged me today about your plugin, it appears very useful. Maybe it
could be worth to release it properly to have more people know about it and
let them install it directly from the plugin manager?
If you need some help with that I can give a hand.
Cheers,
Vincent
2013-11-21 2
github repo :
https://github.com/jenkinsci/hp-application-automation-tools-plugin
ci job :
https://jenkins.ci.cloudbees.com/job/plugins/job/hp-application-automation-tools-plugin/
2012/11/20 Ofir
> https://github.com/hpsa/hp-application-automation-tools-plugin
>
> בתאריך יום שני, 19 בנובמבר 2012
https://github.com/hpsa/hp-application-automation-tools-plugin
בתאריך יום שני, 19 בנובמבר 2012 23:49:12 UTC+2, מאת domi:
>
> Thats not how it works, just send us the link to your repo, this is much
> easier…
> /Domi
>
> On 19.11.2012, at 12:45, Ofir > wrote:
>
> Plugin name is :hp-application-au
Thats not how it works, just send us the link to your repo, this is much easier…
/Domi
On 19.11.2012, at 12:45, Ofir wrote:
> Plugin name is :hp-application-automation-tools-plugin
> GitHib ID is: hpsa
>
> No need to fork, just create an empty repository
11,This plugin allows to run HP Quick Test Professional and HP Service
Test tests from file system and from Quality Center 10
More information can be found
here:
https://wiki.jenkins-ci.org/display/JENKINS/HP+Application+Automation+Tools
בתאריך יום שני, 19 בנובמבר 2012 13:45:26 UTC+2, מאת Ofi
Plugin name is :hp-application-automation-tools-plugin
GitHib ID is: hpsa
No need to fork, just create an empty repository
14 matches
Mail list logo
