• Type: Bug
• Resolution: Unresolved
• Priority: Major
• Component/s: workflow-api-plugin, workflow-job-plugin
• Labels:

  None
• Environment:

  Amazon EC2

[JENKINS-65199] "no such computer EC2" error using github webhook

Alan MD created issue - 2021-03-22 20:44

Alan MD made changes - 2021-03-22 20:45

Description

Original: I use a pipeline build triggered by github webhooks using the dynamic EC2 nodes (Amazon EC2 plugin). "_GitHub hook trigger for GITScm polling"_ is checked and I'm using _"Additional Behaviors -> Polling ignores commits in certain paths"_.  When using dynamic EC2 agents, build is not triggered and I see the following message in the logs: {code:java} {code} _"no such computer EC2 (agent) - agent id"_ EC2 agents are not provisioned and build will not start, this is a bug which affects a lot of teams in a production environment.

New: I use a pipeline build triggered by github webhooks using the dynamic EC2 nodes (Amazon EC2 plugin). "_GitHub hook trigger for GITScm polling"_ is checked and I'm using _"Additional Behaviors -> Polling ignores commits in certain paths"_.  When using dynamic EC2 agents, build is not triggered and I see the following message in the logs: _"no such computer EC2 (agent) - agent id"_ EC2 agents are not provisioned and build will not start, this is a bug which affects a lot of teams in a production environment.

Collapse comment: Elijah Lynn added a comment - 2021-11-04 18:07

Elijah Lynn added a comment - 2021-11-04 18:07

Crosslinking similar issue: https://issues.jenkins.io/browse/JENKINS-46468

Expand comment: Elijah Lynn added a comment - 2021-11-04 18:07

Elijah Lynn added a comment - 2021-11-04 18:07 Crosslinking similar issue:  https://issues.jenkins.io/browse/JENKINS-46468