Include version in artifact

1. determine the next version number in the first job of the pipeline.
2. store the number in a file and declare it as an artifact
3. retrieve the version number in subsequent phases of the pipeline

Note

• The artifact is available only in subsequent phases of the pipeline, not in the one it’s defined in, or previous
• If you embed version number of the potential release to every build, pay attention to what happens to the artifacts of the pipelines that are not released. If the unreleased artifacts stay local to the pipeline, it should be safe. But if there is the possiblity that they are copied around, there is the possibility of confusion because there will be many builds with the same version number.
• Consider specifying expiry for the artifacts