| Table of Contents |
|---|
Links
...
- Move to the folder at the root of your development directory. For example:
cd C:\Users\<user>\Documents\work
- Add a remote pointer to the Gerrit server that hosts your repository using either SSH or HTTPS. (Note: <REPONAME>s are given in various Development Guides.
Using SSH:git remote add origin ssh://USERNAME@gerrit.onap.org:29418/<REPONAME>
Using HTTPS:
With HTTPS, first you will need the Gerrit HTTP-generated password for each HTTPS operation with Gerrit/Git.
git remote add originhttps://USERNAME@gerrit.onap.org/r/a/<REPONAME>
- Now clone the remote repository. Since we clone in the current folder, it will create a subfolder with the remote copy.
Using SSH:git clone ssh://USERNAME@gerrit.openecomponaponap.org:29418/<REPONAME>
Using HTTPS:
With HTTPS, first you will need the Gerrit HTTP-generated password for each HTTPS operation with Gerrit/Git.
git clone https://USERNAME@gerrit.onap.org/r/a/<REPONAME>
...
Sometimes automatic verification/build/deploy doesn't happen as expected. In that case, use the gerrit Reply feature to insert the magic word into the message body.
| Action Desired | Magic Words | Result |
|---|
| trigger the verify job | recheck | re-runs the Jenkins Job Builder (JJB) on an unmerged set of code | |||||||||||||
| trigger check of self release | recheck|reverify | will trigger the "{project-name}-release-verify-{stream}" job. Will make sure the release file contains the needed information and that the candidate exists. (NOTE: possible confusion here over syntax...is that bar (|) to be included or can you use either of these words in the Reply?) Ref: Self Releases Workflow (Nexus2) | |||||||||||||
| trigger the helm verify job | verify-helm | re-runs the JJB verify-helm job used in the OOM project | |||||||||||||
| trigger the merge build Jenkin job | remerge | re-runs the JJB deploy on a merged set of code | |||||||||||||
| trigger self release of artifact | remerge | runs the "{project-name}-release-merge-{stream}" job to push the release and tag the repo. Ref: Self Releases Workflow (Nexus2) | |||||||||||||
| trigger daily release job | please release | re-runs the JJB daily release build | |||||||||||||
| stage-release | re-runs the JJB daily maven-stage build (replaces "please release") | ||||||||||||||
| trigger CLM jobs | run-clm | The CLM jobs are still scheduled to run every Saturday, this feature can be useful for debugging on demand. Commenting "run-clm" in a gerrit that is not merged, will not trigger the CLM job based on that revision but will trigger the job based on the tip of the branch. This job is designed to always run on the latest tip of the branch to avoid inconsistencies on the reports. Source: Configuring Gerrit | |||||||||||||
| trigger Sonar job | run-sonar | this is used to follow up closely on code coverage progress. | |||||||||||||
| rebase | N/A | There is no magic word for this desired action. Instead, hit the button in the review page. | |||||||||||||
trigger OOM CD deployment / healthcheck for component under review | run-helm-deploy | 20181122 - in progress
will run an OOM deploy of the component and any dependent component on request (before a merge) for example if the current helm-verify job is +1 - a full deploy of the component via --set <pod>.enabled=true will be done, healthcheck run and reported back as a +1 if we get a pass for the pod Example of what the jjb job will run when deploying pomba - requires dmaap to function.
| |||||||||||||
| Re-run CI Deployment test | oom_redeploy | Re-runs the remote CI oom deployment job in Orange Lab | |||||||||||||
| Create Jenkins job in Sandbox | Posting this |