sequential build number for each workflow execution

[reddymh]

Summary

Do we plan to introduce sequential build number for each workflow execution or environment variable like BUILD_NUMBER or WORKFLOW_NUMBER for each workflow build.

Use Cases

It will be good if we have build number and will be helpful for tagging the build or using the build number for the CI/CD.

---

Message from the maintainers:

Love this enhancement proposal? Give it a 👍. We prioritise the proposals with the most 👍.

[sarabala1979]

@reddymh Can you provide us more details for this requirement?

[reddymh]

@sarabala1979 for CI/CD , it will be good providing sequential build number for each workflow/pipeline executions.

example:
if I am building java application build the it will be good to have build number or workflow number for each build and tag the build or publish the artifact with the build number or some unique sequential number as well.
If you see any CI tool like jenkins , each job will have sequential build number starting with 1 ..so that we can use for tagging the artifacts

[Hunter-Thompson]

Workflows are different from Jenkins pipelines. It is quite hard to keep track of the sequence because each workflow is created independently, not invoked. No way to accurately determine the sequence.

Jenkins invokes a pipeline which is already created, has a history and thus, there is a sequence to it.

Also tagging an artifact with the build sequence makes no sense IMHO. If you are building an application, don't you think using the git commit id, or the git tag name would be more appropriate than the build sequence number?