Add .gitlab-ci.yml

[jgmize]

• Move release notes Jenkins jobs to Gitlab mozmeao/infra#1152
• Run git push conditionally within update_docker.sh
• https://gitlab.com/mozmeao/release-notes/-/jobs/381130486
• after merge:
  • disable Jenkins job
  • kubectl apply -f k8s/cron.yaml

[pmac]

My only hesitation is that, if I'm reading this right, the fastest schedule that can be run on gitlab.com is once per hour, due to this setting. We currently run the update every 5 or 15 min I believe. This will mostly be fine, but it means we may have to manually kick off an update or two on release days. Moving nucleus to directly commit to git will also fix this, so I hope to accelerate that work, but for now this could be an issue.

[pmac]

See my comment. I think we need to do something to ensure it's pushing to the right git repo.

[pmac]

to which repo will this push? I think with this setup that would be Gitlab? We'll probably need to do something like git push git@github.com/mozilla/release-notes.git

[pmac]

I don't think we want this to run on commits to master since this job commits to master.

[jgmize]

good catch! removing now.

[pmac]

We could potentially quickly add triggering the Gitlab pipeline via a nucleus post-save signal, or even cron running somewhere, and use only: triggers in the config:

https://docs.gitlab.com/ee/ci/yaml/README.html#onlyexcept-basic

[jgmize]

Thanks for the excellent feedback and suggestions, @pmac! I've applied your suggested changes and k8s/cron.yaml from 7f053a4 in iowa-a and it is triggering the pipelines in the gitlab branch. Once this is merged I'll apply the change in b02b5db so that it triggers the pipelines in the master branch.