-
-
Notifications
You must be signed in to change notification settings - Fork 347
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
review chore: improve Travis configuration and speed-up builds #1655
Conversation
I think you can simplify
|
What do you mean by "simplify"? |
is useless: is only required for the verify job is useful for something but I don't remember for what (website?): |
Thanks, I'll check that and try to improve the script. |
ping @monperrus ok for merging this one? It would speed up the builds |
It's a really good start. I would propose to split in two and refine: Split in two:
About the Travis job design, instead of a build Matrix, I would propose explicit names in Travis, and hence in the UI of travis (currently the job names are not super clear). The names would be:
|
I think it is not possible: travis-ci/travis-ci#5898 |
If you look at the Astor jobs: it's pretty clear: https://travis-ci.org/SpoonLabs/astor
So we can probably workaround if we have only one environment variable.
env:
SCRIPT=jdk9.sh
SCRIPT=jdk8.sh
SCRIPT=checkstyle.sh
and the scripts would call Travis "jdkswitcher" themselves.
…--Martin
On 10/31/17 3:44 PM, Thomas Durieux wrote:
About the Travis job design, instead of a build Matrix, I would propose explicit names in
Travis, and hence in the UI of travis (currently the job names are not super clear). The names
would be:
I think it is not possible: travis-ci/travis-ci#5898
<travis-ci/travis-ci#5898>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1655 (comment)>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAxDUv1F7rXa5oKHrXVcrmkhLtQtuvsIks5sxzJBgaJpZM4QHbAJ>.
|
@monperrus for me it's ready to merge |
super maintainable! thanks! |
Fix #1653