Pipeline jobs hang or existing pipelines are deleted due to connection issues between Jenkins Org folder and Github

Issue

  • If connection between Jenkins Org folder and Github is not stable and Jenkins is unable to properly scan Github, multibranch projects’ children can potentially be removed because Jenkins would think repos/Jenkinsfiles are deleted. As designed, the recomputation should have terminated with an error without touching existing children.
    The “Days to keep old items” setting doesn’t seem to help preventing existing pipelines to be deleted.

  • When this connection issue occurs while a pipeline is running, it may leave orphaned process on a slave.

Environment

  • Cloudbees Jenkins Enterprise

Resolution

Upgrade the CloudBees Folders Plugin.
Version 5.7+ includes fix for JENKINS-33815 to prevent pipelines from being deleted when Jenkins Github org fails to scan Github org repos, for whatever reason. (i.e. Github went down, Github return API limit error), etc.

This version also includes the fix for JENKINS-25240, to prevent deletions on a project with builds running.

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.