External trigger: Integration test before release? about integration-test HOT 6 OPEN

@pganssle anyone (with the right usage rights) can kick of manually a one-off run. I imagine we just permission library maintainers to be able to kick off builds manually. Before they want to cut a release.

from integration-test.

@zooba has the rights, so just send him your Azure account e-mail addresses and he can add you to the organization.

from integration-test.

at https://dev.azure.com/pypa/integration-test/_build?definitionId=15 once you're permissioned:

from integration-test.

@gaborbernat should also have the ability to add people. Otherwise I'll take a look when I get into the office today (which, since Seattle has almost an entire inch of snow today, is not guaranteed 😁 )

from integration-test.

If you need to add people, the org was created from my account and I can add people. I mentioned in the discuss thread that pipenv has pretty substantial integration tests in place that I can help bring over here but it isn't clear whether anyone is interested in that, so for now I guess you can let me know if you need anything modified about the org

from integration-test.

We definitely need maintainers to spend some time setting up tests. I know we said we don't want to tie it to tox but I would prefer to have the test easily reproducible locally. As such I would prefer to have it as such. I've tested waters with https://github.com/tox-dev/integration-test, and I would imagine having something similar. Are we in agreement?

PS. The way I wrote that checks out projects via SCM locally and even allows to create fixes in-line, and then one can run it locally to see the test pass. Furthermore, devpi setup and wheel provision are pytest fixtures allowing to be very modular.

from integration-test.