3 ms·

On this note, I started a little project to convert Travis.yml workflows to GitHub Actions: https://akx.github.io/travis-to-github-actions/ https://akx.github.i

• hakre 6y ago
  Looks nice, thanks for sharing. For the part to execute the run-script I'm currently going with a github-action itself: https://github.com/marketplace/actions/run-travis-yml https://github.com/marketplace/actions/run-travis-yml it's based on the original travis-build so that utils like "travis_retry" are still available. each command in the asserted stages (e.g. before_install, install) directly breaks the build while the script runs through and gives the fail exit at the end (while showing the commands run and their result as on travis, asserted stages are with folding). might be a good addition to the online converter. the other parts of the workflow (vm setup, caches, services, matrix etc.) I find hard to port automatically. this needs much more insight and often is specific to the languages. and then it's "relatively easy". but an automatic mapping from the many languages travis supported looks overwhelming. perhaps better is to actually have the whole travis-build project as a github action (but I'm not fluent with ruby).