On GitLab, you start from a docker image, so it's harder to setup some things but easier for others. If you are very good at docker and don't mind making your own images just for CI purposes, then go ahead.
I think I'd probably consider myself at/near expert-level with Docker, but CI/CD runners instanced in containers just doesn't work for some of our workloads.
As an example, some of our projects have a bunch of Docker images that get built via their own Dockerfiles in the repo, are ran and discarded during the workflow, and each one is modifying the checked-out source tree in some fashion (NPM stuff, composer, whatever, etc), and then a final prod Docker image is built and tested from that source repo tree that has been modified by the Docker containers built/ran/discarded during the workflow. So in Gitlab, it sounds like we'd be running Docker in Docker for some projects.
You ever ran Docker in Docker? It's temperamental at the very best and there are a thousand gotchas associated with it, not to mention having to worry about how many variable scopes deep you are and keeping track of that, how to properly bind mount volumes into the nested Docker containers because the method and paths will vary depending on how nested you are, etc. It's just an absolute nightmare to deal with all-around in that context.
I'll see if we have some projects I can try out on it, but the majority of ours are like what I described above.
Imagine they skip 12 and call it 13 like they did with W10
With as little sense as Microsoft makes most of the time, that decision actually does make sense. A lot of programs and scripts were lazy about checking the Windows version and just checked for the presence of a '9' in the version string to determine if they were running on Windows 95/98.
A bunch of shit would have broken if they had released Windows 10 as Windows 9, which is what it should have been semantically.
You know, it's surprisingly vague even in the official documentation.
You just described literally all of Lemmy's documentation.
I had to read the source code for Lemmy to find out what API endpoint to hit, how it worked, and what to expect on return for a script that I was writing. You need to do that for some documented API endpoints as well. Calling it "vague" is a nice way to put it.
tool @ tool @lemmy.world Posts 0Comments 96Joined 2 yr. ago
Or just cleared the SAM password altogether. Windows is trivially easy to break into if you have physical access and the volume isn't encrypted.