Skip to content

Glossary

Atomist

  1. the company that produces this spectacular glossary.
  2. a development automation platform, consisting of a service, a framework, and libraries to help you automate your software delivery, your way.

Atomist service

the part of the Atomist platform that is operated by Atomist the company: the event hub, GraphQL endpoint, and web interface. [more info][architecture]

PushRule

a specification for goals to set on a given push. more info

PushTest

a function that decides whether a particular push is relevant. It can look at the code and return a boolean. more info

autofix

a code transform that is applied every push. more info

automations

in general, an automation is anything that a program does so that you don’t have to. In this guide, an automation is something that Atomist runs for you. You can create automations (functions) and then have Atomist run them when events happen or on demand.

inside a chat channel, you can link a repository to that channel. The Atomist bot will then send messages about that repository to the channel. more info

code inspection

like an of automated code review; a function that looks at the code in a project and produces comments. Atomist can run them after every push. more info

code transform

a function that operates on a project, changing the code inside it. more info

code transform

an automated code change. Write a function to change code, and apply it to one project or many projects, or after every commit. more info

command

this is a thing that the Atomist bot (in team mode) or command line (in local mode) knows how to do. Each command has a phrase that triggers it, called an intent. As a person, send that intent to the @atomist bot in chat or to the atomist command line in the terminal. As an SDM developer, register new commands to teach Atomist how to respond to these.

command line utility (CLI)

(or “atomist command line”) a program that you install on your computer in order to run an SDM. It also does various other atomist-related things, especially in local mode. more info

command registration

defines an intent and an implementation for a new command in an SDM. more info

community Slack

this Slack workspace is free for everyone to join. Here, you can see Atomist in action on our own open source projects. Ask us questions and discuss what you’d like to do or see with Atomist.

cortex

a database where Atomist stores correlated events

dashboard

better known as the Atomist web interface, this lives at app.atomist.com, and it gives you access to some notifications and the settings for your Atomist workspace. more info

delivery

in this guide, delivery is about moving new code into production, through each of the fixes, checks, builds, publishments, deployments, and approvals that are necessary in your organization.

development automation

programs that make the work of software development smoother. This includes delivery automation: getting new code through all its checkpoints and into production. Other examples include project creation, [issue creation](../user/lifecycle.md, and code maintenance.

durable

when an SDM is configured as durable, then when it is no longer connected, the Atomist event hub will queue events for it until it comes back up. more info

extension pack

a collection of integrations or useful functions that can be added to an SDM. more info

feed

(or “atomist feed” or “SDM feed”) a place for a local-mode SDM to send you messages and updates, since it does not have access to chat. more info

fingerprint

a distilled piece of important information about the code at a particular time. They can be compared to notice when a change is significant in a particular way. more info

generator

a particular kind of command that creates a new project. It starts from a seed, runs some code transforms, and puts the result in a new repository.

goal approval

goals can pause the work on a particular delivery flow, pending a human telling them to proceed. A button appears on the push notification in chat.

goal preconditions

one goal can wait for another goal (or goals) to complete before starting. more info

goals

steps to execute after a push. These are set by a software delivery machine. more info

intent

(or “command intent”) the phrase to type to trigger a command

lifecycle

in general, lifecycle means the stages in any process. In this guide, we talk about automations triggered in different parts of the software development lifecycle. Lifecycle messages are the built-in notifications that the Atomist bot sends to chat to describe issue, pull request, issue comment, and push events (along with build, goal, and other events correlated with the push). more info

listener

the SDM framework lets you register listeners to various useful events. check the whole list

local mode

when an SDM runs on your laptop, working only on code that’s on your laptop, sending messages only to your laptop. more info

project

in this guide, “project” refers to a git repository with code in it.

project owner

a grouping above projects. Projects are repositories, and they each belong to someone. On GitHub, the owner is a user or an organization. On BitBucket, the owner is a user or a BitBucket project.

projects directory

(or “Atomist projects directory”) this is a directory on your computer where local-mode SDMs will look for projects to work on. It defaults to $HOME/atomist/projects more info

push event

the most important event in delivery automation, a push represents new code arriving in a repository. Normally (in team mode) this is triggered when someone pushes commits to the central version control repository. In local mode, a push event is triggered on a commit.

push impact

a function that reacts to a change in code. It can do anything: send a message to chat, for instance. more info

push notification

the message that atomist bot sends to chat after each push event. It gets updated to include information about builds, goal, tags, deployments, and more. more info

registration

an object that provides instructions to an SDM or a goal. A registration includes a name (for diagnostics), and some specific action (a transform, an inspection, or a listener, depending on the built-in goal). Many registrations also include an optional PushTest, narrowing on particular pushes.

seed

the starting point for a generator. A seed is a real project that serves as a model for new projects.

skills

another name for commands. Skills are things Atomist knows how to do.

software delivery machine (SDM)

a program that you run, which connects to the atomist service (in team mode) for triggering and chat integration. Your SDM runs your software delivery flow and other development automations.

target

(as in “target repository” or “target owner”) when you run a generator, this is where Atomist will put the new project. See project and project owner

team

in this guide, your team includes all the other people at your company who might interact with Atomist.

team mode

an SDM running in team mode connects to the Atomist service. It might run on your laptop or in a production environment within your network. more info

version control

in this guide, “version control” refers to the place where you push code to share it with your team like GitHub, GitLab, or BitBucket. Everyone uses git locally, right? (I know, not everyone does, but everyone who uses Atomist has to.)

web interface

the Atomist web interface lives at app.atomist.com, and it gives you access to some notifications and the settings for your Atomist workspace. more info

workspace

many services have a concept of “workspace,” and Atomist is one of them. An Atomist workspace represents your organization’s account with Atomist.