Recommend qastaging.launchpad.net over staging.launchpad.net

Bug #1829233 reported by Hemanth V. Alluri
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Low
Unassigned

Bug Description

When trying to create a test project on launchpad.net, a recommendation appeared in one corner of the page suggesting that I use staging.launchpad.net if I was testing. However, staging.launchpad.net does not support git repositories. In question #680828 (https://answers.launchpad.net/launchpad/+question/680828) Colin Watson suggested that I use qastaging.launchpad.net instead if I wanted to use git repositories and https://help.launchpad.net/API/Webhooks also talks about qastaging.launchpad.net but not staging.launchpad.net (for the same reason that git repositories are not suggested by staging.launchpad.net in the first place - so the git webhook target/object wouldn't exist in the first place).

Thus I propose replacing the suggestion to use staging.launchpad.net with a suggestion to use qastaging.launchpad.net instead.

Revision history for this message
Colin Watson (cjwatson) wrote :

We need to work out whether it's better to complicate the UI message (since it's when creating a project, so not intrinsically git-specific) or to add git support to staging. The latter isn't trivial of course (as well as a new backend deployment, it may require arranging to preserve git repositories across staging database restores, which are much more frequent than on qastaging), but it would certainly be convenient for other reasons.

tags: added: confusing-ui git infrastructure lp-code
Changed in launchpad:
status: New → Triaged
importance: Undecided → Low
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.