[sle][Migration][SLE15SP4] Using gitlab to control yaml file
We need store migration yaml file to gitlab, then we can using gitlab to update yaml file.
Also we need change name from SLES_15_SP2 to sles_15_sp2
#1 Updated by coolgw over 1 year ago
CI jobs can run for master branch. But first I recommend you try it out in a personal fork and enable travis CI for your fork. If you are happy with the changes then you can create a pull request with the according changes in .travis.yml and we can enable the according travis CI cron jobs within the main repo. I recommend you start the documentation from https://docs.travis-ci.com/ . It's really good and probably way better in answering questions than I would be able to. For sensitive data like API key and secrets probably https://docs.travis-ci.com/user/encryption-keys/ should help. Keep in mind that travis CI as a public service can be helpful for anything on openqa.opensuse.org. An alternative are "Github Actions". For SUSE-internal triggers I recommend the gitlab CI using our internal instance gitlab.nue.suse.com . Many teams use that already in conjunction with openQA, e.g. to maintain the job templates. travis.yml is only used for travis CI. For gitlab CI you need a file .gitlab-ci.yml , so similar but different 🙂 https://docs.gitlab.com/ee/ci/yaml/
docs.gitlab.com. A good example is probably https://gitlab.suse.de/qsf-y/qa-sle-functional-y from QSF-y how they load their job templates YAML documents using gitlab CI . https://gitlab.suse.de/qsf-y/qa-sle-functional-y/-/blob/master/.gitlab-ci.yml#L8 shows how they set openQA client parameters based on variables. These variables are defined within the gitlab project.
#3 Updated by coolgw over 1 year ago
- Status changed from New to Blocked
following gitlab CI already setup, but currently not used since yaml file for 15sp3 still unstable now. Once yaml file is stable enough, we will start kick out this