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

Add initial Travis-CI config #14

Merged
merged 1 commit into from Aug 7, 2018

Conversation

Projects
None yet
2 participants
@paultcochrane
Contributor

paultcochrane commented Aug 7, 2018

Travis-CI is a continuous integration service which is free for open
source projects. This change adds an initial configuration for
this service. Note that xvfb is used to handle the fact that Travis CI
is a headless environment and that one needs to use the -a flag to
xvfb-run in order that the xvfb server is automatically started,
which then allows the dist to build and test reliably on this
infrastructure.

Add initial Travis-CI config
Travis-CI is a continuous integration service which is free for open
source projects.  This change adds an initial configuration for
this service.  Note that xvfb is used to handle the fact that Travis CI
is a headless environment and that one needs to use the `-a` flag to
`xvfb-run` in order that the `xvfb` server is automatically started,
which then allows the dist to build and test reliably on this
infrastructure.

@vadrer vadrer merged commit c5d9461 into vadrer:master Aug 7, 2018

@vadrer

This comment has been minimized.

Show comment
Hide comment
@vadrer

vadrer Aug 7, 2018

Owner

nice
should it be added to MANIFEST?

Owner

vadrer commented Aug 7, 2018

nice
should it be added to MANIFEST?

@paultcochrane

This comment has been minimized.

Show comment
Hide comment
@paultcochrane

paultcochrane Aug 7, 2018

Contributor

No, since it doesn't need to be distributed in the dist. Hrm, which means I should have added it to MANIFEST.SKIP. Whoops, sorry! Will submit a PR for that in the next while.

Contributor

paultcochrane commented Aug 7, 2018

No, since it doesn't need to be distributed in the dist. Hrm, which means I should have added it to MANIFEST.SKIP. Whoops, sorry! Will submit a PR for that in the next while.

@paultcochrane paultcochrane deleted the paultcochrane:pr/add-travis-config branch Aug 7, 2018

@paultcochrane

This comment has been minimized.

Show comment
Hide comment
@paultcochrane

paultcochrane Aug 7, 2018

Contributor

It looks like you maintain your MANIFEST by hand, in which case a MANIFEST.SKIP wouldn't be necessary. Am I right?

Contributor

paultcochrane commented Aug 7, 2018

It looks like you maintain your MANIFEST by hand, in which case a MANIFEST.SKIP wouldn't be necessary. Am I right?

@vadrer

This comment has been minimized.

Show comment
Hide comment
@vadrer

vadrer Aug 7, 2018

Owner

yes, I think so.
thanks :)

Owner

vadrer commented Aug 7, 2018

yes, I think so.
thanks :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment