CircleCI Ideas

Allow users to manually trigger ad-hoc workflows for commits

We have a long-running and resource-intensive legacy test/build process. Due to this, true continuous integration is cost prohibitive until we can spend some serious time to address our technical debt. Currently we have "only" filters to limit runs to ci-* branches, so users can push to those in order to trigger a build. This works, but is a bit unintuitive and not a great user flow since we still want the source commit/branch tagged as a green build.

What would be great is if we could see all commits/branches in CircleCI, even if they are skipped, and having the ability to trigger a workflow manually to run against a specific commit.

Another use case is to pick a workflow for a specific branch. E.g. when branch release is green, I would like the ability to choose to run a workflow of either deploy_staging or deploy_production.

I think I can probably accomplish this by specifying workflows with a series of hold/approval steps that we just ignore most of the time, but that sure seems like a hack.


  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Mar 27 2018
  • Taking votes
  • Attach files
  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    23 May 15:20

    Aside from that, github notifications went down yesterday morning. That's another use case for triggering this via the UI (or at least with the API considering it's broken on 2.1)

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    12 Jun 15:32

    Similarly we have a number of new git repos being created a new project and CircleCI doesn't execute workflows until it's been enabled on a new repo.  Once it's been enabled, it only runs once on master, no other branch.


    We now have to do dummy/empty commits to re-trigger CircleCI for branches that didn't run before CircleCI was enabled.


    This makes our git history untidy and messes up versioning strategies.


    Also, this was requested a while back here (but since was auto-closed):

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    15 Aug 21:54

    We're using CircleCI to handle our deployment process. If something goes wrong, I'd like to have a rollback workflow that I can manually trigger.

  • Admin
    Nathan Dintenfass commented
    16 Aug 02:24

    We are previewing a way to drive workflows via the api using parameters. It’s not quite what you have in mind, but I wonder if it would work: