Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

The idea is to automate the build and deployment of various Jenkins jobs to a specific environment based on Github tags.

What is required from the development team?

Development team will create the tag for their respective github repositories using a Jenkins job.

What happens next?

  • We will have a multibranch pipeline jenkins jobs for each build, which will poll the repository every 10 minutes to check if any new tags are created in the repo.

  • if new tag is found, we will check for the time(is it b/w the deployment time slot) and check for the tag pattren(ex : current release branch with RC)

  • once the above check is passed, a new jenkins job will be created by the tag name and starts building

  • Based on the job names, the respective build, upload and deploy jobs will be triggered.

  • we will have a slack notification for all the stages(build, artifact and deploy)

  • No labels