[royale-asjs.wiki] branch master updated: add note about not storing credentials in git config

[ah...@apache.org]

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 06374ec  add note about not storing credentials in git config
06374ec is described below

commit 06374ec1273b38e7f10da79d1e98c10fa4e337de
Author: aharui <ah...@apache.org>
AuthorDate: Wed Apr 1 00:38:25 2020 -0700

    add note about not storing credentials in git config
---
 Release-Manager-Notes.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/Release-Manager-Notes.md b/Release-Manager-Notes.md
index 5680277..d77368e 100644
--- a/Release-Manager-Notes.md
+++ b/Release-Manager-Notes.md
@@ -278,6 +278,10 @@ There are at least two ways of creating release artifacts:
 A) Using the CI Server (Instructions below)
 B) [Using the releasecandidate.xml scripts](Creating-Releases-With-releasecandidate-xml)
 
+NOTE:  The CI Server is "shared" so credentials should not be stored on that machine.  The Git config credential.helper should not appear in `git config --list`.  If it does, use `git config --unset credential.helper` to unset it.  You may need to add `--global` or `--system` parameters as well.
+
+Similarly, do not set the Git config user.name or user.email on the CI server.  The CI jobs should ask for a user.name and set it on the command-line.  If you need to do a manual commit Git will tell you to set the config properties, but don't do it.  Use `git -c user.name="My Name" -c user.email="a@b.c" commit` instead.
+
 The release scripts assume that each of the 3 repos is properly versioned.  The scripts assume that the version numbers in certain files reflect the version being released.  The RM may need to verify that the following files have the following versions:
 A) All pom.xml files have the SNAPSHOT version of the release.  So if releasing 0.9.4, then the pom.xml files should be version 0.9.4-SNAPSHOT.  There are some properties with versions in the pom.xml files that may need to be upgraded to 0.9.4 as well.
 B) build.properties lists the correct version (without -SNAPSHOT).