Me: (having realized that the #Terraform code I delivered to a user is probably going to leave that user baffled, opts to create a #GitLab #CI-pipeline that will make use of the TF code easier) "Hey, , you need to stand up a #GitLabRunner for the project to be able to use the #pipeline I created for you"
User: "Let me get a runner installed!"
(time passes)
Me: (after noticing that has finally registered a runner) "Uh… That runner you registered isn't going to be usable with the pipeline I created for you. You configured the runner to only run tagged jobs. Further, you also configured it to only run jobs with a specific tag. The pipeline I created for you doesn't have any tagged jobs, let alone the one you allowed your runner to handle: your runner isn't going to be able to run any part of the pipeline."
#DevRants
#ITrants
#cipipeline
Sure thing... let's make it even MORE horrible.
#CI #CD #CICD #CIPipeline #React #ReactNative #Windows
@melix That said, I know a framework's #cipipeline, like Micronaut's, can be quite different. I'm curious, you think that pipeline is using #docker #frugally or perhaps it's overused b/c it's so convenient?
@melix Been there!
I recently revamped the #cipipeline of a service at work & managed to cut down the time by ~60%.
The trick was to avoid #docker (dind) & reuse the already provisioned resources (ie the build container) while ensuring a #ReproducibleBuild: while docker was used for almost anything, turned out the only time we really needed docker was for consumer #ContractTesting & #EndtoEndTesting and w/ a bit of effort we could safely run most of the tests in the original container.