|
7 | 7 |
|
8 | 8 | (defchangelog (:ignore-words ("40ANTS-DOC" |
9 | 9 | "ASDF" |
| 10 | + "CI" |
| 11 | + "secrets.DEPLOY_TRIGGER_TOKEN" |
10 | 12 | "DEPLOY_TRIGGER_TOKEN" |
| 13 | + "secrets.GITHUB_TOKEN" |
11 | 14 | "GITHUB_TOKEN" |
12 | 15 | "OSX") |
13 | 16 | :external-docs ("https://40ants.com/40ants-asdf-system/")) |
| 17 | + (0.17.0 2025-02-06 |
| 18 | + " |
| 19 | +Added |
| 20 | +===== |
| 21 | +
|
| 22 | +Functions for creation jobs now accept two new arguments: |
| 23 | +
|
| 24 | +- STEPS-BEFORE argument allows to specify a list of steps to be performed before the job. For example, this can be used to install some system packages required for loading ASDF systems during the job execution. |
| 25 | +- STEPS-AFTER argument is the same as previous one, but executes steps after the job. |
| 26 | +") |
| 27 | + (0.16.0 2024-12-14 |
| 28 | + " |
| 29 | +Added |
| 30 | +===== |
| 31 | +
|
| 32 | +Now dynamic space size can be given for lisp steps. |
| 33 | +
|
| 34 | +There are two ways to set it: |
| 35 | +
|
| 36 | +``` |
| 37 | +(build-docs |
| 38 | + :asdf-system \"cl-telegram-bot-docs\" |
| 39 | + :env ((\"DYNAMIC_SPACE_SIZE\" . \"4Gb\"))) |
| 40 | +``` |
| 41 | +
|
| 42 | +This way it will be applied only to the step of the documentation building, |
| 43 | +because [docs-builder script](https://github.com/40ants/docs-builder) allows to use |
| 44 | +such environment variable. |
| 45 | +
|
| 46 | +But if you CI process fails to compile the ASDF system because of the memory limit, |
| 47 | +then you need to set dynamic space size on the earlier state - during \"Setup Lisp\" |
| 48 | +step. For this case an argument DYNAMIC-SPACE-SIZE can be given: |
| 49 | +
|
| 50 | +``` |
| 51 | +(build-docs |
| 52 | + :asdf-system \"cl-telegram-bot-docs\" |
| 53 | + :dynamic-space-size \"4gb\") |
| 54 | +``` |
| 55 | +
|
| 56 | +") |
14 | 57 | (0.15.0 2024-03-02 |
15 | 58 | " |
16 | 59 | New |
17 | 60 | === |
18 | 61 |
|
19 | | -* Now you can specify ENV argument to 40ANTS-CI:DEFWORKFLOW and any job. This should be an alist where keys are strings and values are evaluated during GitHub workflow generation phase. Read more in 40ANTS-CI-DOCS/INDEX::@ENV section. |
20 | | -* 40ANTS-CI/JOBS/AUTOTAG:AUTOTAG function now ignores TOKEN-PATTERN argument if ENV argument was given and has GITHUB_TOKEN value for whole job. |
| 62 | +* Now you can specify ENV argument to 40ANTS-CI/WORKFLOW:DEFWORKFLOW and any job. This should be an alist where keys are strings and values are evaluated during GitHub workflow generation phase. Read more in 40ANTS-CI-DOCS/INDEX::@ENV section. |
| 63 | +* Also, 40ANTS-CI/JOBS/AUTOTAG:AUTOTAG function now ignores TOKEN-PATTERN argument if ENV argument was given and has `GITHUB_TOKEN` value for whole job. |
21 | 64 |
|
22 | 65 | Backward incompatible changes |
23 | 66 | ============================= |
24 | 67 |
|
25 | 68 | * When additional keyword arguments to 40ANTS-CI/STEPS/SH:SH function are given, they are transformed into env variables. Previously, their names were taken as is. Now they are uppercased and dash symbols are replaced with underscores. |
26 | 69 |
|
27 | | -
|
28 | 70 | ") |
29 | 71 | (0.14.0 2024-02-25 |
30 | 72 | " |
@@ -101,7 +143,7 @@ Class 40ANTS-CI/JOBS/CRITIC:CRITIC was fixed for case when there are multiple cr |
101 | 143 | renames to the IGNORE-CRITIQUES argument.") |
102 | 144 | (0.6.0 2022-02-21 |
103 | 145 | "- New job type \"critic\" was added. It advices how to make you Lisp code better. |
104 | | - Learn more about this job type at 40ANTS-CI::@CRITIC section.") |
| 146 | + Learn more about this job type at 40ANTS-CI-DOCS/INDEX::@CRITIC section.") |
105 | 147 | (0.5.0 2022-01-28 |
106 | 148 | "- Move the actions/checkout action from v1 to v2.") |
107 | 149 | (0.4.0 2022-01-28 |
|
0 commit comments