121–130 of 140 posts
Earlier quoted context omitted.
GitLab pipelines are really good.
Not in love with its insistence on recreating the container from scratch every step of the pipeline, among a bundle of other irksome quirks. There are certainly worse choices, though.
If you use the built in container registry and build artifacts, you can pass between steps.
Here's 12 Sysadmin/DevOps (they're synonyms now!) challenges, straight from the day job: 1. Get a user to stop logging in as root. 2. Get all users to stop sharing the same login and password for all servers. 3. Get a user to upgrade their app's dependencies to versions newer than 2010. 4. Get a user to use configuration management rather than scp'ing config files from their laptop to the server. 5. Get a user to bak…
Two pints of ale please!
Earlier quoted context omitted.
No, Advent is the liturgical season preceding Christmas, beginning the fourth Sunday before Christmas (which is also the Sunday nearest November 30), it is a period of at least three weeks and one day (the shortest period that can start on a Sunday and include four Sundays.) The 12 days of Christmas start on Christmas and end on January 5, the eve of the Feast of Epiphany. 12-day advent calendars are a fairly recent…
In the Orthodox Church advent starts on November 15th and continues until December 24th.
Earlier quoted context omitted.
What you describe sounds more like a MS "Modern Workplace" / IT support in a corporate environment.
Are we arguing that corporate workers arent "real sysadmins"?
Earlier quoted context omitted.
Are we arguing that corporate workers arent "real sysadmins"?
HN culture as a whole doesnt really recognize the validity of business that buy software vs build software.
Earlier quoted context omitted.
Are we arguing that corporate workers arent "real sysadmins"?
HN culture as a whole doesnt really recognize the validity of business that buy software vs build software.
> you can already build such a system yourself quite trivially by getting an FTP account, mounting it locally with curlftpfs, and then using SVN or CVS on the mounted filesystem. From Windows or Mac, this FTP account could be accessed through built-in software.
Earlier quoted context omitted.
Re: 6. ... Github Actions Github Actions left a bad taste in my mouth after having it randomly removed authenticated workers from the pool, after their offline for ~5 days. This was after setting up a relatively complex PR workflow (always on cheap server starts up very expensive build server with specific hardware) only to have it break randomly after a PR didn't come in for a few days. And no indication that this h…
This is documented currently (supposed to be 14 days). [1] That said, I have found runners to be unnecessarily difficult. But Jenkins and its own quirks, and when I used GitLab, it used ancient docker-machine and outdated AMIs by default. I think Buildkite has been the only one to make this easy and scalable. But it is meant for self hosted runners. [1] https://docs.github.com/en/enterprise-cloud@latest/actions/h...
Earlier quoted context omitted.
Many, many reasons... the most important of which is, Jenkins is a constant security nightmare and a maintenance headache. But also it's much harder to manage a bunch of random Jenkins servers than GHA. Authentication, authorization, access control, configuration, job execution, networking, etc. Then there's the configuration of things like env vars and secrets, environments, etc that can also scale better. I agree G…
I really scratch my head when I read your comment, as nothing of this is a real issue in my Jenkins. > bunch of random Jenkins servers Either PXE boot from an image, or k8s from an image, have a machine or pod rebooted/destroyed after one job. Update your image once a month, or have a Jenkins job to do that for you. > Authentication, authorization, access control Either use LDAP or Login via Github, and Matrix securi…
And this is if you get to manage it! Often there's 5 different random Jenkins servers set up by different teams, all of which are EOL and rife with security holes, and they expect you to fix them when they break, nobody version controls their configs or backs them up (they haven't even heard of CasC and have no interest in using it), and your boss says you can't say no, and also you can't upgrade them/take them over. I've seen million-dollar products which are completely dependent on over a thousand Jenkins jobs on an out-of-date Jenkins server, so complex and intertwined it couldn't be replaced.
If it were up to me, I would replace most CI with Drone.io (or Woodpecker CI if it ever gets feature parity). Now that's a dead simple CI system.