Bug 1729683 - RFE: allow deleting a running build
Summary: RFE: allow deleting a running build
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Copr
Classification: Community
Component: frontend
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Copr Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-07-13 13:51 UTC by Till Hofmann
Modified: 2023-04-03 14:10 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-04-03 14:10:42 UTC
Embargoed:


Attachments (Terms of Use)

Description Till Hofmann 2019-07-13 13:51:58 UTC
Description of problem:
When deleting a running build, two messages are shown:
1. You can not delete build `971029` which is not finished. 
2. Builds 971029 have been deleted successfully.

Only one of them can be true (I think it's the first one).

How reproducible:
always

Steps to Reproduce:
1. Start a build
2. Delete the build while it's running
3.

Actual results:
The two error messages. Screenshot:
https://thofmann.fedorapeople.org/Screenshot_2019-07-13%20Builds%20for%20thofmann%20ros-testing.png

Expected results:
Ideally, the build would be canceled and then successfully deleted.

Comment 1 Pavel Raiskup 2019-07-26 06:56:15 UTC
Thanks for the report.

> Expected results:
> Ideally, the build would be canceled and then successfully deleted.

I agree, this is not going to be be easy change, but eventually we should
do what you propose.

Comment 2 Pavel Raiskup 2020-12-14 14:32:57 UTC
See also bug 1639788 (delete project with running builds).

Comment 3 Zbigniew Jędrzejewski-Szmek 2022-02-15 09:10:02 UTC
Also pending builds should be able to be deleted.

Comment 4 Pavel Raiskup 2023-04-03 14:10:42 UTC
The bugs related to Copr build system are now migrated to the
default Copr team tracker:
https://github.com/fedora-copr/copr/issues/2612


Note You need to log in before you can comment on or make changes to this bug.