Details
-
Type:
Improvement
-
Status: Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 3.21.1
-
Fix Version/s: None
-
Component/s: REST, Scheduled Tasks
-
Labels:None
-
Environment:n/a
Description
Scenario:
We have tasks in Nexus that we trigger from our CI environment. It would then be good if we could define the task id ourself so that we can have the same id in a testing environment and the prod environment.
For example, when deploying rpm packages to a yum repo we need to trigger a rebuild yum repo metadata task. In the REST API call we need to specify the task ID. Today the ID is auto-generated which causes us to have a config variable with this task id in each environment, which needs to be manually configured. It would be great if we could decide ourself that it should have the id "rebuild-staging-yum-repo-metadata" and then have it hard-coded in our scripts.