Skip to content
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

vela-downstream invoke most recent commit of a branch #220

Closed
msanssouci opened this issue Feb 24, 2021 · 2 comments · Fixed by go-vela/vela-downstream#142
Closed

vela-downstream invoke most recent commit of a branch #220

msanssouci opened this issue Feb 24, 2021 · 2 comments · Fixed by go-vela/vela-downstream#142
Labels
area/plugin Indicates a change to a plugin enhancement Indicates an improvement to a feature

Comments

@msanssouci
Copy link

msanssouci commented Feb 24, 2021

Description

Currently the go-vela/vela-downstream plugin is implemented such that it finds the last the successful build on a branch and restarts it. My use case is I want to build the most recent commit of a branch regardless of previous build statuses. When I tried using the current implementation configuring my functional test repo and branch main, the plugin attempted to restart a pull_request build because it was the last successful build.

Value

My team would like to use go-vela/vela-downstream plugin to trigger builds of our functional tests by triggering a build of the most recent commit on the main branch of our functional test repo.

Definition of Done

I can use the go-vela/vela-downstream to trigger the most recent commit of a branch.

Effort (Optional)

Impacted Personas (Optional)

@msanssouci msanssouci added the enhancement Indicates an improvement to a feature label Feb 24, 2021
@msanssouci msanssouci changed the title vela-downstream invoke HEAD of a branch vela-downstream invoke most recent commit of a branch Feb 24, 2021
@ghost ghost added the area/plugin Indicates a change to a plugin label May 10, 2021
@ghost
Copy link

ghost commented May 10, 2021

Thanks, this is in our backlog and we are assessing its priority.

@ecrupper
Copy link
Contributor

ecrupper commented Jan 3, 2024

Note: this is doable by enumerating all statuses in the status parameter for this plugin, but that isn't exactly ideal. It would be better if there was an all option or something as well. Keeping this issue open for that

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/plugin Indicates a change to a plugin enhancement Indicates an improvement to a feature
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants