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

migrate to github actions #491

Merged
merged 19 commits into from
Feb 16, 2020
Merged

migrate to github actions #491

merged 19 commits into from
Feb 16, 2020

Conversation

dbarrosop
Copy link
Contributor

@dbarrosop dbarrosop commented Feb 15, 2020

Adios travis, hola github actions.

In addition I removed the dependency of running the tests inside containers. I am not a fan of that change but it simplifies the migration. I might look into reverting this in the future but for now this is cleaner and easier.

Copy link
Collaborator

@dmfigol dmfigol left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great work!
I have mostly comments:

  1. currently the build is triggered twice on push to a branch involved in PR. I haven't found an easy way to change it so it covers all our needs and probably complexity is not justified, especially considering it's GH CPU cycles, so whatever :D
  2. actually I like that we don't run nornir in docker and just use venvs, I have nothing against it.
  3. I have some concerns about caching the whole venv, but I think we can wait a see if we hit any issues. Alternative would be caching pip wheels.
  4. I see that pytest skip was removed. I probably still want to have a way to skip tests which depend on services, but it could be a separate PR if needed. Also we will probably not have these services tests anyway once plugins are removed from the core.

It's LGTM, though I'd suggest not merging this until @ktbyers has a chance to go through it too so he is somewhat familiar with the change as well.

@ktbyers
Copy link
Collaborator

ktbyers commented Feb 16, 2020

This is fine with me.

@dbarrosop
Copy link
Contributor Author

currently the build is triggered twice on push to a branch involved in PR

Yes, that's by design and that's correct. The jobs may contain different code if your branch is missing some commit from base.

@dbarrosop dbarrosop merged commit de1dcfe into develop Feb 16, 2020
@dbarrosop dbarrosop deleted the gh_actions branch June 18, 2020 12:16
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 this pull request may close these issues.

3 participants