[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[taler-docs] 01/02: DD44: update path references
From: |
gnunet |
Subject: |
[taler-docs] 01/02: DD44: update path references |
Date: |
Mon, 18 Dec 2023 01:42:05 +0100 |
This is an automated email from the git hooks/post-receive script.
devan-carpenter pushed a commit to branch master
in repository docs.
commit 57a78d71ab7a4bd774bdf7f8509710dc498b4c98
Author: Devan Carpenter <devan@taler.net>
AuthorDate: Sun Dec 17 19:39:17 2023 -0500
DD44: update path references
CI dirs are under "contrib/" now
---
design-documents/044-ci-system.rst | 34 ++++++++++++++++++----------------
1 file changed, 18 insertions(+), 16 deletions(-)
diff --git a/design-documents/044-ci-system.rst
b/design-documents/044-ci-system.rst
index e777f345..78d64830 100644
--- a/design-documents/044-ci-system.rst
+++ b/design-documents/044-ci-system.rst
@@ -43,23 +43,24 @@ Example directory structure:
::
- ci
- ├── ci.sh
- ├── Containerfile
- └── jobs
- ├── 0-codespell
- │ ├── config.ini
- │ ├── dictionary.txt
- │ └── job.sh
- ├── 1-build
- │ ├── build.sh
- │ └── job.sh
- └── 2-docs
- ├── docs.sh
- └── job.sh
+ contrib
+ └── ci
+ ├── ci.sh
+ ├── Containerfile
+ └── jobs
+ ├── 0-codespell
+ │ ├── config.ini
+ │ ├── dictionary.txt
+ │ └── job.sh
+ ├── 1-build
+ │ ├── build.sh
+ │ └── job.sh
+ └── 2-docs
+ ├── docs.sh
+ └── job.sh
Job directories **MUST** follow this pattern:
-``<repo_root>/ci/jobs/<n-job_name>/``
+``<repo_root>/contrib/ci/jobs/<n-job_name>/``
``n`` is an integer used for ordering the build steps.
@@ -78,10 +79,11 @@ Available config options:
WARN_ON_FAILURE = True|False
CONTAINER_BUILD = True|False
CONTAINER_NAME = <string>
+ CONTAINER_ARCH = <string>
Unless *all* jobs specify a "CONTAINER_NAME" in their custom config a
-container file **MUST** be present at ``<repo_root>/ci/Containerfile``.
+container file **MUST** be present at ``<repo_root>/contrib/ci/Containerfile``.
The container file will be built and used to run all of a repo's jobs
by default.
--
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.