Page MenuHomePhabricator

Set up test instance for the community to test new version
Closed, ResolvedPublic


This will help making the switch more painless for the community if they can test out beforehand and report blockers.

Event Timeline seems to exist.
If issues are found on that website, should bug reports be created? Clarification welcome.

If issues are found on that website, should bug reports be created? Clarification welcome.

Yes please! :-)

T254158 would probably be best as it has better visibility, but here underneath this task is fine too.

Let the reports come in. Not sure which things we can fix on our end or which things need upstream help. But we'll sort it out.

The production machine is now on 3.2.

Now that the new Gerrit is live. What do we do with the test instance.
Leave it up for a bit? Or tear it down immediately to free up resources?

(I don't want to close this task as is so we don't forget about it)

How about i take it from you for now and we figure it out. We need a ticket to properly decom it or change its name either way.

It would be the reversal of T239151 (which i just reopened, so we can also use that)

@Paladox and myself have setup which now works and is using the same puppet role that is used in production.

It required some work (for example to make TLS certs work, skipping the LDAP server part, fixing a bunch of keys in cloud Hiera data etc) and we are glad these are solved now and i think for the first time we have a Gerrit in cloud VPS that actually uses the same puppet role as prod.

Users who want to test things, for example Gerrit design changes, can request being added to the devtools cloud VPS project. (also see

We have currently an instance gerrit-prod-1001.devtools.eqiad.wmflabs which has the purpose to always be like prod. It could be accompanied by another "stage" instance where new config can be applied before it is in prod.

The test instance also has a floating IP. (T254596) and a TLS cert via certbot.

The same devtools project also hosts Phabricator instances for testing.

The test instance in production would not be easy to use for volunteer anyways because they would have to go through an entire access request with a sponsor.

This way though it just needs a request to be added to the project.

Also the project does not contain any private data / real user data and skips the LDAP auth part. Gerrit is in the "dev" mode where you can become any user.

I would claim this resolves the ticket and is not a conflict with taking down, it should be better than that.