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

Set up CI build & test for pull requests #22

Closed
bwillard opened this issue Jan 7, 2018 · 4 comments · Fixed by #83
Closed

Set up CI build & test for pull requests #22

bwillard opened this issue Jan 7, 2018 · 4 comments · Fixed by #83
Assignees

Comments

@bwillard
Copy link
Contributor

bwillard commented Jan 7, 2018

We should ensure that all PRs build and pass tests before submitting.

@bwillard bwillard added this to the Stable Infrastructure milestone Jan 7, 2018
@rtannenbaum
Copy link
Contributor

Brian did an initial investigation, based on that I think we should try the free Travis CI edition to start.

Some notes:

  • Free edition does not require code write access, whereas Paid edition might, due to permissions not being granular enough. (Does require webhook access; Github's API for responding to repo events)
  • Travis supports Node.js whereas others (like Circle) do not. We might need Node.js support for our angular frontend, which has some dependencies on Node even though we don't use it directly
  • Uses a shared worker pool for the rest of the org (google) so we may run into latency problems, but we may move our repo to a different org at some point.

@rtannenbaum
Copy link
Contributor

Travis instructions for java projects. Includes both Maven and Gradle examples. https://docs.travis-ci.com/user/languages/java/

rtannenbaum added a commit that referenced this issue Jan 10, 2018
for #22.

Travis should automatically detect that we use Maven based on the presence of pom.xml.
rtannenbaum added a commit that referenced this issue Jan 10, 2018
to make sure it breaks the Travis build (#22)
rtannenbaum added a commit that referenced this issue Jan 10, 2018
rtannenbaum added a commit that referenced this issue Jan 11, 2018
@rtannenbaum
Copy link
Contributor

Forgot we still need to test frontend, will reopen this

@rtannenbaum rtannenbaum reopened this Jan 11, 2018
rtannenbaum added a commit that referenced this issue Jan 11, 2018
@rtannenbaum
Copy link
Contributor

@holachuy once we get the Jasmine/Karma tests passing it looks pretty easy to get Travis to run 'ng test'.

I sent a PR to fix a couple initial issues but I think I'd need to read up a bunch on Angular, Jasmine and Karma to get any further. Would it make more sense for you to fix them?

rtannenbaum added a commit that referenced this issue Jan 16, 2018
A couple fixes to get 'ng test' working for #22
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 a pull request may close this issue.

2 participants