# Step create plugin - quickly generate a new step

**URL:** <https://discuss.bitrise.io/t/step-create-plugin-quickly-generate-a-new-step/1609>\
**Category:** Beta Testing\
**Tags:** bitrise-cli, bitrise-tools\
**Created:** [April 30, 2017, 2:24pm UTC](https://discuss.bitrise.io/t/step-create-plugin-quickly-generate-a-new-step/1609 "2017-04-30T14:24:18Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![viktorbenei](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/viktorbenei/32/18_2.png) [@viktorbenei](https://discuss.bitrise.io/u/viktorbenei)\
**Post date:** [April 30, 2017, 2:24pm UTC](https://discuss.bitrise.io/t/step-create-plugin-quickly-generate-a-new-step/1609/1 "2017-04-30T14:24:18Z")

</div>

_This plugin is still work in progress, but can now be used for creating new steps._

Repo can be found at: [https://github.com/bitrise-core/bitrise-plugins-step](https://github.com/bitrise-core/bitrise-plugins-step)

Right now it implements a step **create** command which should cover everything to get started with Bitrise Step Development.

It’s worth to mention that this plugin will implement other Step related functionality, like list, info, edit, share,…

## How to install / update this plugin?

The plugin is now part of the Bitrise CLI core plugins, so if you have Bitrise CLI 1.6.1 or newer you don’t have to install it (related release announcement: [Monthly release of Bitrise CLI tools and summary of updates (May, 2017) - CLI v1.6.1](http://discuss.bitrise.io/t/monthly-release-of-bitrise-cli-tools-and-summary-of-updates-may-2017-cli-v1-6-1/1690)).

When there’s an update you can install the update with:

```auto
bitrise plugin update step

```

## How to use this plugin?

```auto
bitrise :step ...

```

E.g. to print the plugin’s version:

```auto
bitrise :step version

```

Or to create a new Step:

```auto
bitrise :step create

```

For more info & available commands simply run:

```auto
bitrise :step

```

which will print the plugin’s help.

---

<div class="post-metadata">

**Author:** ![viktorbenei](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/viktorbenei/32/18_2.png) [@viktorbenei](https://discuss.bitrise.io/u/viktorbenei)\
**Post date:** [May 8, 2017, 10:14am UTC](https://discuss.bitrise.io/t/step-create-plugin-quickly-generate-a-new-step/1609/2 "2017-05-08T10:14:02Z")

</div>

Basic `create` command is now ready, and can initialize a Bash based step.

We’re still working on the Go based step support, as well as on a complete experience including `share`. For now Step sharing works the same way as before, by running `bitrise run share-this-step` in the Step’s dir (the `share-this-step` is a workflow in the Step’s bitrise.yml which is auto generated by `create` / part of the step template).

Schedule:

1. The plugin will be added to this month’s Bitrise CLI release as a core plugin, which means it’ll be installed by the CLI automatically, you won’t have to install it yourself.
2. We’ll try to finish the base Bash & Go step create & share experience this week, and will be published as a plugin update, which you’ll be able to install with a simple `bitrise plugin update step` after the CLI release tomorrow.

---

<div class="post-metadata">

**Author:** ![viktorbenei](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/viktorbenei/32/18_2.png) [@viktorbenei](https://discuss.bitrise.io/u/viktorbenei)\
**Post date:** [May 14, 2017, 8:00am UTC](https://discuss.bitrise.io/t/step-create-plugin-quickly-generate-a-new-step/1609/3 "2017-05-14T08:00:48Z")

</div>

The `step` plugin is now part of the Bitrise CLI core plugins since [v1.6.0](https://github.com/bitrise-io/bitrise/releases/tag/1.6.0).

If you have that or a newer Bitrise CLI you no longer have to install the `step` plugin manually, you can simply use the plugin with:

```auto
bitrise :step

```

E.g. to create a new step:

```auto
bitrise :step create

```

---

<div class="post-metadata">

**Author:** ![viktorbenei](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/viktorbenei/32/18_2.png) [@viktorbenei](https://discuss.bitrise.io/u/viktorbenei)\
**Post date:** [May 14, 2017, 10:24am UTC](https://discuss.bitrise.io/t/step-create-plugin-quickly-generate-a-new-step/1609/4 "2017-05-14T10:24:59Z")

</div>

New version (0.9.2) was released, with toolkit selection. It’s now possible to generate both Bash and Go toolkit steps with the plugin.

---

<div class="post-metadata">

**Author:** ![viktorbenei](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/viktorbenei/32/18_2.png) [@viktorbenei](https://discuss.bitrise.io/u/viktorbenei)\
**Post date:** [May 14, 2017, 3:30pm UTC](https://discuss.bitrise.io/t/step-create-plugin-quickly-generate-a-new-step/1609/5 "2017-05-14T15:30:23Z")

</div>

v0.9.3 was just released: it can now auto-fill the website and other URL properties in the `step.yml`, as well as auto detect the Go package name from that.

With this all the basic functionality is now available for both Bash and Go toolkit based steps, and the generated step should be in “ready to share” state right after the (successful) generation 🚀

---

<div class="post-metadata">

**Author:** ![joergbirkhold](https://avatars.discourse-cdn.com/v4/letter/j/aca169/32.png) [@joergbirkhold](https://discuss.bitrise.io/u/joergbirkhold)\
**Post date:** [April 18, 2019, 2:24pm UTC](https://discuss.bitrise.io/t/step-create-plugin-quickly-generate-a-new-step/1609/6 "2019-04-18T14:24:29Z")

</div>

Hi  
for me the plugin fails on MacOS 10.2:  
ERROR: Failed to write template into file: Failed to evaluate template: Failed to find templates dir/box: could not locate box “templates”  
Thanks for any help  
Jörg

---

<div class="post-metadata">

**Author:** ![bitce](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/bitce/32/1639_2.png) [@bitce](https://discuss.bitrise.io/u/bitce)\
**Post date:** [April 23, 2019, 10:23am UTC](https://discuss.bitrise.io/t/step-create-plugin-quickly-generate-a-new-step/1609/7 "2019-04-23T10:23:32Z")

</div>

Hi @joergbirkhold, sorry to hear about that! Can you please either contact us on our on-site chat with this or post your full terminal output in a separate #issues thread?
