Parameterized Build - Build Queue Display of parameters?

[Martin B.]

When I use the [Parameterized
Build](https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Build)
Jenkins will automatically enqueue new parameter permutations.

That is, say I have a few parameters, when I start a new build with
exactly the same parameters as a build that is already *waiting* in the
Queue, then this new build will not be enqueued (just like with normal
Jobs, where a job is never enqueued more than once to the build queue).

When I start the Job with a *different* parameter-set than the one(s)
already waiting in the build queue of Jenkins, it *will* be enqueued.

This is excellent :-)

However, there is one small problem:

**Can I somehow have the build queue (the waiting Jobs) display which
parameters which entry has (without mouseover)?**

You see, when we have enqueued a few items of the same Job, but with
different parameters, it's pretty difficult to differentiate which entry
in the build queue is which.

I have found that the parameters are displayed when I mouse over the
Build Queue entries, but

* This is not very eye-friendly
* On the JOb page, where the enqued items of this Job are displayed,
this info doesn't seem to be available.

Any ideas?

cheers,
Martin

[danny staple]

Build a plugin? We do usually use an http request to set the description to include important bits of info as soon as the job starts, but it would be good to know what's queued. We heavily use parameterised jobs, and regularly have them run concurrently.

--
Danny Staple

Director, ODM Solutions Ltd
w: http://www.odmsolutions.co.uk
Blog: http://orionrobots.co.uk/blog1-Danny-Staple

[Martin B.]

> Build a plugin

Yeah. Well. Errm. I'm a C++ programmer not doing any Java development
normally, so the barrier to entry for building a plugin is even higher
for me :-) (Apart from simply lacking time.)

> usually use an http request to set the description
> to include important bits of info as soon as the job starts

I'm afraid I do not quite follow here. Is it somehow possible to extract
the "mouseover info" with the parameters via the xml/json API?

cheers,
Martin

On 14.07.2011 08:15, danny staple wrote:
> Build a plugin? We do usually use an http request to set the description
> to include important bits of info as soon as the job starts, but it
> would be good to know what's queued. We heavily use parameterised jobs,
> and regularly have them run concurrently.
>
> On 13 July 2011 15:35, Martin B. <0xCDC...@gmx.at

> <mailto:0xCDC...@gmx.at>> wrote:
>
> When I use the [Parameterized

> Build](https://wiki.jenkins-__ci.org/display/JENKINS/__Parameterized+Build
> <https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Build>)

[danny staple]

On 14 July 2011 08:01, Martin B. <0xCDC...@gmx.at> wrote:

> Build a plugin

Yeah. Well. Errm. I'm a C++ programmer not doing any Java development normally, so the barrier to entry for building a plugin is even higher for me :-) (Apart from simply lacking time.)

I know - it was kind of flippant. I've got many plugins I would write - had I the time. Also not normally a Java developer here (mostly C/bash/python). I definitely think stuff to handle parameterized and concurrent jobs can be improved, and would like to have time to sort some of it out a bit.
 

> usually use an http request to set the description
> to include important bits of info as soon as the job starts

I'm afraid I do not quite follow here. Is it somehow possible to extract the "mouseover info" with the parameters via the xml/json API?

Nothing quite so clever - what I meant is that as the job starts, I use the environment variables to construct a string, URL encode it, and then put that into an http request (via curl/wget) that sets the job description. Something like:

wget --quiet "${BUILD_URL}/submitDescription?description=${TEST_NAME}+on+${PLATFORM_TYPE}" --no-proxy --http-user=xxx --auth-no-challenge --http-password="xxx"  -O /dev/null > /dev/null

A very neat thing to know is that the description text there can be html - so you can put things like Rerun buttons in there.

Thanks,
Danny

[Martin B.]

> Nothing quite so clever - what I meant is that as the
> job starts, I use the environment variables to
> construct a string, URL encode it, and then
> put that into an http request (via curl/wget) that
> sets the job description. Something like:
>

> wget --quiet "${BUILD_URL}/submitDescription?description= ...
>

Ah! Very nice!

Obviously it doesn't help me for the queue (as the Job hasn't started
yet), but good to know nonetheless!

cheers,
Martin

On 14.07.2011 12:03, danny staple wrote:
> On 14 July 2011 08:01, Martin B. <0xCDC...@gmx.at

> <mailto:0xCDC...@gmx.at <mailto:0xCDC...@gmx.at>>> wrote:
>
> When I use the [Parameterized
>

> Build](https://wiki.jenkins-____ci.org/display/JENKINS/____Parameterized+Build <https://wiki.jenkins-__ci.org/display/JENKINS/__Parameterized+Build>
> <https://wiki.jenkins-ci.org/__display/JENKINS/Parameterized+__Build

> Blog: http://orionrobots.co.uk/__blog1-Danny-Staple

[Danny Staple]

Martin,

I now have new info on this.
This is available inside the REST API.
If you go to :
<your jenkins url>/queue/api/xml

Then you are able to see/query the params of queued jobs. You can also use the json/python data here.

Danny