[JIRA] (JENKINS-49403) Pipeline method to get the log of a specific stage

[svano...@cloudbees.com (JIRA)]

Title: Message Title

Sam Van Oort commented on JENKINS-49403   Re: Pipeline method to get the log of a specific stage Ray Kivisto There are much more effective ways to accomplish what you describe (agent health monitoring) rather than embedding it inside pipeline. As a starting point, my go-to would be operations tools for maintaining/monitoring infra – Kubernetes or other Docker-management healthchecks, Nagios or similar platform monitoring, or even a basic script that runs a check and takes the node offline if unhealthy. Failing that, there is probably a plugin to take nodes offline if specific criteria are met or run pre-checks before using them. The Slave Prerequisites plugin might be a good starting point if brought up to date with modern Jenkins. You could also do something custom with Listener APIs. It's simply not maintainable if you mix your CI/CD execution logic with the infra-management/operations logic for the build agent – and it is not future-safe to rely on Pipelines directly invoking on-master APIs to do things like take nodes offline. I'll add in one more fun wrinkle: a Stage simply represents a fragment of the Pipeline Directed Acyclic Graph - that means it can itself include child parallels and stages which may be complete or incomplete. This would make it hard to correctly target an operation at the right node block to take one offline – the logs are more usable for users than for automation. Add Comment   This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.