4 ms·

Another downside to Jenkins: $200/hr to learn other products do it just as well with much less overhead.

emmelaich 9y ago
I think $200/h is a low-end average estimate for any type of enterprisey software, open source or not. If you don't buy expertise in the short term, it may cost you a lot more in the long run.
- mooreds 9y ago
  $200/hr sounds expensive until you realize you are gaining access to all the mistakes they've made on someone else's dime.
  - closeparen 9y ago
    Consultants are long gone by the time their mistakes are apparent.
oblio 9y ago
That was actually a joke since I've never done any Jenkins consulting but Jenkins, including the setup cost is waaaay cheaper than other solutions I've seen for what I used it for: distributed cron, queuing system for tasks, higher level dashboard for managers, CI server, etc.
- piva00 9y ago
  I could tell it was a joke when you mentioned keeping backups of your main configuration instead of porting ALL of your Jenkins config to code and maintaining that in version control. At my current job I started as a SRE for the team supporting Jenkins and other CI/CD tools for the rest of engineering (around 50+ other teams), I moved back to a SWE position but as an insight: don't run a single master Jenkins for all of your teams, make it federated (per-team/project or whatever suits your organisational structure) AND do all of Jenkins' configuration through scripts. Never rely on backing up the old configuration (problematic in cases of rollback to previous Jenkins versions, brittle for recovery), just start it fresh every time you need to recover and re-run your provisioning scripts, that also includes NEVER maintaining jobs through the UI, only through JobDSL, JJB or Pipeline scripts.
  - oblio 9y ago
    You need the team you're part of to have enough discipline for that. Not always the case. Sometimes you need to know when to cut your losses and go for the cheap, plastic, solution (i.e. backups).
voidr 9y ago
That's just the poster's consulting price, you can learn everything for free online.

I think $200/h is a low-end average estimate for any type of enterprisey software, open source or not. If you don't buy expertise in the short term, it may cost you a lot more in the long run.

mooreds 9y ago
$200/hr sounds expensive until you realize you are gaining access to all the mistakes they've made on someone else's dime.
- closeparen 9y ago
  Consultants are long gone by the time their mistakes are apparent.

oblio 9y ago

That was actually a joke since I've never done any Jenkins consulting but Jenkins, including the setup cost is waaaay cheaper than other solutions I've seen for what I used it for: distributed cron, queuing system for tasks, higher level dashboard for managers, CI server, etc.

piva00 9y ago
I could tell it was a joke when you mentioned keeping backups of your main configuration instead of porting ALL of your Jenkins config to code and maintaining that in version control. At my current job I started as a SRE for the team supporting Jenkins and other CI/CD tools for the rest of engineering (around 50+ other teams), I moved back to a SWE position but as an insight: don't run a single master Jenkins for all of your teams, make it federated (per-team/project or whatever suits your organisational structure) AND do all of Jenkins' configuration through scripts. Never rely on backing up the old configuration (problematic in cases of rollback to previous Jenkins versions, brittle for recovery), just start it fresh every time you need to recover and re-run your provisioning scripts, that also includes NEVER maintaining jobs through the UI, only through JobDSL, JJB or Pipeline scripts.
- oblio 9y ago
  You need the team you're part of to have enough discipline for that. Not always the case. Sometimes you need to know when to cut your losses and go for the cheap, plastic, solution (i.e. backups).

voidr 9y ago

That's just the poster's consulting price, you can learn everything for free online.