Write script to move all bugs from closed release to next release

[Alexander Charykov]

We need a script which will reassign all bugs which is tied to current release to next release. This action should be done manually after release. Custom-scripts service is a good place to run it.

[Andrey Nikitin (heos)]

On which projects that script should be run?

[Igor Shishkin (teran)]

From duplicate:

Hello,

We need a script to retarget all bugs from already-released-milestone to new one.
This process is a part of our Infra release checklists so we gonna use it upon each one.

Within the process old(Previous) milestone should be removed, new one added instead.
Other fields left unchanged.

Old release and new one should be defined by operator to run it via custom-scripts [0].

[0] https://mirantis.jira.com/wiki/pages/viewpage.action?pageId=198574485

[Igor Shishkin (teran)]

@andrey, mos & fuel

[Dmitry Borodaenko (angdraug)]

I think the right way to implement this is to extend lp-assigner.py so that it checks milestone status, release series, and development focus in launchpad, and adds missing milestones.

For example, now that 7.0 milestone is released, a non-closed bug targeted to 7.0 and not targeted to any MU milestone in any release series would be additionally targeted to 8.0 milestone in 8.0.x series (with status, priority, and assignee copied from 7.0.x), and then marked as Won't Fix for 7.0.x.

If a bug is targeted to 7.0 and is targeted to an MU milestone in any release series, it would be additionally targeted to 8.0 milestone in 8.0.x series (with status, priority, and assignee copied from 7.0.x), and then (reusing the current lp-assigner.py logic) is targeted to the 7.0-updates milestone in 7.0.x release series (Vitaly Sedelnik: please confirm if you prefer it to be 7.0-mu-1 instead).

[Vitaly Sedelnik (vsedelnik)]

Please don't assign bugs to any X.Y-mu-N milestone - these milestones represent the scope of a specific maintenance update and changing the scope in automatic manner is highly not desired. Please use X.Y-updates milestones for automatic nomination.

[Andrey Nikitin (heos)]

I think, we should use separated script, because:
- those scripts have different goals;
- each script runs in different time (lp-assigner runs every hour on time of HCF, but new scrips should be run once).

Moreover, I think we should allocate less resources to support two different small scripts than one big.

[Aliaksandr Buhayeu (abuhayeu)]

Hi guys!

I have started to working on this bug, and want to clarify the actual script requirements. Here are a few questions:

- Is workflow proposed from @dborodaenko shows how it supposed to work? (despite the fact that it would be separate script as @heos mentioned)? Or maybe the @teran version should be implemented (just migrate all bugs from one milestone to another)?

- Should it try to retrieve current target milestone automatically (as dev_focus) and the old milestone from which we migrate the bugs would be the one with the date closest to it, but in the past, or config / run options would be enough?

- And the last one. In case we need migration for example from 7.0 to 8.0, does that "from" includes all other "7.0-mu', '7.0-updates', .. milestones as well, or it should be strict to the one specified?

Appreciate comments!

[Alexander Charykov (acharykov)]

@abuhayeu it should behave as @dborodaenko wrote.

"7.0-mu', '7.0-updates' are maintenance milestones, so it should be kept in same state and added to current milestone. (it is wrote in @dborodaenko comment more clearly)

Configuration should be made via ENV variables because this scripts should be run manually as a jenkins job.

[Fuel Devops McRobotson (fuel-devops-robot)]

Fix proposed to branch: master
Change author: Aliaksandr Buhayeu <email address hidden>
Review: https://review.fuel-infra.org/13959

[Fuel Devops McRobotson (fuel-devops-robot)]

Fix proposed to branch: master
Change author: Aliaksandr Buhayeu <email address hidden>
Review: https://review.fuel-infra.org/14137

[Fuel Devops McRobotson (fuel-devops-robot)]

Reviewed: https://review.fuel-infra.org/13959
Submitter: Alexander Charykov <email address hidden>
Branch: master

Commit: 6f72f33672310c66a72bc9d1d4431fbb55585062
Author: Aliaksandr Buhayeu <email address hidden>
Date: Tue Dec 1 09:06:36 2015

Basic script for bugs migration between releases

This patchset refactors the script to use shared
class for such types of custom scripts.

Shared script itself is under another review.

Change-Id: I7a631918e468d167fd046335984fc0f6c54094d5
Closes-Bug: #1483968

[Fuel Devops McRobotson (fuel-devops-robot)]

Reviewed: https://review.fuel-infra.org/14137
Submitter: Aleksandra Fedorova <email address hidden>
Branch: master

Commit: 459ba79ce9cc5c7b3c59084c85200911b750a496
Author: Aliaksandr Buhayeu <email address hidden>
Date: Mon Nov 30 18:19:44 2015

Added new part to configure a job to run lp_release_migrator script

That script should migrate Launchpad bugs from one milestone to
another from 'mos' and 'fuel' projects according to the rules
described in a Launchpad bug: https://bugs.launchpad.net/fuel/+bug/1483968

This patchset just updates the ENV variable name.

Change-Id: Iaac01c7ac0c69a02c9323c6184a918ba01c22385
Closes-Bug: #1483968