I guess that's convenient because there's some ready-to-use actions out there and you can quickly setup them. At work I don't worry about this because there's a nice workflow using gerrit and jenkins, but if I wanted to setup something like it for my personal projects quickly I'd go for something like what you are doing, or setup some local actions for tests and deployment (I almost always use the second option in my projects)
Exactly - I spent maybe seven minutes total customizing the pre-built YAML on both these actions, which is about how much time I want to spend on CI/CD for a hobby project.
For local actions, I've always just used a Makefile, or NPM scripts when relevant - how do you manage yours?
I used to make a "scripts" folder in each project containing shell/python scripts to make my life easier, but since most of my workflow in personal projects (mostly written in c++) end up only in dealing with dependencies and running tests, I just create a conanfile for the dependencies and write tests using catch2. But github actions look cool, maybe I'll start experimenting with it as well or set some private ci workflow.
Oh wow, first I've heard of conan - definitely going to explore this as I dig deeper with C++. I think GH actions can be used in concert with something like this, yes, I'm generally impressed with the UX.
Thank you!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I guess that's convenient because there's some ready-to-use actions out there and you can quickly setup them. At work I don't worry about this because there's a nice workflow using gerrit and jenkins, but if I wanted to setup something like it for my personal projects quickly I'd go for something like what you are doing, or setup some local actions for tests and deployment (I almost always use the second option in my projects)
Exactly - I spent maybe seven minutes total customizing the pre-built YAML on both these actions, which is about how much time I want to spend on CI/CD for a hobby project.
For local actions, I've always just used a Makefile, or NPM scripts when relevant - how do you manage yours?
I used to make a "scripts" folder in each project containing shell/python scripts to make my life easier, but since most of my workflow in personal projects (mostly written in c++) end up only in dealing with dependencies and running tests, I just create a conanfile for the dependencies and write tests using catch2. But github actions look cool, maybe I'll start experimenting with it as well or set some private ci workflow.
Oh wow, first I've heard of conan - definitely going to explore this as I dig deeper with C++. I think GH actions can be used in concert with something like this, yes, I'm generally impressed with the UX.
Thank you!