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

Travis CI integration #2

Closed
nahumj opened this issue May 18, 2015 · 11 comments
Closed

Travis CI integration #2

nahumj opened this issue May 18, 2015 · 11 comments
Assignees

Comments

@nahumj
Copy link
Collaborator

nahumj commented May 18, 2015

No description provided.

@SensibleSalmon
Copy link
Collaborator

+1 to CI, though I feel unit testing should come first.

@SensibleSalmon
Copy link
Collaborator

Though, adding tests is a never ending process. I'd like to get catch integrated and have a way of metricing code coverage before getting a CI up.

@mercere99
Copy link
Member

Sounds like a good plan. I think the CI will be pretty straightforward in comparison to the testing framework as a whole, so it makes sense to do the testing first.

@SensibleSalmon SensibleSalmon self-assigned this Oct 30, 2015
@SensibleSalmon
Copy link
Collaborator

@mercere99 Looks like whoever does this will need admin access to the repository

@SensibleSalmon
Copy link
Collaborator

@mercere99 Actually strike that, it looks like Travis is built to interface eiither with personal projects that one is the owner of (i.e. you, for Empirical) or with organizations via a user with admin authority.

Not sure if it supports integrating with a personal repo via someone that isn't the owner.

@mercere99
Copy link
Member

Okay -- let me know what you need me to do to get things setup.

@SensibleSalmon
Copy link
Collaborator

I believe if you follow the steps at https://travis-ci.org/getting_started I
can manipulate the yml config gile to do what I need--the travis admin page
isn't very extensive so I assume much of it can be configured within the
yml file.

(Might also be worth looking into transferring custody of Empirical to an
organization, but that's a discussion for another time, I think.)

On Thu, Nov 5, 2015 at 5:34 PM Charles Ofria [email protected]
wrote:

Okay -- let me know what you need me to do to get things setup.


Reply to this email directly or view it on GitHub
#2 (comment).

@emilydolson
Copy link
Collaborator

Transferring it to the Devosoft organization might be a relatively easy solution.

@mercere99
Copy link
Member

Transferring it to Devosoft should be a viable option. I just sent Jake a member request and made Emily an owner of the organization (since I don't think I'm going to be able to look at this in more detail until some time next week at soonest)

@SensibleSalmon
Copy link
Collaborator

Happening in #32

CI is up and running and can be observed in #32 for now. Once it's merged it it should Just Work (tm) automatically on any push into the repo/PR. PR CI status is view able within the PR and all builds can be seen at https://travis-ci.org/devosoft/Empirical/builds

@SensibleSalmon
Copy link
Collaborator

Closing #2, resolved by #32

amlalejini referenced this issue in amlalejini/Empirical Nov 30, 2018
FergusonAJ added a commit that referenced this issue Jul 19, 2022
Pull MABE systematics into VCPU merging branch
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

4 participants