Bug 1400943 - RFE: test './manage.py rawhide_to_release'
Summary: RFE: test './manage.py rawhide_to_release'
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Internal Copr
Classification: Internal
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: 2016-12-02 11:19 UTC by Pavel Raiskup
Modified: 2020-12-14 10:59 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1400941
Environment:
Last Closed: 2020-12-14 10:59:02 UTC

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1400941 0 unspecified CLOSED [rfe] add fedora-rawhide chroots 2021-02-22 00:41:40 UTC

Internal Links: 1400941

Description Pavel Raiskup 2016-12-02 11:19:41 UTC 
Manage to test './manage.py rawhide_to_release' command, so it is guaranteed we
won't drop it.

+++ This bug was initially created as a clone of Bug #1400941 +++
Comment 1 clime 2017-03-10 13:49:52 UTC 
`./manage.py rawhide_to_release` might get replaced by forking on chroots as forking does keep db up-to-date and has potential to also keep dist-git branches up-to-date with the state of backend repos. This is something we might want.

Even if forking is used, it still might be ./manage.py command but it won't be probably tested on level of ./manage.py even in that case. I don't think testing manage.py commands is strictly required even though quite easily possible with our integration test suite.
Comment 2 Pavel Raiskup 2020-12-14 10:59:02 UTC 
Tested by: https://pagure.io/copr/copr/blob/4e6881371075c37bf1eddc4b09bd7e29162c4d89/f/frontend/coprs_frontend/tests/test_commands/test_rawhide_to_release.py#_18-19
Note You need to log in before you can comment on or make changes to this bug.