581–590 of 853 posts
It is us, developers, who convinced our management to purchase GitHub Enterprise to be our forge. We didn't pay any heed to the values of software freedom. A closed source, proprietary software had good features. We saw that and convinced our management to purchase it. Never mind what cost it would impose in the future when the good software gets bad owners. Never mind that there were alternatives that were inferior…
it changes and you move on.
It is us, developers, who convinced our management to purchase GitHub Enterprise to be our forge. We didn't pay any heed to the values of software freedom. A closed source, proprietary software had good features. We saw that and convinced our management to purchase it. Never mind what cost it would impose in the future when the good software gets bad owners. Never mind that there were alternatives that were inferior…
Are there bring-your-own-agent CI platforms that don't have pricing structures like this? Buildkite and CircleCI do.
CircleCI does only charge for self-hosted runners generated egress and/or artifact storage: "Any Network Egress to CircleCI will be charged. At this current time, this includes CircleCI Caches, Workspaces, and Artifacts and will be charged at the normal rate according to your Usage Controls. The only network traffic that will result in billing is accrued through restoring caches and workspaces, and downloading artifa…
It is us, developers, who convinced our management to purchase GitHub Enterprise to be our forge. We didn't pay any heed to the values of software freedom. A closed source, proprietary software had good features. We saw that and convinced our management to purchase it. Never mind what cost it would impose in the future when the good software gets bad owners. Never mind that there were alternatives that were inferior…
It's not my money man. It's still fine.
Earlier quoted context omitted.
Am I right in assuming it’s not the amount of payment but the transition from $0 to paying a bill at all? I’m definitely sure it’s saving me more than $140 a month to have CI/CD running and I’m also sure I’d never break even on the opportunity cost of having someone write or set one up internally if someone else’s works - and this is the key - just as well. But investment in CI/CD is investing in future velocity. The…
Have you ever set up GitHub Actions? The outcome is brittle because of their platform, not because of my inability to do CI.
When CI and CD stop being flat and straightforward, they lose their power to make devs clean up their own messes. And that's one of the most important qualities of CI.
Most of your build should be under version control and I don't mean checked in yaml files to drive a CI tool.
Earlier quoted context omitted.
or alternative hire right people that know what they are doing and don’t need a whole lot of junk to work on and deploy. I have been coding 31 years now and don’t have the slighest clue why anyone would ever need a “github action”
There's value in enforcing checks on the server side to avoid people accidentally/maliciously merging code that doesn't pass said checks. Checks can be linters, security scanners, etc.
Earlier quoted context omitted.
Have any suggestions to those community-developed and maintained options?
Gitea. Gitlab (ish?).
Earlier quoted context omitted.
short-term maybe, but piracy is making a come back
It never left
With DVD, Netflix if something I wanted to watch wasn't on any of my streaming services, it was almost guaranteed to be on DVD Netflix. That fallback doesn't exist anymore.
Earlier quoted context omitted.
This kinda change also has some different gears turning in my head. At $0.002 / build-minute, some of our large software integration tests would cost us around 15 - 20 cents. Some of our ansible integration tests would be 5 - 10 cents - and we run like 50 - 100 of those per day. Some deployments might cost us a cent or two. Apples to oranges, naturally, but like this, our infra-jenkins master would pay for itself in…
> And I mean sure, everything is kinda janky on Jenkins, but everything falls into an expectable corridor of jank you get used to. Self-hosting Jenkins on an EC2 instance is probably going to result in a _better_ experience at this point. Github Cache is barely better than just downloading assets directly, and with Jenkins you can trivially use a local disk for caching. Or if you're feeling fancy and want more isolat…
Hardware is getting cheaper and cheaper, but the fear-mongering around running a Linux machine has successfully prevented most businesses from reaping those cost reductions.