New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Jenkins: retry problematic stages #3146
Comments
@mpranj thank you for making us aware of this. @ingwinlu @Mistreated do you know something about this? |
As far as I know we do not use the “declarative pipeline syntax”, but the older “scripted pipeline syntax”. This means we most probably will never be able to restart stages, unless we switch to the more modern (but also more limited) declarative pipeline style. See also: #2927 (comment) |
Yes, https://issues.jenkins-ci.org/browse/JENKINS-45455 says it is only declarative pipeline. According to https://stackoverflow.com/questions/38129745/jenkins-build-pipeline-restart-at-stage the "retry" might be better suited than https://wiki.jenkins.io/display/JENKINS/Naginator+Plugin (which restarts the whole job, not only parts). @Mistreated Can you please add some retry at the hot-spots? I think this could fix most of #2967 |
Seems to be a wontfix |
According to the pipeline documentation, we should be able to restart individual jobs from stages by clicking a button.
The feature should have been introduced by Pipeline: Declarative version 1.3. We are running 1.3.1 but the feature seems to be missing. Some other plugins are also slightly outdated. Are there any issues blocking us from upgrading everything?
The text was updated successfully, but these errors were encountered: