Skip to content
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

Modularize travis #6

Merged
merged 4 commits into from
May 11, 2018
Merged

Conversation

b-studios
Copy link
Contributor

@b-studios b-studios commented May 11, 2018

As suggested in #5 by @kayceesrk, I started modularizing the travis build by explicitly listing all programming languages in the build matrix. The environment variable PROGLANG is used to only select the folder of the corresponding language in the make file.

Here is a a build job using this config.

@kayceesrk Could you review the ocaml setup? Is it really necessary to build ocaml every time? Can we cache this?

@kayceesrk
Copy link
Collaborator

Great! So the PR also only builds the folders for the given language that corresponds to the current PROGLANG?

We should cache base OCaml (4.03.0) definitely. But we should build Multicore OCaml from scratch to make sure the examples work with trunk.

@kayceesrk kayceesrk merged commit a6b89af into effect-handlers:master May 11, 2018
@b-studios
Copy link
Contributor Author

So the PR also only builds the folders for the given language that corresponds to the current PROGLANG?

Yes, you can see that in the output of the build matrix: https://travis-ci.org/effect-handlers/effects-rosetta-stone/builds/377719375?utm_source=github_status&utm_medium=notification

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants