Styleguide

Stepline

Description

The stepline component renders a specialized "stepline" based on data housed in the stepline yaml file (see: `src/_data/stepline`). It takes few inputs, relying on the data file to generate most of it's content.

Default Stepline

Rendered

This is a header

This is a subheader

step 1 Get an overview of the new .circleci/config.yml format

Start by familiarizing yourself with the new file format. Watch this video, or check out the docs.

step 2 Get a list of the projects still building on 1.0

Use this script to see which projects are building on CircleCI 1.0. Stop building any inactive projects you don’t plan to migrate.

step 3 Create a new branch on your projects for getting 2.0 up and running

You can get your projects building on CircleCI 2.0 without impacting your team. Create a new branch for testing so your team can keep building while you get things set up.

step 4 Use the configuration translator to jump-start your migration

The configuration translation endpoint will help you get started with your config file. You will want to tweak the output, but it should help you get started.

step 5 Use the CLI to validate your 2.0 configuration (and avoid stacking up failed builds)

You can use the command line interface to validate your config changes with a pre-commit Git hook. This will help you avoid running a bunch of failed builds while you are fine-tuning your syntax. Read how in the docs or watch this video.

success
Congratulations!

Your jobs are passing, congratulations! Now you can have some fun.

Share your success. Let your team know about the changes you made to your CircleCI config in a demo. Your projects will likely be building faster, and with more flexibility.

Options

classes : string

tag : string
Defines the tag name to apply as a filter to the stepline data. This input is required.

Default Stepline

Code

{% include components/stepline.html header="This is a header" subheader="This is a subheader" tag="eol" %}

Rendered

This is a header

This is a subheader

step 1 Get an overview of the new .circleci/config.yml format

Start by familiarizing yourself with the new file format. Watch this video, or check out the docs.

step 2 Get a list of the projects still building on 1.0

Use this script to see which projects are building on CircleCI 1.0. Stop building any inactive projects you don’t plan to migrate.

step 3 Create a new branch on your projects for getting 2.0 up and running

You can get your projects building on CircleCI 2.0 without impacting your team. Create a new branch for testing so your team can keep building while you get things set up.

step 4 Use the configuration translator to jump-start your migration

The configuration translation endpoint will help you get started with your config file. You will want to tweak the output, but it should help you get started.

step 5 Use the CLI to validate your 2.0 configuration (and avoid stacking up failed builds)

You can use the command line interface to validate your config changes with a pre-commit Git hook. This will help you avoid running a bunch of failed builds while you are fine-tuning your syntax. Read how in the docs or watch this video.

success
Congratulations!

Your jobs are passing, congratulations! Now you can have some fun.

Share your success. Let your team know about the changes you made to your CircleCI config in a demo. Your projects will likely be building faster, and with more flexibility.