You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The pipeline have multiple steps, some of them are parallel, and some of them have post conditions that run on failure and always.
The problem is that the jobs are not getting re-submited by the EC2 Fleet plugin when spot instances goes down. When i watch my Pipeline console i see that the steps of the stages are getting aborted, but the post condition fails because the agent is already disconnected.
The logs got this at the aborted step
[60] Cannot contact i-0cf5f2bc3900a0408: hudson.remoting.ChannelClosedException: Channel "hudson.remoting.Channel@2a50c887:i-0cf5f2bc3900a0408": Remote call on i-0cf5f2bc3900a0408 failed. The channel is closing down or has closed down
[61] Could not connect to i-0cf5f2bc3900a0408 to send interrupt signal to process
But then in the post condition fails with
Found unhandled org.jenkinsci.plugins.workflow.support.steps.AgentOfflineException exception:
Unable to create live FilePath for i-0cf5f2bc3900a0408; agent-a i-0cf5f2bc3900a0408 was marked offline: Connection was broken
So the build is marked as failed because the post condition fail becaue the agent is offline (spot terminated)
But the plugin is not sending the rebuild of the job, neither im seeing any logs from the plugin resubmiting as seen in #45.
¿Is there a way to make the plugin resubmit even if a post condition is failes?
¿Is this really the problem or could be another thing?
If the problem is really in the post condition. ¿How could i rewrite the pipeline to make the plugin actually resubmit the job?
To Reproduce
Make a Jenkins Pipeline Syntax with parallel stages and post conditions
Wait unit a spot instance terminate
See that the post condition failed
The Job is not resubmitted automatically.
** Logs **
Tip: See this guide to configure a logger in Jenkins UI. Please attach fine logs if you think they are relevant.
Environment Details
Spot Fleet or ASG?
Spot Fleet
Linux or Windows?
Linux
The text was updated successfully, but these errors were encountered:
Issue Details
Currently Im running a Pipeline Job that is something as follow:
The pipeline have multiple steps, some of them are parallel, and some of them have post conditions that run on
failure
andalways
.The problem is that the jobs are not getting re-submited by the EC2 Fleet plugin when spot instances goes down. When i watch my Pipeline console i see that the steps of the stages are getting aborted, but the post condition fails because the agent is already disconnected.
The logs got this at the aborted step
But then in the post condition fails with
So the build is marked as failed because the post condition fail becaue the agent is offline (spot terminated)
But the plugin is not sending the rebuild of the job, neither im seeing any logs from the plugin resubmiting as seen in #45.
¿Is there a way to make the plugin resubmit even if a post condition is failes?
¿Is this really the problem or could be another thing?
If the problem is really in the post condition. ¿How could i rewrite the pipeline to make the plugin actually resubmit the job?
To Reproduce
** Logs **
Tip: See this guide to configure a logger in Jenkins UI. Please attach
fine
logs if you think they are relevant.Environment Details
Spot Fleet or ASG?
Spot Fleet
Linux or Windows?
Linux
The text was updated successfully, but these errors were encountered: