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

Using TravisCI for testing #199

Closed
H0R5E opened this issue Nov 11, 2020 · 3 comments
Closed

Using TravisCI for testing #199

H0R5E opened this issue Nov 11, 2020 · 3 comments

Comments

@H0R5E
Copy link
Member

H0R5E commented Nov 11, 2020

It looks like TravisCI and CircleCI now both support MATLAB continuous integration. I am going to try and get this working for a copy of WecOptTool on my account and I will report the results here.

@H0R5E
Copy link
Member Author

H0R5E commented Nov 11, 2020

OK, so I have it up and running on H0R5E/WecOptTool-Test with the build being successful on the master branch. I then have a PR where I have broken the code to check that Travis responds.

Couple of notes on this:

  1. It's a bit slow - it's taking about 10 mins to build and test
  2. It doesn't seem to be able to run in parallel even though the parallel toolbox is available and there are 2 cores.
  3. It only works on linux (for now)

In general, though, I would say this is a good thing to have given it doesn't cost us anything. We can also stop worrying about the Jenkins server on the Sandia network.

Let me know if you want to put it into WecOptTool and I will port the changes over.

@ryancoe
Copy link
Member

ryancoe commented Nov 11, 2020

Sounds good. Please proceed.

@H0R5E
Copy link
Member Author

H0R5E commented Nov 12, 2020

Done with 05d7705 and 396b166.

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

No branches or pull requests

2 participants