- Starting from the master Jenkinsfile, modify the =stages= section to process your workflow (you can use as inspiration the other branches).
- Starting from the master Jenkinsfile, modify the =stages= section to process your workflow (you can use the other branches as inspiration).
- Push the new branch to your GitLab repository.
- Open a merge request on GitLab.
...
...
@@ -51,14 +41,14 @@
When developing a new production version should be pushed using the following commands:
#+BEGIN_EXAMPLE
git tag -f online-myprocess-prod
git push -f --tags online-myprocess
git tag -f master-prod
git push -f --tags master-myprocess
#+END_EXAMPLE
Note that both the tag creation and push to the repository are forced (=-f=).
** Docker images
Docker images for each branch are built by the GitLab CI from the =docker-images= branch.
Docker images are built by the GitLab CI from the =master= branch and the =master-prod= tag.
A description of the content and structure of the image can be found in the [[https://gitlab.cern.ch/cms-ecal-dpg/ECALELFS/automation/-/tree/docker-images][branch README]].