Wercker Glossary

Box - The box section in the wercker.yml file defines the base Docker image to build a Pipeline from. It could contain language interpreters and tooling required for pipelines.

Entrypoint - A feature in Docker that enables it to specify the executable to be run.

Environment variables - Used to set some global settings that should apply to everything under an organization (such as an SSH key), to fetch private GitHub repositories. Keep in mind that public projects under the organization will also have access to these variables.

Hooks - Define how pipelines get triggered. By default, pipelines will listen for other pipelines to finish. Alternatively, you can assign a Git hook to the pipeline to make it trigger on Git changes.

Organization - Through organizations, you can create and organize teams to make access management for applications much easier and more efficient.

Owners team - The owners team is responsible for the applications, people, teams and access management of an organization.

Pipelines - The pipeline is the heart and soul of Wercker. It’s where you define the actions (steps) and environment for your tasks. It's also often where you define your tests, builds and deploys. They are an aggregate of steps and will pass or fail based on the steps within.

Run.sh - This file contains the entrypoint for your step logic. This should be Bash code in the run.sh file itself. If you want to create a more complex application in a different language, call this from within the run.sh file.

Services - Separate containers that are spun up alongside your Pipelines. They can be used for things such as running a testing database or message queue. You specify service containers in your wercker.yml file through the services section.

SSH keys - Wercker allows you to generate SSH keys and expose them as environment variables to your build or deployment pipeline.

Stack - A complete environment that runs your pipelines, including the operating system and container technology.

Steps - Self-contained Bash scripts or compiled binaries for accomplishing specific automation tasks, defined in the wercker.yml file of your application. Steps can be written manually or borrowed from the community via the Steps Registry.

Step Registry - A marketplace of steps created by the Wercker community. All steps are currently public and free for all users to incorporate into their pipelines.

Virtual Private Pipelines - Wercker VPP is a single-tenant, SaaS-delivered, Docker-native CI/CD automation platform. It is fully managed and scalable and is ideally suited to cloud-native development (although it also supports other types of deployments).

Walterbot - A chatbot in Wercker that sends automatic updates to Slack and allows you to take action directly from inside Slack.

Wercker.yml - The configuration file and format for your pipelines.

Wercker cache - A cache directory that is shared between Pipelines in your Workflows.

Workflows - Workflows provide you with a mechanism for managing your Pipelines. With Workflows, you can connect your Pipelines in series and parallel to form complex, end-to-end CI/CD flows that can take your applications from source to production.