UI to Trigger a pipeline (with optional parameters)
complete
A
Asmith
Add a button to trigger a build with an arbitrary environment variable.
For example, I could add a "Rebuild without Docker Layer Cache" button, check for NO_DOCKER_LAYER_CACHE in my circle.yml file, and conditionally remove old docker images.
Currently there does not seem to be a way to clear the docker layer cache without multiple commits to circle.yml (add clearing line, remove clearing line). This is insane and will drive us off of CircleCI if not addressed. A parameterized build button solves this and many other problem scenarios.
CCI-I-608
S
Sebastian Lerner
complete
https://circleci.com/docs/triggers-overview/#run-a-pipeline-from-the-circleci-web-app
Regarding the clearing of the Docker Layer Cache in the original request, this is also now possible in Project Settings: https://support.circleci.com/hc/en-us/articles/14027411555355-How-to-delete-a-projects-Docker-Layer-Cache#:~:text=You%20can%20also%20delete%20your%20DLC%20cache%20via%20the%20UI&text=Click%20Project%20Settings%20.,Click%20Delete%20Cache%20Contents%20.
Anton
I know some people had crazy configurations to overcome this - use UI support from GitHub Actions that will trigger CircleCi jobs.
I don't think this is a right flow - does the CircleCI team expect the competitor to be used for such tasks?
A
Ajith John
Updated link for related idea:
E
Eric Dahlseng
Related idea:
E
Eric Dahlseng
This would also be extremely helpful for rollback situations!
We currently use a CircleCI workflow for deploying to production upon approval, which works great – except for rollback... when we've discovered a bug that was introduced more than one deployment ago, the only option we have is a very manual process for deploying a specific older version. If there was a way to specify input arguments for a manual workflow, then we could easily use a CircleCI workflow to rollback to arbitrary versions, specified by the environment variable!
A
Arnas Matiukas
This feature is really necessary. It would solve a lot problems i think.For example QA engineers could build with different configurations application. Currently we use Postman for this purpose, but it is really inconvenient to start a build and then go to CircleCI Web UI. Also everyone locally needs to have an access key to API.