Improve docker builds for deployment and/or development
|Reported by:||anongoblin||Owned by:|
|Cc:||michael@…, Olivier Mehani||Parent Tickets:|
[This is Michael Lynch (mtlynch.io). Boris suggested I post here under the anon account as new registrations on the issue tracker seem to be down and the mailing list is not accepting new messages]
I'm interested in contributing to MediaGoblin.
Its test suite is very impressive, so I tried to run the tests and ran into some issues with finding the correct dependencies. One good way to solve this would be to have a continuous integration (CI) service that establishes a "known-good" configuration for running tests.
There was discussion a few years ago about setting up CI, but it doesn't look like it ever went through:
I spent a few hours setting up MediaGoblin on Travis and got it to successfully execute the tests, but it skips 12 out of 183:
If I force the tests to run, the skipped tests fail:
A few questions:
- Are all tests currently in a good state? (i.e. should I expect to see all 183 tests pass?)
- If so, what dependencies am I missing? I tried installing every apt package in the HackingHowTo but the tests still fail.
- Is there interest in setting up official CI for MediaGoblin? There are many free options available, but it would require the project to move (or at least officially mirror) to more modern git hosting (Github, BitBucket, Gitlab, etc).
Here are all my changes:
The most relevant files are my Dockerfile to set up the test environment:
and my Travis configuration:
Change History (19)
comment:15 by , 3 years ago
|Summary:||Travis CI for MediaGoblin → Continuous integration (CI) testing for MediaGoblin|
comment:17 by , 2 years ago
|Summary:||Continuous integration (CI) testing for MediaGoblin → Improve docker builds|
comment:18 by , 2 years ago
|Summary:||Improve docker builds → Improve docker builds for deployment|