I'm just getting started using it, but it seems like the solution to scaling up to a lot of Jenkins jobs. There's a good talk about it, and since you're one of only two people in the thread who used the word DSL and you are having a good experience with Jenkins, I thought I'd ask.
My config is similar except my single EC2 node is actually running Kubernetes via kubeadm, it's a single node Kubernetes cluster and has enough room for about 3 of my worker pods to execute concurrently before the rest have to wait.
(But that's just my setup and has nothing to do with Job DSL.)
For me, managing Jenkins via the helm chart has been the best part of the deal, but I'm a pretty big fan of Helm already...
Let me start by saying that we used to use GitLab, a lot of it was because of the CI but I didn’t have a great experience trying to manage it on top of Kubernetes, they’ve since introduced a Kube native package and I’ve been told it’s much easier, but with the deployed omnibus we ran into a lot of issues with runners randomly disconnecting, it became frustrating to the point where I had developers not wanting to use GitLab and finding interesting ways to work around it.
So I set up Jenkins on a dedicated EC2 instance with a large EBS volume for workplace storage and installed the Jenkins plugin then I wrote a Jenkins library package that exposes a function to read a gitlab yaml file and generates the appropriate stages with parallel steps that execute as pods in khbernetes - took about a week to get the things we actually used from Gitlab CI and their YAML DSL working correctly.
Now we very happily use Jenkins, mostly through YAML but in the occasions where things are much easier going directly to Groovy to use interface with plugins, developers can.
GitLab and their approach to CI (easy to use yaml) really facilitated developers writing CI, which increased our software quality overall.
Let me start by saying that we used to use GitLab, a lot of it was because of the CI but I didn’t have a great experience trying to manage it on top of Kubernetes, they’ve since introduced a Kube native package and I’ve been told it’s much easier, but with the deployed omnibus we ran into a lot of issues with runners randomly disconnecting, it became frustrating to the point where I had developers not wanting to use GitLab and finding interesting ways to work around it.
So I set up Jenkins on a dedicated EC2 instance with a large EBS volume for workplace storage and installed the Jenkins plugin then I wrote a Jenkins library package that exposes a function to read a gitlab yaml file and generates the appropriate stages with parallel steps that execute as pods in khbernetes - took about a week to get the things we actually used from Gitlab CI and their YAML DSL working correctly.
Now we very happily use Jenkins, mostly through YAML but in the occasions where things are much easier going directly to Groovy to use interface with plugins, developers can.
They're also just useful for super targeted ads.
shrug
FlexShopper is the leading online lease-to-own platform, with the largest LTO marketplace, an LTO payment method for third party sites, and an expanding portfolio of verticals for generating leases online.
FlexShopper is seeking smart, energetic, passionate engineers to join a growing team to help develop our new microservices platform that has real scaling requirements (at 3 years old, the current system is handling multiple million hits a day).
Engineers would be joining a fast-paced environment driving towards the goal of delivering rock-solid software that solve interesting problems to enhance the user's experience, solve back office problems, or new ways to aggregate & analyze data (we have tons of it).
Some of the technologies we work with: Node, Angular, Mongo, Docker (in production! containers are deployed onto our Deis - soon to be Kubernetes - cluster), ElasticSearch, MySQL, Python, R (Data!)
If you're interested, contact andres.galindo at flexshopper.com
FlexShopper is the leading online lease-to-own platform, with the largest LTO marketplace, an LTO payment method for third party sites, and an expanding portfolio of verticals for generating leases online.
FlexShopper is seeking smart, energetic, passionate engineers to join a growing team to help develop our new microservices platform that has real scaling requirements (at 3 years old, the current system is handling multiple million hits a day).
Engineers would be joining a fast-paced environment driving towards the goal of delivering rock-solid software that solve interesting problems to enhance the user's experience, solve back office problems, or new ways to aggregate & analyze data (we have tons of it).
Some of the technologies we work with: Node, Angular, Mongo, Docker (in production! containers are deployed onto our Deis - soon to be Kubernetes - cluster), ElasticSearch, MySQL, Python, R (Data!)
If you're interested, contact andres.galindo at flexshopper.com
It's just an nginx reverse proxy, there is a publicly available version at https://hn.galindo.io (if its somehow abused I'll make it private)
Note: It doesn't allow anything but GET requests and will strip the Cookie header.