We need to verify that the BzAPI proxy will continue to work properly when 4.2 is pushed to production on BMO. Also we will want tool developers to point their code at the new BzAPI proxy to make sure their tools continue to work properly. Please let me know if you need my help or the help of IT to get this set up. dkl
No problem - I can do this. Is there a deadline? Gerv
(In reply to Gervase Markham [:gerv] from comment #1) > No problem - I can do this. Is there a deadline? > > Gerv Upgrading to 4.2 was a Q2 goal and has not slipped to Q3 unfortunately :( But we want the BzAPI instance to be available as soon as possible as we need to make sure people have adequate time to test their tools/dashboards against the 4.2 codebase. So if you could get this set up with next week or two, that would give people enough time to test and we can still conceivably get this thing rolled out in Q3. dkl
I believe Dave meant that it *has* slipped to Q3. But we want to lock this down as early in Q3 as possible.
(In reply to Mark Côté ( :mcote ) from comment #3) > I believe Dave meant that it *has* slipped to Q3. But we want to lock this > down as early in Q3 as possible. Sorry typo error. "Upgrading to 4.2 was a Q2 goal and has now slipped to Q3 unfortunately :(" dkl
Er, this isn't going to work simply until you take the HTTP Auth off the site. BzAPI doesn't know how to get past that. I could perhaps try and teach it, but it would be easier if I didn't have to :-) When do you plan to remove that? In case it helps, there is already an installation pointed at bugzilla-stage-tip: https://api-dev.bugzilla.mozilla.org/tip/bug/35 Is there some document somewhere with an upgrade timeline and an explanation of the relationship between all these staging servers? Gerv
(In reply to Gervase Markham [:gerv] from comment #5) > Er, this isn't going to work simply until you take the HTTP Auth off the > site. BzAPI doesn't know how to get past that. I could perhaps try and teach > it, but it would be easier if I didn't have to :-) When do you plan to > remove that? right now the database there is unsanitized to test out private features as well as to make sure the checksetup.pl from 4.0 to 4.2 worked properly. We place to remove the HTTP auth once the database has been completely sanitized and it is ready for public consumption. Should be too much longer. Once that is done your test instance should be able to work as-is. > In case it helps, there is already an installation pointed at > bugzilla-stage-tip: > https://api-dev.bugzilla.mozilla.org/tip/bug/35 bugzilla-stage-tip is where we test experimental features for the current stable code base so that doesn't really apply for this request. > Is there some document somewhere with an upgrade timeline and an explanation > of the relationship between all these staging servers? Working on it. Part of it can be seen here: https://wiki.mozilla.org/BMO/42Upgrade Don't take it all literally as some is a copy over from the 4.0 Upgrade and needs to be edited/removed. https://wiki.mozilla.org/BMO/42Upgrade/Alpha will be the first email sent out once the list of criteria is met on the the top of that page. dkl
OK, the installation is up: https://api-dev.bugzilla.mozilla.org/allizom/bug/35 Is that OK, or do you think I'll need to teach it about HTTP Auth? Gerv
That will work. As I mentioned, we will soon remove the LDAP auth so this should hopefully just start to work when that happens. Thanks for setting this up. I will close this bug when the restriction is removed and we can verify it is working. dkl
Status: NEW → ASSIGNED
This is now working. :-) Gerv
Status: ASSIGNED → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.