Closed Bug 1337652 Opened 5 years ago Closed 5 years ago
Implement Jenkins Pipeline using Tox + Jenkinsfile, *only* for /e2e-tests/ dir?
First, apologies if this is an (unwanted) surprise and/or perceived to be foisted on the team at large; that's not our intention. tl;dr - if fine with the team at large, this bug will be to track implementing Tox and Jenkinsfile (aka Pipeline, formerly known as "Workflow") *only* for the /e2e-tests/ portion of the shared repo. === As part of formerly-known-as-Web-QA moving its test-automation jobs to our "new" team's -- Firefox Test Engineering -- shared Jenkins infra, we're consolidating and standardizing CI/build-configuration management, where possible, using the Jenkins project's recommended "configuration as shippable code."  http://tox.readthedocs.io - example: https://github.com/mozilla/mozillians-tests/blob/26a141efc63ecd3c627f3da616311d1593dbec84/tox.ini  https://jenkins.io/doc/book/pipeline/jenkinsfile/ - example: https://github.com/mozilla/mozillians-tests/blob/26a141efc63ecd3c627f3da616311d1593dbec84/Jenkinsfile  https://jenkins.io/doc/book/pipeline/  http://firefox-test-engineering.readthedocs.io/en/latest/reference/Testing/continuous_integration.html
This sounds totally fine to me. r+
Taking; WIP patch up soon.
Assignee: nobody → stephen.donner
https://github.com/mozilla/socorro/pull/3668 is up for cheers, jeers, and everything in-between!
Forgot to close this out; it landed in https://github.com/mozilla/socorro/commit/5d914b6f1655743dbf5dc334eb2008038d18de6e !
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.