Re: How to check the actual assigned label of a queued build via REST API?

> > we use Go but you can use curl or any HTTP client, it is something like > this > > JENKINS_CRUMB=$(curl --silent > "$JENKINS_URL/crumbIssuer/api/xml?xpath=concat(//crumbRequestField,\":\",//crumb)") > curl --silent -X POST -H "${JENKINS_CRUMB}" -F "script= ${JENKINS_URL}/scriptText > >

How to check the actual assigned label of a queued build via REST API?

Do you do that remotely? Like injecting a script using the jenkins-cli.jar? I considered using the REST API to fetch the labels of the node referenced in the "why" message, but that would be meaningful only if the node had a single label. For multiple labels, again, I would be unable to tell

How to check the actual assigned label of a queued build via REST API?

I would like to use the REST API to get the list of queue builds and their respective "assigned label". Basically, I need to know that a build is waiting in the queue for a node with label X. Through the REST API (*/queue/api/json?pretty=true*) I'm able to get the reason *why *the build is

Pipeline that iterates over Build Results from another job

I would like to create a pipeline that every couple of weeks will make a quality assessment based on the archived artefacts of another job. In short, it has to iterate over all the builds from that given job, for a given period of time, fetch one of the archived files from them and perform an

Access to http://jenkins-ci.org/census

>From Usage Statistics Privacy Advisory 2016-03-30 : As soon as we found out about this bug, we disabled third party access to > the partially decrypted data at http://jenkins-ci.org/census Is there

Re: play-autotest-plugin no longer available

> mailing list :) > > > On 10/02/16 02:01, Rafael Rezende wrote: > > Ok. > > Could it be caused by the mismatching between the artifactId and the > > wiki page Id (if there is such a thing)? > > > > The first maintainer assigned artifactId "play-a

Re: play-autotest-plugin no longer available

xists and was still rejected. I > suggest we wait a bit to see whether this resolves itself, otherwise I'll > need to investigate. > > On 08.02.2016, at 10:46, Rafael Rezende <rafaelrez...@gmail.com> wrote: > > > The current release (1.0.0) and the archive pages are una

play-autotest-plugin no longer available

The current release (1.0.0) and the archive pages are unavailable (404 not found) from the plugin's wiki: https://wiki.jenkins-ci.org/display/JENKINS/play-plugin Archive link: http://updates.jenkins-ci.org/download/plugins/play-autotest-plugin/ Current version: