You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.adoc
+14Lines changed: 14 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -404,6 +404,20 @@ Show pkcs12 information
404
404
405
405
More information about Jenkins Core maintainers and the different roles can be found in https://github.com/jenkinsci/jenkins/blob/master/docs/MAINTAINERS.adoc[MAINTAINERS].
406
406
407
+
== FAQ
408
+
409
+
**The stage release failed and we already push commits during the maven release.**
410
+
411
+
The problem here, is if we re-trigger the release job, we also update the release version again.
412
+
So if the process fails on running `mvn release:stage`, then we can re-trigger it from inside the container as custom parameters are located in `settings-release.xml`.
413
+
414
+
```
415
+
kubectl get pods -n release # Looking for the correct jenkins agent name
* Jenkins docker images are describe from https://github.com/jenkinsci/docker[jenkinsci/docker] repository and deployed to DockerHub as link:https://hub.docker.com/r/jenkins/jenkins[jenkins/jenkins]
0 commit comments