Travis are have changed their open-source free tier, which places heavy restrictions on our needs. We are currently on a paid plan, but are looking to migrate off.
These may already have all their actions migrated, although I think its mostly docker build files.
They should have all actions migrated, and be removed from travis
[ ] json_api_client
This is a fork of another gem, which brings in some fixes. We should focus of migrating to the latest version, rather than maintaining a fork.
Repos without CI
These repos currently have no CI solution. In some cases its because one probably isn't warranted.
CI needed?
[ ] sequencescape-client-api
[ ] sprint_client
[ ] hca-print-tool
[ ] ftpcmd
[ ] warehouse_two
CI probably not needed
[ ] storelight-sql
[ ] config
[ ] .github
[ ] beckman-robot-scripts
[ ] deployment
[ ] provision
[ ] usg_scripts
[ ] ss_cherrypicking (Empty repo)
[ ] plate_barcode [ Migrate to baracoda instead ]
[ ] General backlog items
[ ] axlsx [Migrate to community fork instead of maintaining our own]
[ ] label_printer [Yana's tool, mostly replaced by steve's recent stuff, not sure how you'd ci the tests]
[ ] sequencescape_search [I don't think we use this?]
[ ] sanger_barcode [Legacy barcode printing]
[ ] irods_reader [Not using functionality]
[ ] psd_logger [No longer used?]
Repos already on GH actions
These repos either never used travis, or were migrated a while ago. I'm judging this by the presence of a .github/workflows folder
Background
Travis are have changed their open-source free tier, which places heavy restrictions on our needs. We are currently on a paid plan, but are looking to migrate off.
I have made notes about the changes made to migrate Sequencescape here: https://github.com/JamesGlover/travis_to_gh_actions
Migrated
Still on travis, but some actions
These may already have all their actions migrated, although I think its mostly docker build files. They should have all actions migrated, and be removed from travis
Repo to migrate
Probably don't migrate
Repos without CI
These repos currently have no CI solution. In some cases its because one probably isn't warranted.
CI needed?
CI probably not needed
Repos already on GH actions
These repos either never used travis, or were migrated a while ago. I'm judging this by the presence of a .github/workflows folder