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

Run tslint on Travis #166

Merged
merged 1 commit into from Jun 12, 2017

Conversation

Projects
None yet
1 participant
@c-w
Copy link
Contributor

commented Jun 9, 2017

This PR adds basic integration with Travis CI.

The CI will still have to be enabled by an admin of the ibex-dashboard repository on the Travis site. I recommend the following setup which we use on fortis-insights:

image

For now, the only CI that is being run is the linter, but adding other tasks on the CI is easy, just a matter of adding another NPM_COMMAND to the env section. Using the env section instead of the scripts section has two advantages: (1) the tasks will get run in parallel instead of in sequence (2) it's easier to see what caused the build to fail, e.g. test issue or lint issue.

@c-w

This comment has been minimized.

Copy link
Contributor Author

commented Jun 12, 2017

CI now set up for ibex-dashboard on the Travis site.

@c-w c-w merged commit b32eda0 into Azure:ibex-version-1.0 Jun 12, 2017

@c-w c-w deleted the c-w:travis-ci branch Jun 12, 2017

@c-w

This comment has been minimized.

Copy link
Contributor Author

commented Jun 12, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.