jenkinsci / jenkinsci/workflow-basic-steps-plugin
[JENKINS-46582] stash / unstash pipeline step is not preserving files timestamp
- Lingua principale
- Java
- Stelle
- 73
- Fork
- 129
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Descrizione
I'd like to checkout some source code once, and incrementally build it in parallel with different compilation options, using the following pipeline:
node {
checkout scm
stash name: 'sources'
}
parallel (
'release': {
node() {
unstash 'sources'
make BUILD=release
}
},
'debug': {
node() {
unstash 'sources'
make BUILD=debug
}
}
)
It is working almost fine. The issue is that at each build, the full source code is rebuild, even if running on the same node than previous compilation.
The root cause is the untash step which is not preserving the initial file timestamp. Therefore my build system supposed every files has been modified since the last build.
---
Originally reported by jguigui, imported from: stash / unstash pipeline step is not preserving files timestamp
Raw content of original issue
I'd like to checkout some source code once, and incrementally build it in parallel with different compilation options, using the following pipeline:
node {
checkout scm
stash name: 'sources'
}parallel (
'release': {
node() {
unstash 'sources'
make BUILD=release
}
},'debug': {
node() {
unstash 'sources'
make BUILD=debug
}
}
)
It is working almost fine. The issue is that at each build, the full source code is rebuild, even if running on the same node than previous compilation.
The root cause is the untash step which is not preserving the initial file timestamp. Therefore my build system supposed every files has been modified since the last build.
environment
```
Jenkins 2.76
Linux
```
Guida per i contributori
Apri la guida per i contributori
Direzione di ricerca
Inizia dall’implementazione di workflow-basic-steps-plugin alla base dei passaggi della pipeline stash e unstash, usando la pipeline parallela fornita come caso di riproduzione. Verifica come vengono ripristinati i file su Linux e individua la copertura dei test esistente; il lavoro è completato quando unstash preserva i timestamp originali dei file sorgente, così che le build incrementali non ricostruiscano i file invariati.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- java
- Ambito
- build-system, ci-cd
- Tipo di issue
- Bug
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Stato di attività
- Ferma
- Chiarezza
- Abbastanza chiara
- Idoneità per principianti
- 35/100