8 ms·
It looks nice, but it looks like jenkins is doing way to much and locking you into using it. IMO a build server should only be managing it's triggers (time, ch
by flukus 10y ago
It looks nice, but it looks like jenkins is doing way to much and locking you into using it.
IMO a build server should only be managing it's triggers (time, checkin) and then calling the build script (make or whatever) with the correct parameters for that build configuration. Instead it seems to be trying to take the role of both.
- hunvreus 10y agoWanna see if Pipelines [1] works for you? If not, could you tell me what is missing? [1]: https://github.com/Wiredcraft/pipelines https://github.com/Wiredcraft/pipelines
- kosinus 10y agoI don't know. We tried looking for alternatives when we were a bit down in the gutter with our Jenkins setup, but were even more disappointed with the other options. Instead, we now use Jenkinsfiles everywhere, or pipeline scripts where we have scheduled stuff. That's working well enough so far for our small team. The things Jenkins provides can be difficult to find elsewhere. For example, we spin up an EC2 slave for most builds, but sometimes need to then take the result and deploy it from another (static) node because of network restrictions. Stuff like git access, the credential store, moving stuff between nodes just works everywhere.
- flukus 10y agoDo you have a build script (makefile or something else)? IE, can you perform a build from you're machine?
- kosinus 10y agoMost of our builds are 'basically' Node.js / npm or PHP / composer, so reasonably contained build processes. It looks simple on the surface, but once you start running CI for a while you notice all the dependencies on the environment. Versions installed of PHP, Composer, Node.js, MySQL / MariaDB, Java, Ant all tripped us at some point. (Not to mention we develop on Mac, deploy on Linux.) Instead, we now have a very basic Ubuntu-based AMI with Docker installed, and otherwise stopped depending on the host environment as much as possible. Jenkins spins up an EC2 instance when needed, and shuts it down again after some period of inactivity. 95% of our pipeline scripts do work inside a container.
- arghwhat 10y agoJenkins is by far the worst CI/CD system, except for all the others. Jenkins seem to be the only multi-node job orchestrator that works well enough for a CI/CD workflow, but every time it tries to do something "smart", it seems to fail spectacularly.