Joachim Zobel <[email protected]> wrote: > https://salsa.debian.org/science-team/gap-hap > > no pipeline is running on commit to debian/master and no "Run pipeline" > button is visible? > > I have double checked the settings, CI is enabled and the path is > configured. Is this a lack of permissions? >
If I visit <https://salsa.debian.org/science-team/gap-hap> at commit 04d4ca84, instead of a file `d/salsa-ci.yml` (no leading period) I see a `d/.gitlab-ci.yml` instead (with leading period). With `ruby-mdl` (now team maintained), I'm used to the former pattern, which is why my setup was / is slightly different to yours. Back when ruby-mdl` was in my namespace, the setup was in two steps. step 1) settings -> general -> badges, where I added - Name: to `Pipeline status` - Link: pattern of `https://salsa.debian.org/<owner>/<project>/`, here `https://salsa.debian.org/nbehrnd/ruby-mdl/` as a specific example. Here, it likely would be `https://salsa.debian.org/science-team/gap-hap` - the badge url was in pattern of `https://salsa.debian.org/<owner>/<project>/badges /debian/latest/pipeline.svg` It was necessary to fill each of the three fields. But then, it was possible to see a gray badge in the preview of the setup (i., not public) and grey -- because there was no workflow to reference too. step 2) settings -> ci/cd, general pipelines to define the location of the workflow in question. For me it was `debian/salsa-ci.yml` (vide supra) and by complete address -- not just `d/salsa-ci.yml`. So in your case `debian/.gitlab-ci.yml`. Does the CI really need to be stored in a hidden file? An empty commit, e.g. ``` bash git commit --allow-empty -m "trigger workflow" -sS git push ``` is enough to launch the remote CI anew. Because I was able to use the Ruby specific recipe ``` salsa-ci.yml --- include: - https://salsa.debian.org/ruby-team/meta/raw/master/salsa-ci.yml ``` before joining the Ruby team, I infer the recipe ``` .gitlab-ci.yml --- include: - https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/recipes/debian.yml ``` in yours should equally be free to be used by anyone interested to package for Debian. For training purposes, I once or twice cloned "the real" repository, dropped the remote address for good (`git remote remove origin`) to then add the address of a private repository on salsa, too. Best regards, Norwid
