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

Expand our CI Tools Build Test Configuations #98

Closed
odysseywestra opened this issue Jul 3, 2017 · 1 comment
Closed

Expand our CI Tools Build Test Configuations #98

odysseywestra opened this issue Jul 3, 2017 · 1 comment
Assignees
Labels
type.Project Issue is important for a milestone

Comments

@odysseywestra
Copy link
Member

After we address #97, we should add various build configurations tests as well to avoid any commits or pull requests that may potentially break the building process. I'll probably work on this one when it comes time to. In the meantime what build config options should we test out? The obvious first choice should be --gegl-enabled option.

@odysseywestra odysseywestra added the type.Project Issue is important for a milestone label Jul 3, 2017
@odysseywestra odysseywestra self-assigned this Jul 3, 2017
@jtojnar
Copy link
Contributor

jtojnar commented Aug 5, 2024

Weirdly, there should have been CI for those variants at the time of opening this issue:

7e522a5
8d81a62

We no longer use Travis but the matrix got ported to GitHub actions:

461cf8d

@jtojnar jtojnar closed this as completed Aug 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type.Project Issue is important for a milestone
Development

No branches or pull requests

2 participants