I suggest you ...

Allow all pipeline and workflow configuration in wercker.yml

The split configuration of wercker.yml and Web UI is very confusing for new users and creates a painful and manual administration point.

The requirement to create a pipeline in the wercker.yml and then create it again in the UI in order to execute it is not intuitive and not maintainable for many projects.

Since the pipeline creation and workflow creation dialogs ask for such limited data, can't the information be defined in wercker.yml - i.e. pipeline as code instead of pipeline as some code and some UI clicking?

Vice-versa - if the workflows/pipelines can be created in the UI, why not export/serialize them to wercker.yml to save into the codebase?

12 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Tim HTim H shared this idea  ·   ·  Admin →

    0 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...

      Feedback and Knowledge Base