Issues
1-2 of 2
1 of 2
Support triggering builds of jobs via naming convention
Fixed
Description
Environment
None
Pinned fields
Click on the next to a field label to start pinning.
Details
Details
Assignee
Mark Rekveld
Mark RekveldReporter
Mark Rekveld
Mark RekveldComponents
Fix versions
Affects versions
Priority
Zoom
Open Zoom
Created October 27, 2023 at 6:29 PM
Updated November 3, 2023 at 9:17 AM
Resolved November 3, 2023 at 9:17 AM
Activity
Show:
Mark Rekveld
changed the StatusNovember 3, 2023 at 9:17 AMIn Progress
Done
Mark Rekveld
updated the Fix versionsNovember 3, 2023 at 9:17 AMNone
lite-next
Mark Rekveld
updated the ResolutionNovember 3, 2023 at 9:17 AMNone
Fixed
Mark Rekveld
updated the Fix versionsNovember 3, 2023 at 9:17 AMNone
server-next
Mark Rekveld
updated the Fix versionsNovember 3, 2023 at 9:17 AMNone
connect-next
Mark Rekveld
updated the LinkOctober 27, 2023 at 6:30 PMNone
This issue blocks MS-519
Mark Rekveld
changed the AssigneeOctober 27, 2023 at 6:29 PMUnassigned
Mark Rekveld
Mark Rekveld
changed the StatusOctober 27, 2023 at 6:29 PMTo Do
In Progress
Mark Rekveld
updated the RankOctober 27, 2023 at 6:29 PMNone
Ranked higher
Mark Rekveld
changed the StatusOctober 27, 2023 at 6:29 PMBacklog
To Do
Mark Rekveld
created the IssueOctober 27, 2023 at 6:29 PM
Currently triggering a build is either for specific of linked jobs. For linked jobs this requires that there is at least one build that was linked to an issue before the linked jobs can be triggered.
It would be of real benefit if it was possible to trigger a build of jobs that use the issue key in its name or display name as this is a common multi branch convention used.