Note that putting input in a node is not a great idea *in general* as it
ties up the executor (and all the resourced related) for a human to come
along... workflow script allows it but it can cause pain.
On Sunday, December 20, 2015 at 9:48:54 PM UTC+11, Kai H wrote:
>
> Appears to have been fixed in the Jenkins core 1.642 version. I do see the
> Builds in the queue now.
>
> On Sunday, December 20, 2015 at 11:31:11 AM UTC+1, Kai H wrote:
>>
>> Hi,
>>
>> I tried this "adapted" example from the the TUTORIAL.md:371 ff:
>>
>> node ('a-specific-node-with-one-executor') {
>> input "Just stall the build for a while"
>> }
>>
>> When I run this twice in parallel, the first build will be running on the
>> executor and waiting for me to click on Proceed. The second job appears as
>> pending in the project, yet when I look at the overall Jenkins build queue
>> there is no trace of it at all. The document claims it would be shown as
>> "part of <myJobName>" in the global Jenkins build queue. What am I missing?
>>
>> Kai.
>>
>
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" 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-users/f58f569e-6aa6-46ac-8618-e7cff29a2a66%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
