Since the release of GitHub actions I always wanted to setup a continuous integration using GitHub actions as described in their documentation.
Wh...
For further actions, you may consider blocking this person and/or reporting abuse
Docker Compose is definitely installed on GitHub actions, not sure what you mean by "no support".
Here's the Workflow that uses
make
tasks to run thedocker-compose
commands: github.com/weathermen/soundstorm/b...And the Makefile, which runs them: github.com/weathermen/soundstorm/b...
Thanks for that! I just removed that part. I tried to use it though and ran into issues mostly because my setup is not fully docker-compose based. I use docker-compose only for services, my Rails code runs in the ubuntu container from GitHub.
So the issue I get is this one:
My docker-compose.yml:
The volume is mounted with a user/permission that is different from the one used when I run the
rails test
command. I tried to work around that without luck, if you have any idea let me know. From what I can tell I think your whole infra runs in a docker container while me I always run Ruby/Rails locally and only use compose for services (good or bad that's how I do it for now).Thanks again!
Hi, I've found tricky solution for the manual trigger and also others completed my answer on stack overflow: stackoverflow.com/questions/589331...
Oh wow that's very clever, and I read also the comment on SO from someone saying you could also limit that to the repository owner.
Do you know what it would take to update my current gist to allow for the repository owner, when they star the repo, to trigger a build?
Right now I have:
what do I need to change? I am new to the syntax :D
Alright, you can try this :
Notice you may have to reindent but I hope it would be fine :)
Thanks, I guess the last step is on how to combine what you propose with an already in place workflow that gets executed at push time.
For now I have:
But if I change that to what you propose then my workflow is no more executed at push time.
Do you know if we can combine both manual trigger trick + usual push testing in a single or a combination of workflows maybe? Let me know!
Yes, I set just the beginning but you can adapt it for an existing workflow or a new one.
Yes you can !
For your example it will be like that :
I din't try out yet this but I've already tried to setup a workflow with push event and cron, so it should be fine !
Hi,
I was working on a very similar article (Actually, I'm not sure that I'll publish it now XD).
In my workflow, I set up two tests. The first one uses Rubocop to do static analysis of the code, and the second one uses RSpec and then generate a report using SimpleCov.
You can check my yaml file here
I also noticed another issue when I was trying to use environment variable to specify the version of the operating system that will be used for the tests.
Great job, thanks for sharing.
Hey there, thanks for the comment. Indeed I haven't yet setup multiple steps with dependencies in my setup. I might have to and your example will be very useful, thanks!
Nice posts!. Don't you have in your bag a tuto on how to setup correctly a dockerized React + Rails API using Sidekiq/Redis? As a newbie, developing an app is not so difficult, but deploying it, env variables, the database config.. all these kind of things is a real nightmare.
Hey there, sorry I do not have that (also, I stopped my Rails learning and went back to Node.js!).
Good luck though, thanks for your comment
So helpful! Thank you!
Awesome guide! Thanks so much!
Do you have any experience with using environment credentials in Github actions? Or should the master.key override the test.key anyway?
I have no experience but this post: stackoverflow.com/questions/614445... suggest using a test key and uploading it to GitHub I guess