6 ms·

at a glance... seems nearly identical to OpsWorks. am i right? why would i use one or the other? that said, and maybe i can answer my own question... OpsWorks

at a glance... seems nearly identical to OpsWorks. am i right? why would i use one or the other? that said, and maybe i can answer my own question... OpsWorks has been a grand pain in the ass, so new options even built on AWS come welcome.

yeukhon 11y ago
My reading is that this project aims to do more than just OpsWork. It basically manages your deployment and release cycle, including releasing your infrastructure changes, if you make it so. You can basically do all of this in Jenkins today, but you don't have the fancy GUI, that's my impression so far. http://spinnaker.io/online_docs/overview/overview.html http://spinnaker.io/online_docs/overview/overview.html
- daviddumenil 11y ago
  A replacement for Jenkins as the CI Pipeline management tool is my understanding. It now makes sense why they stepped away from the Job DSL Jenkins plugin that they helped create a while back (though there's still support for Jenkins steps in there which'll be a great help with porting existing pipelines).
  - stuff4ben 11y ago
    JobDSL was more along the lines of a templating engine with groovy customization that tends to break Jenkins masters. The Workflow plugin would be more akin to Spinnaker than JobDSL.
    - daviddumenil 11y ago
      I'm not saying it's a like for like replacement, I'm saying they stopped working on JobDSL because they were working on Spinnaker. This feels like a Jenkins replacement rather than a Jenkins plugin replacement or at least something that sits atop Jenkins in driving your build and deployment activities (it's got support to call and watch Jenkins jobs so it's sensible to assume they use both). I'm interested to hear that JobDSL is painful for Jenkins masters do you know what the pain points are?
      - stuff4ben 11y ago
        >I'm interested to hear that JobDSL is painful for Jenkins masters do you know what the pain points are? In a multi-tenant environment that we run using Enterprise Jenkins from CloudBees, the default option for JobDSL is to create jobs at the root level which is problematic if you don't allow teams at that level. We've also had issues with jobs just getting "stuck" which even after a restart of the master doesn't clear it out. Plus the fact that it encourages bad behavior among teams by allowing them to create thousands of jobs that never get cleaned up is just another reason we've banned it from other installations we've setup. Jenkins itself is pretty terrible and even the proposed 2.0 changes don't appear to do anything to change things for the better. If Spinnaker can replace Jenkins, more power to them. But I don't think that's the initial aim. Regarding your other comment about "something that sits atop Jenkins in driving your build and deployment activities" that's just about exactly what the Workflow plugin ecosystem does. However you're still stuck with Jenkins and its baggage.
      - bmoyles 11y ago
        JobDSL came from an engineer who collaborated with some others at a conference. It's not anything we own or drive the development of. It's used in some places internally but is not pervasive. The Spinnaker guys were not responsible for JobDSL, totally unrelated.
- catshirt 11y ago
  yeah sorry, perhaps i was too broad. not OpsWorks specifically, but i'm wondering if it provides anything AWS services in general don't provide. like CodePipeline/CodeDeploy. think i just need to read a bit more or try it out.
- cfieber 11y ago
  Spinnaker is pretty focussed on deployments and as such has those operations as first class citizens (deploy, resize, manage traffic, destroy, etc) Jenkins is also a first class stage type - it is the way we run the build and test side of our deployments

yeukhon 11y ago

My reading is that this project aims to do more than just OpsWork. It basically manages your deployment and release cycle, including releasing your infrastructure changes, if you make it so. You can basically do all of this in Jenkins today, but you don't have the fancy GUI, that's my impression so far. http://spinnaker.io/online_docs/overview/overview.html http://spinnaker.io/online_docs/overview/overview.html

daviddumenil 11y ago
A replacement for Jenkins as the CI Pipeline management tool is my understanding. It now makes sense why they stepped away from the Job DSL Jenkins plugin that they helped create a while back (though there's still support for Jenkins steps in there which'll be a great help with porting existing pipelines).
- stuff4ben 11y ago
  JobDSL was more along the lines of a templating engine with groovy customization that tends to break Jenkins masters. The Workflow plugin would be more akin to Spinnaker than JobDSL.
  - daviddumenil 11y ago
    I'm not saying it's a like for like replacement, I'm saying they stopped working on JobDSL because they were working on Spinnaker. This feels like a Jenkins replacement rather than a Jenkins plugin replacement or at least something that sits atop Jenkins in driving your build and deployment activities (it's got support to call and watch Jenkins jobs so it's sensible to assume they use both). I'm interested to hear that JobDSL is painful for Jenkins masters do you know what the pain points are?
    - stuff4ben 11y ago
      >I'm interested to hear that JobDSL is painful for Jenkins masters do you know what the pain points are? In a multi-tenant environment that we run using Enterprise Jenkins from CloudBees, the default option for JobDSL is to create jobs at the root level which is problematic if you don't allow teams at that level. We've also had issues with jobs just getting "stuck" which even after a restart of the master doesn't clear it out. Plus the fact that it encourages bad behavior among teams by allowing them to create thousands of jobs that never get cleaned up is just another reason we've banned it from other installations we've setup. Jenkins itself is pretty terrible and even the proposed 2.0 changes don't appear to do anything to change things for the better. If Spinnaker can replace Jenkins, more power to them. But I don't think that's the initial aim. Regarding your other comment about "something that sits atop Jenkins in driving your build and deployment activities" that's just about exactly what the Workflow plugin ecosystem does. However you're still stuck with Jenkins and its baggage.
    - bmoyles 11y ago
      JobDSL came from an engineer who collaborated with some others at a conference. It's not anything we own or drive the development of. It's used in some places internally but is not pervasive. The Spinnaker guys were not responsible for JobDSL, totally unrelated.
catshirt 11y ago
yeah sorry, perhaps i was too broad. not OpsWorks specifically, but i'm wondering if it provides anything AWS services in general don't provide. like CodePipeline/CodeDeploy. think i just need to read a bit more or try it out.
cfieber 11y ago
Spinnaker is pretty focussed on deployments and as such has those operations as first class citizens (deploy, resize, manage traffic, destroy, etc) Jenkins is also a first class stage type - it is the way we run the build and test side of our deployments