But any new product, especially beta access, is bound to give you a little grief. ![]() Feel free to disregard that step's run line to downgrade bundler. Lastly, I have standardized on Bundler 1.17.3 until a few v2 kinks are worked out. Here I am using the matrix context but there are others like github, job, steps, secrets, and more. GitHub Actions has several context objects that can be used from setting environment variables to expressions. So make them logical to you or your team. ![]() Again these step names show up as headers in the log view. By default the checkout action does not so I added one. Keep the name logical to the workflow.Įach step can have a name attribute as well. This is what shows up when you browse all Actions in GitHub's user interface. Renamed the top level name from Ruby to CI. Name : CI on : jobs : test : runs-on : ubuntu-latest strategy : matrix : ruby : - ' 2.5.x' - ' 2.6.x' rails : - ' rails_v5.1.x' - ' rails_v5.2.x' - ' rails_v6.0.x' steps : - name : Checkout uses : - name : Setup System run : | sudo apt-get install libsqlite3-dev - name : Setup Ruby uses : with : ruby-version : $.gemfile" gem uninstall -aIx bundler gem install bundler -v 1.17.3 bundle install -jobs 4 -retry 3 - name : Test run : bundle exec rakeĪ few highlights on why I landed on the specifics of this workflow above. Let's dig into my notes on how I setup my first CI workflow with GitHub Actions. No bounds on scaling.Įnough hype and reasoning.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |