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

Setup CI for automatic testing #1

Closed
wants to merge 1 commit into from
Closed

Setup CI for automatic testing #1

wants to merge 1 commit into from

Conversation

MrMinos
Copy link

@MrMinos MrMinos commented May 3, 2020

Do not merge yet!

  • We can use GitLab or TravisCI, I have no preference, GitLab had a smaller barrier for me to get going
  • I would like to see each teams having at least one model test that they would like to run automatically, so that we can do the "real thing"
  • Would need to resolve dependencies as teams add their own pytest cases; as well as once we figure out what the simulator tests will look like

@AVSurfer123
Copy link
Member

@MrMinos Where is this CI being run? It looks like you have some type of server set up for it to access? Also I'm assuming GitLab works with Docker right?

@AVSurfer123 AVSurfer123 added the build Issues related to build/CI label Jul 27, 2020
@MrMinos
Copy link
Author

MrMinos commented Aug 6, 2020

@AVSurfer123 Sorry I was MIA past two weeks.

Currently there is no CI running. This PR contains .yml file for using GitLab's CI, but I remember us having discussions in the meeting about using Travis CI.

I will have to catch up on the current simulation setup with Jenny and et al, and we should discuss the best path forward.

My current thought for CI automated simulations is, we would not want a graphical output. We would purely want numerical simulations in the CI pipeline.

@pullapprove pullapprove bot requested a review from himty September 8, 2020 18:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
build Issues related to build/CI
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants