• Type: Bug
• Resolution: Fixed
• Priority: Minor
• Component/s: jenkinsfile-runner
• Labels:

  • ci.jenkins.io
  • triaged

[JENKINS-56632] Jenkinsfile Runner CI Pipeline is unstable

Oleg Nenashev created issue - 2019-03-20 11:39

Oleg Nenashev made changes - 2019-03-20 11:41

Description

Original: [https://github.com/jenkinsci/jenkinsfile-runner/blob/master/Jenkinsfile] uses agents with the `docker` label. These agents are permanent agents which do not automatically cleanup workspaces or orchestrate parallel runs. If multiple runs are executed in parallel, it may lead to various workspace collisions.

New: [https://github.com/jenkinsci/jenkinsfile-runner/blob/master/Jenkinsfile] uses agents with the `docker` label. These agents are permanent agents which do not automatically cleanup workspaces or orchestrate parallel runs. If multiple runs are executed in parallel, it may lead to various workspace collisions.   Acceptance criteria:  * Jenkinsfile is updated to prevent collision of workspaces in parallel builds  * Jenkinsfile automatically cleanups workspaces when the build succeeds or fails during the execution... for all stages utilizing the node

Francisco Fernández made changes - 2019-03-21 09:09

Assignee

New: Francisco Fernández [ fcojfernandez ]

Francisco Fernández made changes - 2019-03-21 09:09

Status

Original: Open [ 1 ]

New: In Progress [ 3 ]

Francisco Fernández made changes - 2019-03-21 09:10

Link

New: This issue is blocked by INFRA-2057 [ INFRA-2057 ]

Baptiste Mathus made changes - 2019-03-21 09:17

Labels

Original: ci.jenkins.io

New: ci.jenkins.io triaged

Francisco Fernández made changes - 2019-03-26 16:28

Remote Link

New: This issue links to "PR#101 (Web Link)" [ 22527 ]

Oleg Nenashev made changes - 2020-08-07 06:58

Resolution		New: Fixed [ 1 ]
Status	Original: In Progress [ 3 ]	New: Resolved [ 5 ]