...
| git clone https://github.com/project-sunbird/sunbird-devops.git cd sunbird-devops && git checkout tags/release-1.14.0 1 -b release-1.14.01 cd deploy/jenkins sudo bash jenkins-server-setup.sh |
...
Name | Value |
|---|---|
ANSIBLE_FORCE_COLOR | true |
ANSIBLE_HOST_KEY_CHECKING | false |
ANSIBLE_STDOUT_CALLBACK | debug |
hub_org | docker hub organization / username eg: In sunbird/player image, sunbird is the hub_org |
private_repo_branch | The branch name in the private repository which you would like to use. This branch will have the inventory and secrets |
private_repo_credentials | The unique string which you provided for ID field while entering the github repo credentials. eg: private-repo-creds |
private_repo_url | The github URL to your private repo. You can visit your private repo and click on clone button, which will display the https URL to your private repository. Only https URL is currently supporrted. |
public_repo_branch | This is the branch or tag from where Jenkinsfile will be picked up. You can set this value as refs/tags/release-1.14.0 1 if you want to build from tags or provide the value of development branch like release-1.15 (not recommened since development branches are not stable). |
...
| Name | Value |
|---|---|
| Library Name | deploy-conf |
| Default version | Tag name of the jenkins shared library. This should be same version of the release you are going to build and deploy. For example, if you decide to use tags release-1.14.0 1 as your base, jenkins shared library tag will be release-1.14.0-shared-lib. When you upgrade to tags release-1.15.0, this value should get changed to release-1.15.0-shared-lib |
| Retrieval method | Modern SCM |
| Source Code Management | Git |
| Project Repository | https://github.com/project-sunbird/sunbird-devops.git |
...