Skip to content

Disabling jobs only in CI. #62

@Zimmi48

Description

@Zimmi48

In rocq-community/paramcoq#75, I had to put coqPackages.mathcomp.job = false; because I had also put coqPackages.mathcomp.override.version = "master"; but there was no reason to have a CI job building the full mathcomp.

In jwiegley/category-theory#21, since no Cachix was set, I wanted to avoid the inefficiency of having dependencies built in separate jobs (only to be rebuilt in the main job). Therefore, I had to put a number of job = false; (more for the "dev" bundles than for the others). In the case of Coq, the unwanted consequence is that Coq is silently skipped when we try to build it, and it is only actually built later on, while trying to build ssreflect: https://github.com/Zimmi48/category-theory/runs/3493747463?check_suite_focus=true#step:10:9

There should be a way of excluding a job from CI without making nix-build --job a no-op.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions