On 04/27/2018 04:06 PM, Randy Barlow wrote:
On 04/27/2018 02:04 PM, Randy Barlow wrote:
> I just deployed a Bodhi 3.7.0 beta build to stg.
bodhi-3.7.0 has now been deployed to production.
* Include the missing tests in the summary about greenwave’s
This still doesn't work in staging because staging Greenwave doesn't
show the same response as production Greenwave - however, I think
this will work in production as long as the newer Greenwave from staging
is not deployed to production. I'm hoping I can figure this out with the
Greenwave developers before they need to deploy - it may require a patch
in Greenwave or a patch in Bodhi or both. In the meantime, I expect that
this is working now.
* Show waivers about an update on its page for easier access to
and admins (#2277).
You had linked to an update that
had a waiver in the PR, but I don't see any mention of the waiver on its
Is it broken?
It turns out that this was broken, so Patrick fixed it yesterday.
* Properly call the WaiverDB API when waiving tests from the UI
Staging Bodhi doesn't have a WaiverDB token, so I've been unable to test
Staging now has a token, and I was able to use it to test the WaiverDB
integration myself for the first time. There were a number of
significant usability issues[3-6] that are sure to get lots of
complaints if we enable it in production. I personally think the UI is
probably still better than the CLI even with these issues, but threebean
suggested that we should improve the UX before enabling it. I had been a
bit on the fence due to not wanting a flood of support questions in
#fedora-admin, so I'm going with threebean's recommendation for now to
continue to leave the WaiverDB UI turned off in Bodhi until it works