Actually, that still doesn't explain where it gets the build number and URL
for the link to the job.
On Tuesday, 21 February 2017 09:53:09 UTC, Graham Lyons wrote:
>
> OK, so it looks like the /ajaxExecutors endpoint just uses the progress
> value from this data which is why that works.
>
> Any help on the other points would be gratefully received.
>
> Ta,
> G
>
> On Monday, 20 February 2017 17:19:25 UTC, Graham Lyons wrote:
>>
>> Hi,
>>
>> I'm trying to get information about running builds on Jenkins agents,
>> with and without pipelines. 'Old-style' jobs show up just fine but
>> pipelines only ever appear as placeholder tasks:
>>
>> {
>> "currentExecutable": {
>> "_class":
>> "org.jenkinsci.plugins.workflow.support.steps.ExecutorStepExecution$PlaceholderTask$PlaceholderExecutable"
>> },
>> "currentWorkUnit": {
>>
>> },
>> "idle": false,
>> "likelyStuck": false,
>> "number": 1,
>> "progress": 84
>> }
>>
>> I'm using Jenkins ver. 2.19.1 but, looking at the source code, I don't
>> see any changes relating to this in later versions. I could be wrong about
>> that of course.
>>
>> Is this expected? Is there a way to make it behave differently? How does
>> the /ajaxExecutors endpoint get its data?
>>
>> If anyone can help then I'd really appreciate it.
>>
>> Thanks,
>> Graham
>>
>
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/0016a14a-2e72-4115-a13b-409b86a80e99%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
