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

Switch to GitHub Actions #21620

Closed
Fryguy opened this issue Dec 15, 2021 · 6 comments
Closed

Switch to GitHub Actions #21620

Fryguy opened this issue Dec 15, 2021 · 6 comments
Assignees
Labels
Milestone

Comments

@Fryguy
Copy link
Member

Fryguy commented Dec 15, 2021

Our contract with Travis has ended, and while we expected to revert to the prior default of 5 free workers, we were incorrect as it seems Travis doesn't have support for open source anymore, so we're stuck 🙃 (technically they support 10000 free credits which is not much at all). Need to switch everything to GitHub Actions.

Core Repositories

Gems & packages

Non-core repositories

Website and Documentation

Not code

  • ManageIQ/.github
  • ManageIQ/manageiq-design
  • ManageIQ/manageiq-lxca-docs
  • ManageIQ/manageiq-nuage-docs
  • ManageIQ/manageiq-redfish-docs
  • ManageIQ/manageiq-vcloud-docs
  • ManageIQ/manageiq_build_status
@Fryguy Fryguy added the test label Dec 15, 2021
@Fryguy Fryguy self-assigned this Dec 15, 2021
@Fryguy Fryguy added this to the Najdorf milestone Dec 15, 2021
@chessbyte
Copy link
Member

@Fryguy why are the v2v repos in the list above? I thought we no longer pull them in. Or is that just for completeness as well as maybe backporting to branches where they were released before.

BTW, do each of these need to be backported to all the prior branches?

@Fryguy
Copy link
Member Author

Fryguy commented Dec 16, 2021

For now, I just did a grandiose "fetch all public repos that are not forks nor archived" and dropped the list here. Some of them may not apply. Some, like v2v we may want to do anyway for backport reasons. I was already getting lost with what is done/not done, so I wanted a checklist where we can make these decisions.

BTW, do each of these need to be backported to all the prior branches?

I'm not sure yet...we do run cron jobs on older branches, so we may want to backport to at least the branches we care to cron the tests on.

@Fryguy
Copy link
Member Author

Fryguy commented Feb 5, 2022

Need to also fix an issue where branches pushed to local forks fail on the Gemfile.lock.release (though a PR made with that branch will succeed). I thikn it's because it's technically a non-master branch, but also not a PR. Not sure how to solve this just yet, but it's annoying in the GitHub Notifications.

@Fryguy
Copy link
Member Author

Fryguy commented Feb 5, 2022

Other TODO:

@Fryguy
Copy link
Member Author

Fryguy commented Feb 25, 2022

I'm going back and adding crons to all of the repos. As discussed with @agrare we will do all "manageiq application" repos daily and the rest of the repos like gems and such weekly

Core repositories (daily)

Gems and packages (weekly)

Non-core repositories (weekly)

Website and Documentation (daily)

@Fryguy
Copy link
Member Author

Fryguy commented Jan 4, 2023

I'm closing this as completed as of Najdorf. There are a handful of known repos that are more difficult and I will open those as separate issues in their respective repos.

The following still need to be completed but are low priority

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Najdorf
Development

No branches or pull requests

2 participants