3 ms·

CI sucks... in big companies it sucks more. The unruly XML configs are a small part of the problem. Taking two days though? Fire the engineer(s) behind the ini

CI sucks... in big companies it sucks more. The unruly XML configs are a small part of the problem. Taking two days though? Fire the engineer(s) behind the initiative. (I assume this is a one-sided sales pitch though.) You guys have clearly hired a baller good UX/UI person and have an amazing roster of clients. Wish you all the success in the world!

pbiggar 13y ago
Two days actually makes sense. Let's say you already have a machine, and haven't set up jenkins before. You need to install ubuntu, install jenkins, and then start to configure and figure it out as you go. Its not use friendly, so I would expect this to take most of the day. That's without installing the databases, queues, etc, that you need. In all likelyhood, you wont have this in chef (your production box doesn't run postgres or redis or rabbit), so you're going from scratch. All it takes is one pesky configuration thing you can't figure out to have it take your entire day. And heaven forbid if you haven't got a few years of linux admining under your belt already, in which case you can write off the rest of the week.
- josephlord 13y ago
  And don't forget to document it so that it is repeatable and then cleanup the documentation when you are done with all the configs that didn't work.
  - qznc 13y ago
    Shouldn't there be a reusable Ansible-Docker thingy somewhere?
- UK-AL 13y ago
  It's not configuring jenkins that's the problem. It's all scripts it requires, build, testing, packing, deployment scripts and whatever else you want to automate. In general trying to automate things, brings all the workflow problems out to forefront to be fixed. It makes thinking clearer.
- npongratz 13y ago
  Depending on your needs, Bitnami [0] and TurnKey Linux [1] offer preconfigured batteries-included VMs (among other options) that might lower the barrier to entry. (I'm not affiliated with either, but have enjoyed using Bitnami's stacks.) In particular, I have found Bitnami's Jenkins stack to be helpful for quickly spinning up a prototype and focusing on Jenkins rather than than installing+configuring databases and other stuff. I think it took me about an hour to be up and running with Bitnami's Jenkins VM, including download and provisioning time. It then took me quite a bit longer to coax Jenkins into building my stuff correctly. Installing and configuring databases and other subsystems may eventually be necessary depending on scale. For my prototyping and learning needs, I've greatly benefited by working with self-contained VMs like Bitnami's. It's an option to consider, at least. [0] http://bitnami.com/stack/jenkins http://bitnami.com/stack/jenkins [1] http://www.turnkeylinux.org/jenkins http://www.turnkeylinux.org/jenkins
UK-AL 13y ago
"CI sucks... in big companies it sucks more. The unruly XML configs are a small part of the problem." That has nothing to do with CI. CI is a workflow, not an implementation.

pbiggar 13y ago

Two days actually makes sense. Let's say you already have a machine, and haven't set up jenkins before. You need to install ubuntu, install jenkins, and then start to configure and figure it out as you go. Its not use friendly, so I would expect this to take most of the day. That's without installing the databases, queues, etc, that you need. In all likelyhood, you wont have this in chef (your production box doesn't run postgres or redis or rabbit), so you're going from scratch. All it takes is one pesky configuration thing you can't figure out to have it take your entire day. And heaven forbid if you haven't got a few years of linux admining under your belt already, in which case you can write off the rest of the week.

josephlord 13y ago
And don't forget to document it so that it is repeatable and then cleanup the documentation when you are done with all the configs that didn't work.
- qznc 13y ago
  Shouldn't there be a reusable Ansible-Docker thingy somewhere?
UK-AL 13y ago
It's not configuring jenkins that's the problem. It's all scripts it requires, build, testing, packing, deployment scripts and whatever else you want to automate. In general trying to automate things, brings all the workflow problems out to forefront to be fixed. It makes thinking clearer.
npongratz 13y ago
Depending on your needs, Bitnami [0] and TurnKey Linux [1] offer preconfigured batteries-included VMs (among other options) that might lower the barrier to entry. (I'm not affiliated with either, but have enjoyed using Bitnami's stacks.) In particular, I have found Bitnami's Jenkins stack to be helpful for quickly spinning up a prototype and focusing on Jenkins rather than than installing+configuring databases and other stuff. I think it took me about an hour to be up and running with Bitnami's Jenkins VM, including download and provisioning time. It then took me quite a bit longer to coax Jenkins into building my stuff correctly. Installing and configuring databases and other subsystems may eventually be necessary depending on scale. For my prototyping and learning needs, I've greatly benefited by working with self-contained VMs like Bitnami's. It's an option to consider, at least. [0] http://bitnami.com/stack/jenkins http://bitnami.com/stack/jenkins [1] http://www.turnkeylinux.org/jenkins http://www.turnkeylinux.org/jenkins

UK-AL 13y ago

"CI sucks... in big companies it sucks more. The unruly XML configs are a small part of the problem." That has nothing to do with CI. CI is a workflow, not an implementation.