1. Forum
  2. Usenet
  3. LINUX.DEBIAN.MAINT.HAMS

  • How to configure CI on salsa?

    From Daniele Forsi@21:1/5 to All on Sun Nov 28 10:20:02 2021
    Hello,

    I'm trying to configure a CI pipeline for ampr-ripd because building
    that package is failing locally on my system and before pushing a fix
    I would like to set a pipeline to confirm the failure and then to
    confirm that my commit [4] fixes it before merging.

    In the "CI/CD Settings" page [1] I have set "CI/CD configuration file"
    to "recipes/debian.yml@salsa-ci-team/pipeline" as in [2] but the
    Pipelines page [3] still shows the "Get started" button instead of a
    "Run pipeline" button.
    Is this supposed to work with my access level or I'm doing something wrong? Should I instead add a debian/gitlab-ci.yml config like in other repositories?

    [1] https://salsa.debian.org/debian-hamradio-team/ampr-ripd/-/settings/ci_cd [2] https://salsa.debian.org/salsa-ci-team/pipeline/-/blob/master/README.md
    [3] https://salsa.debian.org/debian-hamradio-team/ampr-ripd/-/pipelines
    [4] https://salsa.debian.org/debian-hamradio-team/ampr-ripd/-/commit/72041c6617fc3e9f72aac105953c7d04d44eb9b3

    thanks,
    --
    73 de IU5HKX Daniele

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Christoph Berg@21:1/5 to All on Tue Nov 30 09:10:01 2021
    Re: Daniele Forsi
    In the "CI/CD Settings" page [1] I have set "CI/CD configuration file"
    to "recipes/debian.yml@salsa-ci-team/pipeline" as in [2] but the
    Pipelines page [3] still shows the "Get started" button instead of a
    "Run pipeline" button.
    Is this supposed to work with my access level or I'm doing something wrong? Should I instead add a debian/gitlab-ci.yml config like in other repositories?

    Oh, that's very interesting that gitlab no longer requires an in-repo
    CI config. TIL.

    You set up everything correctly, but the un-intuitive part is that you
    need to actually push something *after* having set up CI. The easiest
    way to do that is to push a branch that doesn't change anything, which
    I just did. (The job failed because I removed that branch too early.)
    Now the button is there.

    Cheers,
    Christoph

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)