jenkinsci / jenkinsci/workflow-basic-steps-plugin

[JENKINS-41931] unstash fails transiently

Aperta
#424 1 commento 0 reazioni 0 assegnatari Vedi su GitHub
component:workflow-basic-steps-plugin imported-jira-issue priority:minor resolution:unresolved
Lingua principale
Java
Stelle
73
Fork
129
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Descrizione

sometimes the unstash command doesnt actually unstash the files and the pipeline fails. if i rerun the pipeline again it works.

below are the screen caps of the directory listing for my job, and the failure message i get.

please let me know what else you would like to see

---
Originally reported by plainsane, imported from: unstash fails transiently


  • status: Open
  • priority: Minor
  • component(s): workflow-basic-steps-plugin
  • resolution: Unresolved
  • votes: 1
  • watchers: 4
  • imported: 20251215-220547

Raw content of original issue

sometimes the unstash command doesnt actually unstash the files and the pipeline fails. if i rerun the pipeline again it works.

below are the screen caps of the directory listing for my job, and the failure message i get.

please let me know what else you would like to see

  • environment: linux/mesos/marathon/docker

3 attachments

- [Jenkinsfile](https://issues.jenkins.io/secure/attachment/35885/Jenkinsfile)
- [Screenshot_20170210_103059.png](https://issues.jenkins.io/secure/attachment/35886/Screenshot_20170210_103059.png)
> ![Screenshot_20170210_103059.png](https://issues.jenkins.io/secure/attachment/35886/Screenshot_20170210_103059.png)
- [Screenshot_20170210_103243.png](https://issues.jenkins.io/secure/attachment/35884/Screenshot_20170210_103243.png)
> ![Screenshot_20170210_103243.png](https://issues.jenkins.io/secure/attachment/35884/Screenshot_20170210_103243.png)

Guida per i contributori

Apri la guida per i contributori

Direzione di ricerca

Start by reviewing the attached Jenkinsfile and the two failure screenshots, then investigate the reported unstash failure in the stated Linux/Mesos/Marathon/Docker environment. Reproduce the transient pipeline failure and determine what evidence is needed to identify the cause; done means the failure is understood and a verified fix or next diagnostic step is documented.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Valutazione

Stack tecnologico
docker, java, linux
Ambito
ci-cd, devops
Tipo di issue
Bug
Difficoltà
4/5
Tempo stimato
3-5 giorni
Stato di attività
Ferma
Chiarezza
Da chiarire
Idoneità per principianti
25/100

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.