Dahhhh. Pay for a damn hosted CI server please, like Circle or Travis, so I don't have to maintain this crappy Jenkins instance. More "plugin" updates by default than a crappy wordpress site.

Talking of which. Circle CI has come on leaps and bounds since I last looked at it. So much nicer than Travis. Think this is going to be my de-facto CI solution for open source stuff from now on.

I love gitlab also for this!

write a concept paper on how a cloud ci saves time and money with all the benefits circle ci brings over jenkings.
Pitch it to your boss.

@heyheni Ah, I wish. Last time I tried something like that I got a "Damn that's expensive. And why have you spent time on this? You've got loads of other work to do!"

@AlmondSauce if your boss doesn't like to save money how is this company still in business? 😏

@heyheni they only listen to non-IT higher ups ironically

We use Bitbucket for CI/CD (mainly because we use Atlassian for everything but that's not the point). I don't know how much it costs but with our plan we get 50 build minutes and we usually buy 1000 more build minutes for $10. You can make your own Docker images to significantly speed up your pipeline and reduce the build time so you probably won't even need to buy the extra 1000 build minutes if you only build on pull requests.(as we do)

@jurion You're literally the first person I've heard who has said that... Why?

@jurion CI can be whatever you make it. Some just use it to verify the code compiles, others use it to kick of scripts, update environments, initiate testing procedures, deploy to multiple environments, etc.

Personally I'd say that it's a worrying sign if you can't reliably automate it. Your team should not be routinely adding dependencies that your stack and tool chain can't handle - if they are, it's a sign of an incredibly fragile tool chain that's bound to break at some point. Something as simple as a new transform should be checked into the repo, and then just work for anyone (or anything) that checks it out.

@jurion I've never used Azure, so I can't comment. But most of the popular CI tools I've used literally run off a docker image - so you install whatever you want in that image, including all your dependencies, then forget about the specifics.

Could be Azure doing something funky though. This is MS.

@jurion I'm not sure how *not* using containers makes that easier? The very definition of containers is that you just have your container initialisation file to maintain, 0 VMs, 0 servers, etc.

Want to switch a dependency? Never mind an hour's work, it's then a case of changing a single line in that file.