Project

Profile

Help

Task #8252

closed

Story #8093: [EPIC] Release automation

Automatically tag issues as plugin_temlpate ones if associated commits belong to a plugin_template git repo

Added by ttereshc over 1 year ago. Updated about 1 year ago.

Status:
CLOSED - COMPLETE
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
CI/CD
Sprint:
Quarter:

Description

Some issues are not marked as plugin template ones because we forget to do so.

With Y release, there is always a bunch of issues which is not clear where they belong, installer, or plugin_template, or forgotten from other releases, or just the ones with no changelog (we are much better with it now, to be fair), or something else. I personally haven't experienced a single Y release when all modified issues were properly associated with a category or tag, or belong to this release only.

Releasing plugin template is a first step in the release process. And it's helpful to close those issues in redmine right away to sort out the remaining clutter. It's not always straightforward and if release is big, it's time consuming to figure out which issues are plugin_template ones.

It's not critical but would be really nice if our automation could set plugin template tag automatically.

Actions #1

Updated by ttereshc over 1 year ago

  • Description updated (diff)
Actions #2

Updated by ttereshc over 1 year ago

  • Parent task set to #8093
Actions #3

Updated by daviddavis about 1 year ago

  • Status changed from NEW to CLOSED - COMPLETE

The plugin_template issues are now at https://github.com/pulp/plugin_template/issues and there's no plugin template tag anymore.

Also available in: Atom PDF