-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Trigger build for Branch, Commit #2679
Comments
Will there be a UI conterpart Build button (like Restart button). You'll need a way to specify / select branch as well as an optional commit. |
For this first iteration it will be available via the API and the CLI. There is a separate effort to add a branch summary screen to the user interface, at which point we will add a button to launch a build for a particular branch. I do not have a timeline for the UI, which is a separate team. Once I have more details I can post an update to this thread. |
@bradrydzewski does this feature already enabled on v1.1.0? I saw the PR merged on this version but when I send api with builds nothing happened, |
@iamjarvo nope it is not part of any release yet. You would have to use master / latest until 1.2 is available. Also just a side note that you can often check on features and corresponding versions here https://github.com/drone/drone/blob/master/CHANGELOG.md 🙂 |
thanks @bradrydzewski |
@bradrydzewski , when is going to be support for params for /builds
I saw in promote its enable |
I couldn't find an active GitHub repo for the docs, but these endpoints are missing from the official docs: |
Currently the only way to programmatically trigger a build is by re-starting an existing build with a new build number via the API. With 1.0 we now have the ability to fetch command branch data from version control, which means we can trigger a new build without any pre-existing data.
I propose adding the following endpoints:
You can pass additional parameters to your pipeline as url query parameters:
Note that if no branch is provided, the default branch (master) is used.
The text was updated successfully, but these errors were encountered: