Bug 1308348
Summary: | successful builds disappearing | ||
---|---|---|---|
Product: | [Community] Copr | Reporter: | Dave Love <dave.love> |
Component: | frontend | Assignee: | Jakub Kadlčík <jkadlcik> |
Status: | CLOSED DUPLICATE | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | unspecified | CC: | clime, van.de.bugger |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-03-01 09:30:40 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Dave Love
2016-02-14 14:23:20 UTC
I confirm the bug. However, "successful builds disappearing" does not describe the problem precisely. I would say "Build links on packages tab are broken". Look at page <https://copr.fedorainfracloud.org/coprs/loveshack/livhpc/package/extrae/>, move mouse pointer to successful build 158727, and note link destination address: <https://copr.fedorainfracloud.org/coprs//livhpc/build/158727/>. Note two subsequent slashes: ...coprs//livhpc... User name, namely, "loveshack" should be there, but it is missed. Now click on "builds" tab, and fin the same build 158727, and look at the link destination address: <https://copr.fedorainfracloud.org/coprs/loveshack/livhpc/build/158727/>. This is correct address, the link is good one, build is in place. I have exactly the same problem, see for example <https://copr.fedorainfracloud.org/coprs/vandebugger/release/package/tapper/> and <https://copr.fedorainfracloud.org/coprs/vandebugger/release/package/locale-en_RU/>. All the build links on "Packages" tab are broken. BTW, this is definitely a regression, because I actively used build links on "Packages" tab. Unfortunately, I cannot name exact day when correct behavior is broken. Oh yes. Thanks for being more alert than me! I _think_ it started happening in the last two or three weeks. Fixed by Thank you guys for the feedback. Code is fixed and deployed to the production, so it works now. Fixed by commits: 07a8d63 145aee3 Although this bug was filed first, there is already closed bug related to this one. If you dont mind I will close it as duplicate. *** This bug has been marked as a duplicate of bug 1310693 *** |