RE: GIT feature branches vs. Continuous Integration (CI) - Improve your software development
Hey, good advice here.
Would you like to have a quick look at the Steem FOSSbot Voter repo and tell me what you think of the management there? I do not use CI, not sure how to do that with a Node.js server.
I'm the only developer 😭 bar a few small contributions, but I manage it in a hierarchy like this
master - only for releases or emergency patches
^
develop - all devs work ends up here after a short period ideally (daily, or similar)
^
personal branch - work on this, merge from develop often, and merge to develop when appears more or less stable
So it's a pipeline that goes up to master.
I also use some other branches, one as a kind of scratchpad for dirty testing (as deployment is easiest from GitHub), some for the docker deployments which have some extra files and for the sake of convenience branches are the best way to go I think.
Hay @personz,
thank you for your feedback = )
So from what you describe you basically went for the pretty standard "gitflow" strcuture.
Source
Without using feature branches. From my point of view thats totally fine and when you are the only developer it also saves you some overhead.
Regarding the CI topic: I would absolutly recommend to go for that if you have some hardware available to setup a CI Server. Jenkins for example is available as a Docker-Image in can be setup in seconds. Here is a tutorial how to create a CD job for Node.js: https://codeforgeek.com/2016/04/continuous-integration-deployment-jenkins-node-js
Best regards!
Thanks for the link
You're always welcome ;)
Thank you! I'll give it a lot, it would be really useful I think. 😆