AL-Go version
8.3
Describe the issue
The settings for versioningStrategy describes the following behaviour:
0 = Build is the github run_number for the CI/CD workflow, increased by the runNumberOffset setting value (if specified).
Revision is the github run_attempt subtracted 1.
According to this description, the run_number from the CI/CD workflow would be used, regardless of the workflow being run.
In reality, the run_number of the current workflow is used.
Expected behavior
Either of the following:
- The CI/CD run_number is used (and incremented to prevent duplicate versions) regardless of workflow
- The documentation should be updated to reflect the actual behaviour
Steps to reproduce
E.g. with the Test Next Major workflow:
- Set
versioningStrategy to 0 in Test Next Major.settings.json
- Run the Test Next Major workflow
Additional context (logs, screenshots, etc.)
No response
AL-Go version
8.3
Describe the issue
The settings for
versioningStrategydescribes the following behaviour:According to this description, the run_number from the CI/CD workflow would be used, regardless of the workflow being run.
In reality, the run_number of the current workflow is used.
Expected behavior
Either of the following:
Steps to reproduce
E.g. with the Test Next Major workflow:
versioningStrategyto 0 inTest Next Major.settings.jsonAdditional context (logs, screenshots, etc.)
No response