...
The idea is to automate the build and deployment of various Jenkins jobs to a specific environment based on Github tags.
...
We will read the file deploy.txt from Github repository and then look for the job names updated by the development team.
We will then loop through the file and parse the above Json map to identify what is the build, upload and deploy job.
We will trigger these and wait for completion and then a slack / email notification will be sent.
We will also probably have a array of parameters for the various jobs - This is still in inception and we haven’t decided whether we should have this or anything else, but putting out the idea here -
| Code Block |
|---|
Learner[] = ["private_banrch", "branch_or_tag"]
Yarn[] = ["private_banrch", "branch_or_tag", "jobs_to_deploy"] |
Identifying new entries based on commits:
...
| Code Block |
|---|
git diff d0a5b1f9922dea2a18cff9e6fdcf48a4880ae061 HEAD deploy.txt Learner, | release-2.9.0_RC2 Player, | release_2.9.0_RC6 |
Once we get this info, we will do a loop of this content and trigger the jobs.
...