You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@royale.apache.org by ah...@apache.org on 2019/06/19 19:01:15 UTC

[royale-asjs.wiki] branch master updated: Updated Release Steps Jobs On Jenkins (markdown)

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 fadcf57  Updated Release Steps Jobs On Jenkins (markdown)
fadcf57 is described below

commit fadcf57d3ace8209cb0bb62373b9785f979e7af6
Author: aharui <ah...@apache.org>
AuthorDate: Wed Jun 19 12:01:14 2019 -0700

    Updated Release Steps Jobs On Jenkins (markdown)
---
 Release-Steps-Jobs-On-Jenkins.md | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/Release-Steps-Jobs-On-Jenkins.md b/Release-Steps-Jobs-On-Jenkins.md
index 28fc9ed..bb60662 100644
--- a/Release-Steps-Jobs-On-Jenkins.md
+++ b/Release-Steps-Jobs-On-Jenkins.md
@@ -14,10 +14,16 @@ One reason for so many release steps is that we do not want to store any credent
 
 Similarly, when GPG signatures are required, the RM must download the artifacts to be signed and do the signing locally.  The RM's keys should never be transferred/copied to the CI Server
 
+## Job Details
+
+### 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.
+
 ## Future Improvements
 
 ### Uploading failures
 
 The current steps still require that the RM be able to upload a lot of artifacts to the Nexus Staging Repository and Apache's dist.apache.org.  If folks still have issues with uploads, we can alter the scripts to upload only the PGP signature files from the RM's computer and upload the other artifacts from the CI Server
 
-However, it should be possible to "retry" the uploads by re-running the upload steps locally.
+However, it should be possible to "retry" the uploads by re-running the upload steps locally.
\ No newline at end of file