Interesting - I’ve been retired a few years but the way we used github was git commit, git push, usually at the end of the day. How has the workflow changed so people constantly need it to do any work?
Unfortunately, the ecosystem around github has evolved so that most folks centralize their testing and deployment code into being executed on github infrastructure. Frankly a perversion of the decentralized design of git.
Fortunately for my team, it doesn’t matter because our process requires stuff that can’t be done from github infrastructure anyway, so we have kept the automatic testing and deployment on premise even as github is the ‘canonical’ place for the code to live.
GitHub added CI/CD pipeline functionality (called GitHub Actions). If it’s down I can’t merge code or deploy code anywhere since company policy requires analysis builds to run, and our deploys use the GitHub Actions to ship the code.
GitHub actions is crazy convenient, but it’s a huge pain to run a copy locally. I try not to depend on it too much, but sometimes it is simplest to just go refill my coffee while it figures itself out.
(And it’s almost never down. This week was unusual, to me.)
I still use github for personal projects but have never looked into what the Actions do, since github serves my minimal needs as-is. But it also did when I was working. I would think if people find that depending on certain features ultimately disrupts their work, the smart thing would be not to use those features.
Interesting - I’ve been retired a few years but the way we used github was git commit, git push, usually at the end of the day. How has the workflow changed so people constantly need it to do any work?
Unfortunately, the ecosystem around github has evolved so that most folks centralize their testing and deployment code into being executed on github infrastructure. Frankly a perversion of the decentralized design of git.
Fortunately for my team, it doesn’t matter because our process requires stuff that can’t be done from github infrastructure anyway, so we have kept the automatic testing and deployment on premise even as github is the ‘canonical’ place for the code to live.
Wow, that’s such a classic Microsoft approach - “Embrace and Extend.”
GitHub added CI/CD pipeline functionality (called GitHub Actions). If it’s down I can’t merge code or deploy code anywhere since company policy requires analysis builds to run, and our deploys use the GitHub Actions to ship the code.
GitHub actions is crazy convenient, but it’s a huge pain to run a copy locally. I try not to depend on it too much, but sometimes it is simplest to just go refill my coffee while it figures itself out.
(And it’s almost never down. This week was unusual, to me.)
I still use github for personal projects but have never looked into what the Actions do, since github serves my minimal needs as-is. But it also did when I was working. I would think if people find that depending on certain features ultimately disrupts their work, the smart thing would be not to use those features.
Yes. That would be wiser. But it would also mean setting up a Jenkins server.
No problem. Jenkiins! Get your ass in here!