Change build-node to centos for plugin

[ci-management.git] / Sandbox_Setup.md

diff --git a/Sandbox_Setup.md b/Sandbox_Setup.md
old mode 100755 (executable)
new mode 100644 (file)
index 42ed608..abdc7c7
--- a/Sandbox_Setup.md
+++ b/Sandbox_Setup.md
@@ -25,8 +25,9 @@ please send email to helpdesk@onap.org (LF helpdesk team)
 To download **ci-management**, execute the following command to clone the
 **ci-managment** repository.
 
-`git clone ssh://<LFID>@gerrit.onap.org:29418/ci-management --recursive && scp -p -P 29418 \
-<LFID>@gerrit.onap.org:hooks/commit-msg ci-management/.git/hooks/`
+`git clone https://gerrit.onap.org/r/ci-management && (cd ci-management && curl -Lo \
+$(git rev-parse --git-dir)/hooks/commit-msg https://gerrit.onap.org/r/tools/hooks/commit-msg; \
+chmod +x $(git rev-parse --git-dir)/hooks/commit-msg)`
 
 Make sure to sync global-jjb submodule using:
 
@@ -51,7 +52,7 @@ jenkins-jobs test --recursive jjb/
 
 Backup the jenkins.ini.example to jenkins.ini
 
-`cp jenkins.ini.example jenkins.ini`
+`cp jenkins.ini.example ~/.config/jenkins_jobs/jenkins_jobs.ini`
 
 After copying the jenkins.ini.example, modify `jenkins.ini` with your
 **Jenkins LFID username**, **API token** and **ONAP jenkins sandbox URL**
@@ -72,7 +73,9 @@ ignore_cache=True
 ```
 ### How to retrieve API token?
 Login to the [Jenkins Sandbox](https://jenkins.onap.org/sandbox/), go to your user
-page by clicking on your username. Click **Configure** and then click **Show API Token**.
+page by clicking on your username. Click **Configure** and then click **Add new Token**.
+After that specify a token name (optional) and click on **Generate** to generate and show
+new token. Please note down your token and store it securely.
 
 To work on existing jobs or create new jobs, navigate to the `/jjb` directory where you
 will find all job templates for the project.  Follow the below commands to test,
@@ -83,9 +86,9 @@ update or delete jobs in your sandbox environment.
 After you modify or create jobs in the above environment, it's good practice
 to test the job in sandbox environment before you submit this job to production CI environment.
 
-`jenkins-jobs --conf jenkins.ini test jjb/ <job-name>`
+`jenkins-jobs test jjb/ <job-name>`
 
-**Example:** `jenkins-jobs --conf jenkins.ini test jjb/ sdc-master-verify-java`
+**Example:** `jenkins-jobs test jjb/ sdc-master-verify-java`
 
 If the job you’d like to test is a template with variables in its name, it must be
 manually expanded before use. For example, the commonly used template `sdc-{stream}-verify-java`
@@ -96,7 +99,7 @@ specified JJB job name.
 
 Execute the following command to pipe-out to a directory:
 
-`jenkins-jobs --conf jenkins.ini test jjb/ <job-name> -o <directoryname>`
+`jenkins-jobs test jjb/ <job-name> -o <directoryname>`
 
 The output directory will contain files with the XML configurations.
 
@@ -107,9 +110,9 @@ outputting valid XML descriptions of Jenkins jobs. Upon successful
 verification, execute the following command to update the job to the
 Jenkins sandbox.
 
-`jenkins-jobs --conf jenkins.ini update jjb/ <job-name>`
+`jenkins-jobs update jjb/ <job-name>`
 
-**Example:** `jenkins-jobs --conf jenkins.ini update jjb/ sdc-master-verify-java`
+**Example:** `jenkins-jobs update jjb/ sdc-master-verify-java`
 
 ## Trigger jobs from Jenkins Sandbox:
 
@@ -132,9 +135,9 @@ details and the console output.
 
 Execute the following command to Delete a job from Sandbox:
 
-`jenkins-jobs --conf jenkins.ini delete jjb/ <job-name>`
+`jenkins-jobs delete jjb/ <job-name>`
 
-**Example:** `jenkins-jobs --conf jenkins.ini delete jjb/ sdc-master-verify-java`
+**Example:** `jenkins-jobs delete jjb/ sdc-master-verify-java`
 
 The above command would delete the `sdc-master-verify-java` job.