In a multibranch pipeline, we encountered a situation where there was a branch named "aaa" with a corresponding remote Jenkinsfile repository having the same branch name.
After merging the "aaa" branch into the multibranch pipeline, deleting the remote Jenkinsfile repository for the "aaa" branch, and subsequently recreating the "aaa" branch, the pipeline started using an outdated Jenkinsfile.
couldn't find any cleanup mechanism in place for managing Jenkinsfiles in such scenarios.
To Reproduce
create branch aaa in multibranch + the same aaa branch in remote repo
merge aaa / or delete aaa in multi branch project
delete aaa branch from remote jenkinsfiles repo
4 recreate aaa branch in multibranch - it use the very old Jenkinsfile
Expected behavior
use the latest jenkinsfile
Screenshots
If applicable, add screenshots to help explain your problem.
morgoved
commented
6 months ago
In a multibranch pipeline, we encountered a situation where there was a branch named "aaa" with a corresponding remote Jenkinsfile repository having the same branch name.
After merging the "aaa" branch into the multibranch pipeline, deleting the remote Jenkinsfile repository for the "aaa" branch, and subsequently recreating the "aaa" branch, the pipeline started using an outdated Jenkinsfile.
couldn't find any cleanup mechanism in place for managing Jenkinsfiles in such scenarios.
To Reproduce
Expected behavior use the latest jenkinsfile
Screenshots If applicable, add screenshots to help explain your problem.
Jenkins LTS - 2.414.3 plugin version : 1.24