-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
travis-ci build and test workflow #16
Comments
Anyone willing to create a .travis.yml file ? |
optionally the .gitlab-ci.yml may be easier and more flexible (using gitlab.com as CI) as it allows to use any docker image, so all dependencies can be included in docker, and CI can just perform the build. |
I'm not familiar with gitlab.com as the CI, can it be wired into github ? ISTR that github does support docker images Dave Cramer On 9 March 2016 at 08:57, Jan Gorecki [email protected] wrote:
|
Can be wired by git push to gitlab.com. |
OK, but we can't wire gitlab into github... to build on every PR? Dave Cramer On 9 March 2016 at 09:02, Jan Gorecki [email protected] wrote:
|
I'm sure we can, using multi-remote on push, or using webhooks, or using push from travis. |
So why do we need docker ? We should be able to build pl/r on travis-ci Dave Cramer On 9 March 2016 at 09:15, Jan Gorecki [email protected] wrote:
|
To re-use the dependency included in the image and it's maintenance. You can do own images for anything but often it is desired to have maintenance of dependency. |
Would be nice to have travis-ci build and test workflow, or at least the build part.
User would have a live deploy documentation.
The text was updated successfully, but these errors were encountered: