[JIRA] [workflow-plugin] (JENKINS-33499) Workflow EC2 Integration - build node not provisioned

4 views
Skip to first unread message

john.d.ament@gmail.com (JIRA)

unread,
Mar 12, 2016, 10:00:02 AM3/12/16
to jenkinsc...@googlegroups.com
John Ament created an issue
 
Jenkins / Improvement JENKINS-33499
Workflow EC2 Integration - build node not provisioned
Issue Type: Improvement Improvement
Assignee: Jesse Glick
Components: workflow-plugin
Created: 12/Mar/16 2:59 PM
Priority: Minor Minor
Reporter: John Ament

When using the workflow plugin, EC2 nodes are not provisioned in parallel. Say that I have two parallel steps that both use a dynamically provisioned EC2 node. These two parallel steps request nodes in a serial fashion.

When using the old pipeline plugin, the build jobs would each request a node and two nodes would get provisioned.

When using the new workflow/pipeline plugin only a single node is provisioned when entering this step. The first step takes the node, and then a second node is requested against EC2.

It would be ideal if the workflow plugin could request 2 nodes to be provisioned in parallel.

Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
Atlassian logo

muadda@gmail.com (JIRA)

unread,
May 19, 2016, 9:36:01 AM5/19/16
to jenkinsc...@googlegroups.com
Alban Crequy commented on Improvement JENKINS-33499
 
Re: Workflow EC2 Integration - build node not provisioned

I have the same issue. Parallel provisioning would be useful to me as well. Do you know of any workaround?

jglick@cloudbees.com (JIRA)

unread,
Aug 2, 2016, 12:16:02 PM8/2/16
to jenkinsc...@googlegroups.com
Jesse Glick assigned an issue to Francis Upton
 

No sample script supplied, so probably just a user error. You need to put node inside parallel, not outside.

Change By: Jesse Glick
Component/s: ec2-plugin
Component/s: workflow-plugin
Labels: workflow
Assignee: Jesse Glick Francis Upton
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
Atlassian logo

john.k.tims@gmail.com (JIRA)

unread,
Nov 17, 2016, 12:41:02 PM11/17/16
to jenkinsc...@googlegroups.com
John Tims updated an issue
Change By: John Tims
Attachment: Screen Shot 2016-11-17 at 10.36.00 AM.png

john.k.tims@gmail.com (JIRA)

unread,
Nov 17, 2016, 12:41:04 PM11/17/16
to jenkinsc...@googlegroups.com
John Tims commented on Improvement JENKINS-33499
 
Re: Workflow EC2 Integration - build node not provisioned

Jesse Glick

stage('get node') {
    parallel 'step1': {
        node('ec2-t2.large') {
            println 'hey from step1'
        }
    }, 'step2': {
        node('ec2-t2.large') {
            println 'hey from step2'
        }
    }
}

results in

[Pipeline] stage
[Pipeline] { (get node)
[Pipeline] parallel
[Pipeline] [step1] { (Branch: step1)
[Pipeline] [step2] { (Branch: step2)
[Pipeline] [step1] node
[Pipeline] [step2] node
[step2] Still waiting to schedule task
[step2] EC2 (i-0166ce7971e70b3ef) is offline
[step1] Still waiting to schedule task
[step1] EC2 (i-0166ce7971e70b3ef) is offline

and here's what the build queue looks like

john.k.tims@gmail.com (JIRA)

unread,
Nov 17, 2016, 12:44:01 PM11/17/16
to jenkinsc...@googlegroups.com
John Tims updated an issue
Change By: John Tims
Attachment: Screen Shot 2016-11-17 at 10.41.36 AM.png

john.k.tims@gmail.com (JIRA)

unread,
Nov 17, 2016, 12:44:03 PM11/17/16
to jenkinsc...@googlegroups.com
 
Re: Workflow EC2 Integration - build node not provisioned

The second agents starts up as soon as the first one is done.

jglick@cloudbees.com (JIRA)

unread,
Nov 23, 2016, 12:43:01 PM11/23/16
to jenkinsc...@googlegroups.com

Not likely a Pipeline bug. Perhaps something broken in the cloud provisioner in this plugin.

tristan@techsoft3d.com (JIRA)

unread,
Dec 15, 2016, 2:08:02 PM12/15/16
to jenkinsc...@googlegroups.com

This is really painful with AMI's that take a significant amount of time to come online (Windows ones, for instance).

Does anyone know if this behavior occurs in non-Pipeline scenarios where multiple freestyle jobs running in parallel request the same node label serviced by the EC2 plugin?

raihaan.shouhell@autodesk.com (JIRA)

unread,
Jun 26, 2019, 4:52:02 AM6/26/19
to jenkinsc...@googlegroups.com
Raihaan Shouhell resolved as Fixed
 

Fixed in 1.40

Change By: Raihaan Shouhell
Status: Open Resolved
Resolution: Fixed
Released As: https://wiki.jenkins.io/display/JENKINS/Amazon+EC2+Plugin
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
Reply all
Reply to author
Forward
0 new messages