-
Notifications
You must be signed in to change notification settings - Fork 36
Open
Labels
feature requestNew feature or requestNew feature or request
Description
Is your feature request related to a problem? Please describe.
The following command "collects the list of tracked project issues (for example, issues stored in JIRA or other bug tracking systems) and add them to the build-info"
jf rt bag [command options] <build name> <build number> [Path To .git]
``
When used in Jenkins, this allows associating JIRA Ids with published artifacts
There are scenarios where we want to attach JIRA ids to he published artifacts but these JIRA IDs were not compulsorily mentioned in the git commits. These scenarios are:
* The developer forgot to add a JIRA id in the commit. In this instance it is be easier to re-kick off the Jenkins build with a provided JIRA ID than go through the whole git branch / merge / build workflow
* Some JIRA ids from dependencies (libraries) are not directly in the repo being built but we still want to mention them in the final artifact.
**Describe the solution you'd like to see**
I would like the ability to provide a custom list of JIRA IDs to add to the build info in addition to the ones collected from the current git repo. For instance
```sh
jf rt bag -extra-jiras=PROJ-1234,PROJ-9876 <build name> <build number>
``
**Describe alternatives you've considered**
We have not found an alternative as at present it is not even possible to edit the list of JIRA ids in a published build once it's published.
**Additional context**
Note that an alternative solution would be to add the ability to edit the list of JIRA IDs on a published artifactory build from the UI interface (or via the cli)Metadata
Metadata
Assignees
Labels
feature requestNew feature or requestNew feature or request