[gnutls-devel] GnuTLS | .gitlab-ci.yml: mark all CI jobs interruptible (!1628)

Read-only notification of GnuTLS library development activities gnutls-devel at lists.gnutls.org
Tue Aug 9 08:56:15 CEST 2022

Stanislav Židek started a new discussion: https://gitlab.com/gnutls/gnutls/-/merge_requests/1628#note_1055027947

I think the better approach would be to add `interruptible: true` to `default` section to prevent errors in future and limit duplication.

Other problem: `interruptible: true` is missing in `commit-check` job and docs say "You can’t cancel subsequent jobs after a job with interruptible: false starts." I am not sure about the precise definition of "subsequent job" though, if it is only about time of starting, or if it means jobs need to be dependent.

Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/-/merge_requests/1628#note_1055027947
You're receiving this email because of your account on gitlab.com.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.gnupg.org/pipermail/gnutls-devel/attachments/20220809/93eca66e/attachment.html>

More information about the Gnutls-devel mailing list