It all starts with a software delivery machine of your very own. That can be for your team or for you personally–one of each is good.
An Atomist Software Delivery Machine (SDM) provides a high-level interface for you to take action when things happen. In much the same way your continuous integration build kicks off when you push to your repository, Atomist can execute tasks like security scans, documentation publication, release creation, and deployment. Because you’re using a real programming language, not YAML or Bash, and because you have access to a real ecosystem, Node.js, you can create the richest delivery experience you can imagine.
API for Software
The SDM is a persistent process that runs in the background. An SDM links up to the API for software, implemented by the Atomist service, exposing:
- What we know: The Atomist cortex, accessible through GraphQL queries and subscription joins
- What just happened: An event, triggered by a GraphQL subscription, which is contextualized with the existing knowledge
- What you’re working on: A library that enables you to comprehend and manipulate the source code you’re working on.
When a push occurs, the SDM gets all this context and the code. It decides what delivery actions to take, and sets goals accordingly. Instead of a static pipeline, you get to choose the delivery flow for each commit.
A push is not the only event that matters in our software development. The Atomist development automation platform ingests events from your software development systems:
- Source code repositories like GitHub.com and GitHub Enterprise
- Issue tracking systems like GitHub and Jira
- Continuous integration platforms like Travis CI, CircleCI, and Jenkins
- Application frameworks like Spring
- Runtime platforms like Kubernetes and Cloud Foundry
- Custom events from any other system you use
and makes them available via the Atomist API for software.
As Atomist ingests events, typically via webhook JSON payloads, it automatically correlates them to each other: commits to pushes to builds to deployments to running containers. This results in a data model that represents your development flow. The Software Delivery Machine subscribes to the most important events, like a push to source control and a completed build. You can subscribe to more events and take action when they occur, with the data model providing the necessary context so your automations can always do the right thing.
The development automation platform also provides a simple yet powerful interface for implementing custom chat bot commands, also executable from your command line. Atomist provides all the infrastructure needed to recognize commands, collect parameters, execute the code, and respond. This lets you focus on writing your command code, not boilerplate code and ceremony around running bots. Instead of shell scripts that are useful only to you, write commands that help your whole team.
Coding your SDM
Some common setups, such as deliverying and maintaining Spring Boot apps or npm libraries, are provided in extension packs. You can configure the whole pack, or use functions from the pack in your own setup.
Connect your SDM
Atomist maintains two implementations of the API for Software:
- Team mode: a complete, cloud-based service,
- Local mode: an open-source, filesystem-based version that runs on your laptop.
An SDM is most useful when running for your whole team, connected to the Atomist API for software, Slack, and your version control. Run it on your laptop while you’re testing and modifying the SDM, then in your favorite production environment (on-prem or in the cloud) for ongoing use.
If you don’t want to subscribe to the Atomist service and hook up Slack and GitHub/BitBucket/GitLab etc, you’re in luck! Run your SDM in local mode, on your own machine. Receive push events from your own local commits, get messages in a terminal feed, and trigger commands on the command line.
Check the Developer Quick Start for instructions to get started in local mode.