This is an automated email from the ASF dual-hosted git repository.
piotrz pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/royale-asjs.wiki.git
The following commit(s) were added to refs/heads/master by this push:
new e99f90e Update instruction with fail and revert section
e99f90e is described below
commit e99f90ee20ab63332d7a49f6738793304d5b2fbd
Author: Piotr Zarzycki <[email protected]>
AuthorDate: Wed Jul 24 09:38:42 2019 +0200
Update instruction with fail and revert section
---
Release-Steps-Jobs-On-Jenkins.md | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/Release-Steps-Jobs-On-Jenkins.md b/Release-Steps-Jobs-On-Jenkins.md
index cee8fc7..5602ae4 100644
--- a/Release-Steps-Jobs-On-Jenkins.md
+++ b/Release-Steps-Jobs-On-Jenkins.md
@@ -23,6 +23,12 @@ Similarly, when GPG signatures are required, the RM must
download the artifacts
The various jobs all end by sending an email to [email protected] if successful.
If the emails are not clear, please improve them. The template for the emails
are sort of hidden in a Jenkins job configuration. Go to "Post-Build Actions"
at the bottom of the config page, then choose "Advanced Setting", then find the
"Success" email and choose "Advanced".
+## Fail and Revert
+If you fail on comparing artifacts you will probably have to revert all the
changes which has been done by couple of previous steps. Changes has to be
reverted on created branch for release purposes ex. release/0.9.6
+
+1. If you fail on comparing artifacts on your machine in step **Release Step
003** you should revert everything what has been pushed during perform of steps
from **Release Step 001 If Utils** to **Release Step 003**
+2. If you fail on comparing artifacts on your machine in step **Release Step
007** you should revert everything what has been pushed during perform of steps
from **Release Step 005** to **Release Step 007**
+
### Release Step 001
This step creates the release branch for royale-compiler from the develop
branch using Maven. Maven updates the develop branch to the next version
number which is why it needs a "git push". Then other release steps will
modify the release branch so the email at the end of this step requests that
the RM run two git commands to set up remote origin tracking of the release
branch.
