Skip to content

[Bug]: Versioning strategy 0 does not take the CI/CD workflow run number as documented #2155

@DF1229

Description

@DF1229

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:

  1. The CI/CD run_number is used (and incremented to prevent duplicate versions) regardless of workflow
  2. The documentation should be updated to reflect the actual behaviour

Steps to reproduce

E.g. with the Test Next Major workflow:

  1. Set versioningStrategy to 0 in Test Next Major.settings.json
  2. Run the Test Next Major workflow

Additional context (logs, screenshots, etc.)

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions