[med-svn] [Git][med-team/policy][master] 3 commits: replaced ref to gitlab-ci.yml by salsa-ci.yml

[Étienne Mollier]

Étienne Mollier pushed to branch master at Debian Med / policy


Commits:
618e6197 by Étienne Mollier at 2021-02-21T16:51:43+01:00
replaced ref to gitlab-ci.yml by salsa-ci.yml

routine-update builds by default the debian/salsa-ci.yml file to
construct the default test pipeline informations provided by the Salsa
CI team.

- - - - -
90932e8d by Étienne Mollier at 2021-02-21T16:58:41+01:00
adding a note about former naming convention

Before debian/salsa-ci.yml was trendy, thanks to routine-update, the
common name was debian/gitlab-ci.yml, so it might be a good idea to be
aware it exists.

- - - - -
51830b8a by Étienne Mollier at 2021-02-21T17:06:45+01:00
added small salsa-ci.yml examples

- - - - -


1 changed file:

- policy.rst


Changes:

=====================================
policy.rst
=====================================
@@ -866,19 +866,48 @@ format. This is better than using the ``1.0`` format directly because
 the ``3.0 (quilt)`` format brings other advantages, in particular
 the conservation of file permissions in the ``debian`` directory.
 
-.. _debian-gitlab-ci.yml:
+.. _debian-salsa-ci.yml:
 
-``debian/gitlab-ci.yml``
+``debian/salsa-ci.yml``
 ------------------------
 
 To run continuous integration tests at each push in our Salsa forge, the Salsa
 CI team provides a pipeline that can be activated by including
 some template files available from their `repository
 <https://salsa.debian.org/salsa-ci-team/pipeline>`__.  The simplest and
-recommended way is to put the include statements in a ``debian/gitlab-ci.yml``
+recommended way is to put the include statements in a ``debian/salsa-ci.yml``
 file, and configure the repository to recognise that file, as documented
 in the ```salsa-ci-team/pipeline`` repository's `README
 <https://salsa.debian.org/salsa-ci-team/pipeline/blob/master/README.md>`__ file.
+It may happen that CI pipeline configuration is stored in
+``debian/gitlab-ci.yml`` instead, for project which not necessarily used
+``routine-update`` for setting the initial file.
+
+The usual ``debian/salsa-ci.yml`` fresh out of ``routine-update`` will look
+like:
+
+::
+
+   ---
+   include:
+     - https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/salsa-ci.yml
+     - https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/pipeline-jobs.yml
+
+If for some packages, an attempt to build on 32 bits architecture is a waste of
+precious CI runner CPU cycles, then it is possible to disable such test
+entirely:
+
+::
+
+   ---
+   include:
+     - https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/salsa-ci.yml
+     - https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/pipeline-jobs.yml
+   
+   variables:
+     SALSA_CI_DISABLE_BUILD_PACKAGE_I386: "true"
+
+Again, refer to the README provided by the Salsa CI team for more options.
 
 .. _symbols:
 



View it on GitLab: https://salsa.debian.org/med-team/policy/-/compare/8cc5a64443a785edbb1721f562333d7656a87df5...51830b8ab13b819ed9ba40d549ddfbddfdbf52e2

-- 
View it on GitLab: https://salsa.debian.org/med-team/policy/-/compare/8cc5a64443a785edbb1721f562333d7656a87df5...51830b8ab13b819ed9ba40d549ddfbddfdbf52e2
You're receiving this email because of your account on salsa.debian.org.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/debian-med-commit/attachments/20210221/912902c9/attachment-0001.htm>