You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 8, 2024. It is now read-only.
I noticed in the API Docs the project build API is being replaced. Is that an accurate statement?
POST /project/:vcs-type/:username/:project/build
Replaced by POST /project/:vcs-type/:username/:project/pipeline
If so, will the ability to trigger a build at a certain branch/commit or tag be introduced through a different feature? We're using this capability to implement sane environment/version management using the grace-circleci-builder. This API feature is exceptionally useful, save for the lack of being able to provide build parameters at execution-time (ie: secret injection).
The text was updated successfully, but these errors were encountered:
You should be able to accomplish the same tasks with the replacement endpoint. In our v2 Preview docs https://circleci.com/docs/api/v2/#trigger-a-new-pipeline we describe how the POST body will accept branch, tag, and parameters. Give it a shot!
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I noticed in the API Docs the project build API is being replaced. Is that an accurate statement?
If so, will the ability to trigger a build at a certain branch/commit or tag be introduced through a different feature? We're using this capability to implement sane environment/version management using the grace-circleci-builder. This API feature is exceptionally useful, save for the lack of being able to provide build parameters at execution-time (ie: secret injection).
The text was updated successfully, but these errors were encountered: