1. Forum
  2. Usenet
  3. LINUX.DEBIAN.DEVEL.MENTOR

  • How to turn off Salsa CI for a package?

    From Rebecca N. Palmer@21:1/5 to All on Fri Jan 28 00:10:01 2022
    The default (I'm not sure if this is a global or per-team default) Salsa
    CI pipeline tries to build and test packages on every commit.

    For pandas, this always hits the 1 hour timeout, and hence "fails"
    uselessly (wasting both the server's resources, and my attention when a
    failure alert appears).

    https://salsa.debian.org/science-team/pandas/-/pipelines

    I've tried these attempts at "do nothing" in debian/salsa-ci.yml.
    Neither of them does that: the default CI still runs.

    https://salsa.debian.org/science-team/pandas/-/commits/debian

    workflow:
    rules:
    - when: never

    --- or (based on forensics-samples) ---

    ---
    default:
    script:
    - echo "disabled as it times out"

    We could instead increase the timeout, but I don't know if that much
    resource use would be appropriate.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Eriberto@21:1/5 to All on Fri Jan 28 00:30:02 2022
    Hi Rebecca,

    Em qui., 27 de jan. de 2022 às 20:00, Rebecca N. Palmer <[email protected]> escreveu:

    The default (I'm not sure if this is a global or per-team default) Salsa
    CI pipeline tries to build and test packages on every commit.

    For pandas, this always hits the 1 hour timeout, and hence "fails"
    uselessly (wasting both the server's resources, and my attention when a failure alert appears).

    https://salsa.debian.org/science-team/pandas/-/pipelines

    I've tried these attempts at "do nothing" in debian/salsa-ci.yml.
    Neither of them does that: the default CI still runs.

    https://salsa.debian.org/science-team/pandas/-/commits/debian

    workflow:
    rules:
    - when: never

    --- or (based on forensics-samples) ---

    ---
    default:
    script:
    - echo "disabled as it times out"

    We could instead increase the timeout, but I don't know if that much
    resource use would be appropriate.



    There are some ways to disable it, like removing the debian/salsa.yml
    file, renaming it or setting the Salsa to search for another
    filename[1].

    [1] https://salsa.debian.org/debian/dh-make/-/blob/master/lib/debian/salsa-ci.yml.ex

    Regards,

    Eriberto

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Andreas Tille@21:1/5 to All on Sat Jan 29 09:00:02 2022
    Am Thu, Jan 27, 2022 at 10:29:26PM +0000 schrieb Rebecca N. Palmer:
    I've tried these attempts at "do nothing" in debian/salsa-ci.yml. Neither of them does that: the default CI still runs.

    https://salsa.debian.org/science-team/pandas/-/commits/debian
    See

    https://www.wgdd.org/2019/11/salsa-skip-ci/

    Hope this helps

    Andreas.

    --
    http://fam-tille.de

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Rebecca N. Palmer@21:1/5 to All on Sat Jan 29 12:30:02 2022
    The issue turned out to be that the pandas repository's settings were
    pointed to a CI settings file outside the repository, so it wasn't even
    looking at my debian/salsa-ci.yml.

    As suggested by Eriberto's link, this setting is found at (starting from
    the repository's page in Salsa, logged in) Settings (in left menubar) >
    CI/CD > General pipelines > Expand > CI/CD configuration file.

    After pointing that setting back at debian/salsa-ci.yml, it does take
    the absence of such a file as "do nothing".

    The timeout length setting is on the same page.

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