This is an automated email from the ASF dual-hosted git repository.
aharui 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 0d864a8 Updated Release Steps Jobs On Jenkins (markdown)
0d864a8 is described below
commit 0d864a8d2a5bcced9beee15b180aec10fa08ba79
Author: aharui <[email protected]>
AuthorDate: Thu Jun 20 10:11:44 2019 -0700
Updated Release Steps Jobs On Jenkins (markdown)
---
Release-Steps-Jobs-On-Jenkins.md | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/Release-Steps-Jobs-On-Jenkins.md b/Release-Steps-Jobs-On-Jenkins.md
index bb60662..0cf891c 100644
--- a/Release-Steps-Jobs-On-Jenkins.md
+++ b/Release-Steps-Jobs-On-Jenkins.md
@@ -1,6 +1,6 @@
The Release Steps jobs on Jenkins are an attempt to break the creation of
release artifacts into several smaller steps and only require that one computer
(the Jenkins server) be configured to create the release artifacts. The
Release Manager must still be configured to VERIFY that the release artifacts
are correct.
-Historically, only one person has been able to run the releasecandidate.xml
scripts successfully. Others reported issues with network connections and
unreliable upload and download of artifacts and dependencies.
+Historically, only one person has been able to run the releasecandidate.xml
scripts successfully. Others reported issues with network connections and
unreliable upload and download of artifacts and dependencies. So, having one
machine configured that we know will work should help others become release
managers and not have to figure out how to configure their machines and
networks.
## Verification
@@ -16,6 +16,8 @@ Similarly, when GPG signatures are required, the RM must
download the artifacts
## Job Details
+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.
+
### 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.
