# Workflow Editor "v2" (Open Source & Offline Workflow Editor) **URL:** \ **Category:** Beta Testing\ **Tags:** bitrise-cli, bitrise-tools\ **Created:** [December 30, 2016, 10:57am UTC](https://discuss.bitrise.io/t/workflow-editor-v2-open-source-offline-workflow-editor/39 "2016-12-30T10:57:37Z")\ **Posts on this page:** 17\ **Page:** 1
**Author:** ![erosdome](https://avatars.discourse-cdn.com/v4/letter/e/9fc348/32.png) [@erosdome](https://discuss.bitrise.io/u/erosdome)\ **Post date:** [December 30, 2016, 10:57am UTC](https://discuss.bitrise.io/t/workflow-editor-v2-open-source-offline-workflow-editor/39/1 "2016-12-30T10:57:37Z")
We’re working on a complete revision of the Workflow Editor. The new editor is built in a way that you’ll be able to run it **“offline”** , on your own Mac/PC, without signing in to [bitrise.io](https://www.bitrise.io) - just like our [CLI](https://github.com/bitrise-io/bitrise) - as well as on [bitrise.io](https://www.bitrise.io), providing a unified editor for every use case! It’s also completely open source, of course 😉 The repository can be found here: [GitHub - bitrise-io/bitrise-workflow-editor: Bitrise Workflow Editor](https://github.com/bitrise-io/bitrise-workflow-editor) Overall look & feel: ![](https://us1.discourse-cdn.com/flex016/uploads/bitrise/original/1X/566274a5b44084606a7687f2a75f20ca4a8bd0b7.png) **IMPORTANT: the Workflow Editor plugin requires [Bitrise CLI 1.5.4](https://github.com/bitrise-io/bitrise/releases/tag/1.5.4) or newer!** ## How to test the latest beta release: _First of all, make sure that you have the Bitrise CLI installed, [v1.5.4](https://github.com/bitrise-io/bitrise/releases/tag/1.5.4) or newer required! ([Bitrise CLI v1.5.4 installation instructions](https://github.com/bitrise-io/bitrise/releases/tag/1.5.4))._ _Once installed, run `bitrise version` to test the version of the CLI. If it prints `1.5.4` you’re ready to use the Workflow Editor plugin!_ The Workflow Editor plugin now ships as part of the Bitrise CLI, so you no longer have to install the plugin yourself. If you have at least Bitrise CLI v.1.5.4 you can start to use the `workflow-editor` right away! _Note: if you just installed the CLI and you did not run any other command with it, you might have to run `bitrise setup` to ensure that all core plugins are available and are the right versions. If you did any `bitrise run ..` after the CLI install then `bitrise setup` is not required, as it’s done automatically when the CLI detects that it was not yet performed for the current version._ To upgrade the already installed plugin to the latest version: ```auto bitrise plugin update workflow-editor ``` That’s all, you’re ready to go! To run the workflow editor: ```auto cd /path/to/my/project bitrise :workflow-editor ``` ## How to test the latest development version: 1. Go to [GitHub - bitrise-io/bitrise-workflow-editor: Bitrise Workflow Editor](https://github.com/bitrise-io/bitrise-workflow-editor) 2. Clone the master branch to `$GOPATH/src/github.com/bitrise-io/bitrise-workflow-editor` 3. Run `bitrise run go-install` 4. Navigate to your project path where the **bitrise.yml** is stored 5. Run `bitrise-workflow-editor` ## Release Schedule First versions are released both for the Bitrise CLI as a default plugin, and on [bitrise.io](https://www.bitrise.io), so you can enjoy using the new editor everywhere! 😉 ## Bug report: If you stumble upon any bugs, please report them to us at [GitHub · Where software is built](https://github.com/bitrise-io/bitrise-workflow-editor/issues) ---
**Author:** ![godreikrisztian](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/godreikrisztian/32/22_2.png) [@godreikrisztian](https://discuss.bitrise.io/u/godreikrisztian)\ **Post date:** [January 31, 2017, 10:57am UTC](https://discuss.bitrise.io/t/workflow-editor-v2-open-source-offline-workflow-editor/39/2 "2017-01-31T10:57:23Z")
We just released the first beta version of the Workflow Editor. 🛠 See the install instructions on the [github release page](https://github.com/bitrise-io/bitrise-workflow-editor/releases/tag/0.9.0). ---
**Author:** ![erosdome](https://avatars.discourse-cdn.com/v4/letter/e/9fc348/32.png) [@erosdome](https://discuss.bitrise.io/u/erosdome)\ **Post date:** [February 3, 2017, 3:48pm UTC](https://discuss.bitrise.io/t/workflow-editor-v2-open-source-offline-workflow-editor/39/3 "2017-02-03T15:48:04Z")
v0.9.1 (beta) released: - CLI package changed from urfave CLI to Cobra CLI - Multiple step library support added - App env vars section not displayed if config YML does not contain `app` or `envs` key - fixed ---
**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:** [February 15, 2017, 11:52am UTC](https://discuss.bitrise.io/t/workflow-editor-v2-open-source-offline-workflow-editor/39/4 "2017-02-15T11:52:10Z")
The current beta of the workflow editor (v0.9.3) is now part of the latest Bitrise CLI release (v1.5.4), which means that you no longer need to install the plugin manually! If you install the Bitrise CLI 1.5.4 or newer you can start to use the workflow-editor right away! > [@Monthly release of Bitrise CLI tools and summary of updates (Feb, 2017)](http://discuss.bitrise.io/t/monthly-release-of-bitrise-cli-tools-and-summary-of-updates-feb-2017/763): > > We ship a new bitrise cli version on the second Tuesday of every month. The new release will be available on the [bitrise.io](https://www.bitrise.io) virtual machines on the weekend after the CLI release, unless we discover any serious bug / regression. Read on to learn more about this month’s [Bitrise CLI](https://github.com/bitrise-io/bitrise) release and about the changes around bitrise tools and steps. New version of Bitrise CLI ([1.5.4](https://github.com/bitrise-io/bitrise/releases/tag/1.5.4)) To allow bitrise-cli to use [stepman](https://github.com/bitrise-io/stepman)’s new features we updated the required minimal stepman version to [0.9.28](https://github.com/bitrise-io/stepman/releases/tag/0.9.28). The… When updates are available for the workflow editor, you’ll get notified when you start the editor, and you can update the editor with: `bitrise plugin update workflow-editor` ---
**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:** [February 15, 2017, 2:45pm UTC](https://discuss.bitrise.io/t/workflow-editor-v2-open-source-offline-workflow-editor/39/5 "2017-02-15T14:45:36Z")
Workflow editor v0.9.4 release: > [@Offline Workflow Editor / Workflow Editor v2 v0.9.4 released](http://discuss.bitrise.io/t/offline-workflow-editor-workflow-editor-v2-v0-9-4-released/803): > > Changelog: Step delete bug fixed ([https://github.com/bitrise-io/bitrise-workflow-editor/issues/55](https://github.com/bitrise-io/bitrise-workflow-editor/issues/55)) Ctrl+S / Cmd+S hotkey for save added Workflow selector dropdown scroll issue fixed ([https://github.com/bitrise-io/bitrise-workflow-editor/issues/50](https://github.com/bitrise-io/bitrise-workflow-editor/issues/50)) Step versions are now in descending order ([https://github.com/bitrise-io/bitrise-workflow-editor/issues/52](https://github.com/bitrise-io/bitrise-workflow-editor/issues/52)) For more information about the new Workflow Editor (beta) and how to install it, visit: [http://discuss.bitrise.io/t/offline-workflow-editor…](http://discuss.bitrise.io/t/offline-workflow-editor-workflow-editor-v2/39) ---
**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:** [February 16, 2017, 2:10pm UTC](https://discuss.bitrise.io/t/workflow-editor-v2-open-source-offline-workflow-editor/39/6 "2017-02-16T14:10:19Z")
v0.9.5: > [@Offline Workflow Editor / Workflow Editor v2 v0.9.5 released](http://discuss.bitrise.io/t/offline-workflow-editor-workflow-editor-v2-v0-9-5-released/819): > > Changelog: Selected workflow, selected trigger type stored in URL ([https://github.com/bitrise-io/bitrise-workflow-editor/issues/60](https://github.com/bitrise-io/bitrise-workflow-editor/issues/60)) Last selected tab, workflow, trigger type stored in cookie Ctrl+S key command now working on Linux ([https://github.com/bitrise-io/bitrise-workflow-editor/issues/59](https://github.com/bitrise-io/bitrise-workflow-editor/issues/59)) Bug when leaving triggers tab and save prompt showing incorrectly fixed ([https://github.com/bitrise-io/bitrise-workflow-editor/issues/58](https://github.com/bitrise-io/bitrise-workflow-editor/issues/58)) Step ordering bug fixed ([https://github.com/bitrise-io/bitrise-…](https://github.com/bitrise-io/bitrise-workflow-editor/issues/57) ---
**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:** [February 20, 2017, 12:18pm UTC](https://discuss.bitrise.io/t/workflow-editor-v2-open-source-offline-workflow-editor/39/7 "2017-02-20T12:18:08Z")
v0.9.6: > [@Offline Workflow Editor / Workflow Editor v2 v0.9.6 released](http://discuss.bitrise.io/t/offline-workflow-editor-workflow-editor-v2-v0-9-6-released/853): > > Changelog: Open Sans set as default font for editor Change added step bug fixed ([https://github.com/bitrise-io/bitrise-workflow-editor/issues/63](https://github.com/bitrise-io/bitrise-workflow-editor/issues/63)) For more information about the new Workflow Editor (beta) and how to install it, visit: [http://discuss.bitrise.io/t/offline-workflow-editor-workflow-editor-v2/39](http://discuss.bitrise.io/t/offline-workflow-editor-workflow-editor-v2/39) ---
**Author:** ![david.everlof.knowit](https://avatars.discourse-cdn.com/v4/letter/d/278dde/32.png) [@david.everlof.knowit](https://discuss.bitrise.io/u/david.everlof.knowit)\ **Post date:** [February 20, 2017, 4:10pm UTC](https://discuss.bitrise.io/t/workflow-editor-v2-open-source-offline-workflow-editor/39/8 "2017-02-20T16:10:45Z")
Writing here instead of a new topic since it relates to the workflow editor. First: We’ve fully committed to the new workflow-editor and are now running our bitrise.yml files from our repo, which is awesome (source-controlled bitrise.yml (Y)) Now the question: Is it possible to link to other bitrise.yml files? Our apps will now have like, 80-90% of their bitrise.yml file in common and we’d like to refactor out particular workflows to an another, perhaps included bitrise file? ---
**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:** [February 20, 2017, 4:17pm UTC](https://discuss.bitrise.io/t/workflow-editor-v2-open-source-offline-workflow-editor/39/9 "2017-02-20T16:17:35Z")
Awesome, really great to hear you like the new WF editor @david.everlof.knowit 😉 Sharing code between bitrise.yml s - there’s no built in way right now. You can of course `bitrise run --config=/path/to/bitrise.yml` from e.g. a **Script** step, to run another yml, but that’s… a workaround which works, but not elegant enough and certainly could be better. Feel free to create a #Feature Requests for this! Actually, this one seems to be quite close: > [@Add ability to reference step/workflow globally between apps](http://discuss.bitrise.io/t/add-ability-to-reference-step-workflow-globally-between-apps/727): > > From Callum Taylor on 2016/09/23 10:55:15 +0000 As an agency with many apps, we have a few steps that are the same for every app (such as sending slack message, uploading to s3 etc), some of these steps are simple, but chaging them for all apps (we will most likely have 30+) will be pretty time consuming. Would be nice to have an ability to reference a step within a workflow, or a workflow that can just be a “pre/post” workflow, somehow with an “account step/workflow” feature, or a new step th… ---
**Author:** ![david.everlof.knowit](https://avatars.discourse-cdn.com/v4/letter/d/278dde/32.png) [@david.everlof.knowit](https://discuss.bitrise.io/u/david.everlof.knowit)\ **Post date:** [February 21, 2017, 6:57am UTC](https://discuss.bitrise.io/t/workflow-editor-v2-open-source-offline-workflow-editor/39/10 "2017-02-21T06:57:42Z")
Alright, thank you. Yeah, if we’ll add something like this we’ll probably use the `bitrise run --config=...` version. I’ll add a feature request as well though! ---
**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:** [June 30, 2017, 8:47pm UTC](https://discuss.bitrise.io/t/workflow-editor-v2-open-source-offline-workflow-editor/39/11 "2017-06-30T20:47:36Z")
The WF editor is now available on [bitrise.io](http://bitrise.io) too, so I’ll mark this as solved here as it’s no longer WIP / Beta anymore 🙂 ---
**Author:** ![ch\_kent](https://avatars.discourse-cdn.com/v4/letter/c/ecb155/32.png) [@ch\_kent](https://discuss.bitrise.io/u/ch_kent)\ **Post date:** [August 22, 2017, 6:36am UTC](https://discuss.bitrise.io/t/workflow-editor-v2-open-source-offline-workflow-editor/39/12 "2017-08-22T06:36:50Z")
I’m probably missing some obvious stuff here, but I have questions… There is no mention of running the offline editor on Windows. But it’s not clear to me whether that completely rules out the possibility…perhaps this is being worked on? Or perhaps the editor is all performed in a browser session, so using a docker image might suffice? Worst case scenario is using a linux VM, but I just want to understand what other options I might have first. Thanks ---
**Author:** ![birmacher](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/birmacher/32/4864_2.png) [@birmacher](https://discuss.bitrise.io/u/birmacher)\ **Post date:** [August 23, 2017, 2:31pm UTC](https://discuss.bitrise.io/t/workflow-editor-v2-open-source-offline-workflow-editor/39/13 "2017-08-23T14:31:40Z")
We have not tested our CLI on Windows, so it’s not yet supported, but you can definitely setup a Linux VM there and it should be good to go. ---
**Author:** ![ch\_kent](https://avatars.discourse-cdn.com/v4/letter/c/ecb155/32.png) [@ch\_kent](https://discuss.bitrise.io/u/ch_kent)\ **Post date:** [August 24, 2017, 7:07am UTC](https://discuss.bitrise.io/t/workflow-editor-v2-open-source-offline-workflow-editor/39/14 "2017-08-24T07:07:40Z")
Thanks @birmacher. Would a Docker container suffice? I can’t see any Bitrise docker images in docker hub so I’m guessing that’s not an option…? ---
**Author:** ![birmacher](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/birmacher/32/4864_2.png) [@birmacher](https://discuss.bitrise.io/u/birmacher)\ **Post date:** [August 24, 2017, 7:51am UTC](https://discuss.bitrise.io/t/workflow-editor-v2-open-source-offline-workflow-editor/39/15 "2017-08-24T07:51:36Z")
We actually do have 🙂 You can find more info here about how to use them: [http://devcenter.bitrise.io/docker/run-your-build-locally-in-docker/](http://devcenter.bitrise.io/docker/run-your-build-locally-in-docker/) ---
**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:** [September 2, 2017, 6:43am UTC](https://discuss.bitrise.io/t/workflow-editor-v2-open-source-offline-workflow-editor/39/16 "2017-09-02T06:43:59Z")
@ch_kent The smallest one which has the CLI preinstalled (and other tools for step development etc.): [https://hub.docker.com/r/bitriseio/docker-bitrise-base/](https://hub.docker.com/r/bitriseio/docker-bitrise-base/) Should be enough to run the editor, but keep in mind that the editor runs in your browser, so the related port will have to be exposed through docker. ---
**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:** [September 2, 2017, 6:45am UTC](https://discuss.bitrise.io/t/workflow-editor-v2-open-source-offline-workflow-editor/39/17 "2017-09-02T06:45:55Z")
Actually the current workflow editor uses random ports… @ch_kent Feel free to create a #feature-request at [https://github.com/bitrise-io/bitrise-workflow-editor](https://github.com/bitrise-io/bitrise-workflow-editor) to have an option to set a fix port for the editor, which can then be specified for docker to be exposed.