[JIRA] (JENKINS-57946) No notification when Jenkins fails to check out a pipeline script
Title: Message Title TOURLONNIAS Laureny commented on JENKINS-57946 Re: No notification when Jenkins fails to check out a pipeline script I actually find it very unfortunate that an error in the job falling due to GIT is not manageable. It seems very surprising that this is not planned. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199922.1560206168000.9600.1576570980183%40Atlassian.JIRA.
[JIRA] (JENKINS-57946) No notification when Jenkins fails to check out a pipeline script
Title: Message Title A B created an issue Jenkins / JENKINS-57946 No notification when Jenkins fails to check out a pipeline script Issue Type: Bug Assignee: Unassigned Components: pipeline Created: 2019-06-10 22:36 Priority: Major Reporter: A B Jenkins SCM pipeline doesn't provide any action for when the pipeline script can't be fetched. I only just found out a job (which used to work fine) had been failing for months just because it wasn't able to access its pipeline script from the SCM. It fails the #1 feature of a CI system: notify me when things go wrong. This is a dealbreaker IMHO in terms of making pipeline jobs usable, and violates basic error handling practices (don't ignore errors). There should be way to define notification actions for when the "checking out the pipeline script" step fails. This was using Jenkins 2.138.2 with Pipeline 2.6. Add Comment
