Jenkins

Oh, I've seen things, yes.

I've actually seen things that came before Jenkins, which were very nice, and Jenkins was released in the 2000s.

That was actually a pretty looking thing.

Like a lot of people not share that opinion today, but back in the day, it was a huge improvement comparing what it used to be before.

You create a branch, open pull request, you run the CI on a pull request, get the feedback, iterate until it's green, then you merge.

So that was that is how it is nowadays.

There are some deviations from that, but this pattern i would say emerged over time because where we started was a separate ict server and you would have a separate version control system well the git was distributed so you could We did it in many places, but like Bill Cruz and Jenkins and all of those stuff.

What was it, Team City back in the day?

So the, the problem was, um, back then, uh, like five years ago, when I started working on project, I had...

I was main- I was working at the time on the Jenkins project.

Mm-hmm.

Uh, we had a lot of Git repositories, custom application, Java libraries, and so on.

And one of the project work which is still running today is the infrastructure where we run the Jenkins, where we test Jenkins, and so on.

Mm-hmm.

And so all that infrastructure is managed by, um, uh, infrastructure as code, like Puppet, Kubernetes, and so on.

[laughs]

Now, for the open source software community, the cloud has been a boon generally, accelerating development and adoption.

commercial cloud providers indeed offer fully managed services for many popular open source software up and down the stack from container orchestration tools like Kubernetes and Docker to databases like Postgres to integrated CI CD and DevOps tool chains like Jenkins for automating code and software delivery and for hosting applications in many different ways.

The pay as you go model as well, I think provides flexibility and a lower cost of ownership, which along with a number of these other benefits shown here, drives developers to build community projects in the cloud more and more.

So there's a similar interplay at work between the big data sphere and the cloud.

You used one vendor for source code management, a completely different CICD tool to run the actual tests.

Usually Jenkins or something like that.

Exactly.

Then a third-party security scanner and yet another platform for deployment.

CircleCI was out there forever.

There's always Jenkins.

No.

I mean, Cursor's