Currently it is possible to specify a build number when getting artifacts from project dependencies, but not for job dependencies.
The use case is the following. A project is setup with a nightly build, and occasionally one of them is tested to be potentially released. For this, a person needs to :
Verify that the build works correctly, which could take a few days.
Manually trigger a "release" job on the same project, that retrieves the artifact from the build that was tested and prep it for release.
The problem is that it is not possible to retrieve artifacts from a specific job within the same project, and several nightly builds might have been ran by the time a build is deemed ready for release.
(The current workaround is to manually construct the url of the artifact from the project and build number, since the artifact consists of a single zip file)
Robin Shen commented 2 years ago
You may select the tested good nightly build, and promote it to release. Or in OneDev 7, open pipeline of the tested nightly build, and trigger release job from there. Some explanation on pipeline on Reddit:
Currently it is possible to specify a build number when getting artifacts from project dependencies, but not for job dependencies. The use case is the following. A project is setup with a nightly build, and occasionally one of them is tested to be potentially released. For this, a person needs to :
The problem is that it is not possible to retrieve artifacts from a specific job within the same project, and several nightly builds might have been ran by the time a build is deemed ready for release. (The current workaround is to manually construct the url of the artifact from the project and build number, since the artifact consists of a single zip file)