StackStorm Solution 3 Master Content Repo PLATFORM Web GUI CLI Chatops CLIENTS Sensor Plugins (inbound integrations) Action Plugins (outbound integrations) INTEGRATIONS .yml REST API Rules Engine Workflow Engine Audit… A M Q P m e s s a g e b u s A M Q P m e s s a g e b u s / / / / {*} IFTTT No N! issue No N! issue Loosely coupled; users abstract automation from integration Loosely coupled; users abstract automation from integration Workflow and rules enable simple scripts to be tied together like Legos. Automate & share pipelines. Workflow and rules enable simple scripts to be tied together like Legos. Automate & share pipelines. Polished – with GUI, ChatOps, CLI, RBAC, error handling, help & more Polished – with GUI, ChatOps, CLI, RBAC, error handling, help & more
What Problems Are We Solving? • Automated Testing (CI) – Integration testing on every commit to all supported versions • Packaging & Shipping (CD) – Distro specific packages on every successful build – Fully automated delivery to all repositories 5
How Is It Built? • GitHub Sensor – GitHub post commit hooks are received by a GitHub sensor • ActionChains – All workflows are written using the sequential workflow runner - ActionChain • ActionTriggers – Workflows are tied together using the trigger that is emitted on completion of an action execution. • Rules – Rules are used to enforce workflow execution preconditions 8
5. End to End Test - Staging 14 Successful completion of the smoke tests, will trigger the full end to end testing suite. This includes all documented examples and deployment scripts.
7. Package & Deploy 16 The release triggers the production packaging workflow. This workflow takes the blessed packages and delivers them to the production repositories.
Why Build It Ourselves? • Eating Our Own Dog Food – Continuous validation of StackStorm as a CI/CD solution • The Ultimate Acceptance Testing • Bragging Rights 17