I am wondering though, when you do hit “New Build” and want to use the current branch, I assume you’re using HEAD? And the commit message is something random? i.e. is the action you want to perform a “just trigger a build on the latest HEAD the current branch” kinda thing?
Is your workflow perhaps:
I’m testing a new BK pipeline setup and I’m iterating on it. Hitting Rebuild uses the current commit, but ideally it’d just trigger a build using HEAD on the current branch
Thanks for the thoughtful consideration @keithpitt
Yes, you pretty much nailed my workflow. I’ve been through the process of setting up pipelines across a couple of companies now and maybe have used the new build button a few more times than your average user.
I like the idea of a context sensitive quick link. I think it makes things a bit easier for users in my position, without “moving the cheese” of users expecting a master build (which I guess a few people might use to trigger a build -> deploy on master in continuous deployment environments).
So when you click “Rebuild”, it’d offer you this context menu allowing you to do different things. In your case, you’d want the second option. The first option is the current behaviour. The third option would open the “New Build” box with everything ready to go (allowing you to make changes just like custom env)
Would something like this be a good solution? (or maybe putting it behind “Rebuild” is a little confusing?)
Totally (I mocked those images up very late last night, and I don’t think they solve the problems well). Hopefully the process of working through this is helpful! (It’s a nice experiment being way more transparent about how to solve the problem, and keeping you involved, let me know if you find it annoying )
So the other idea I had this morning is that we embrace what you’re trying to do, and provide specific buttons for it. i.e. what if pipelines started out in “setup” mode. When a pipeline is in this mode, there’d be a big “create new build on HEAD” type button above all the builds you’re looking at. Since we know what you’re trying to do, it makes sense that we call it out.
Once you’ve got the pipeline up and running and builds are green, we can have a “I’m done setting up this pipeline” button, which removes the “Trigger on HEAD” button, and a cool optional step - reset the pipeline back to Build #1, and remove all the old crappy ‘testing this’ commit messages.
I really like the idea of the setup mode for a pipeline the more I think about it, but not sure it helps with the original issue of being on a branch and the New Build button being slightly unhelpful with being pre-populated with master. Although my brain is now struggling to remember why I was clicking on “New Build” on a branch so often to warrant this topic.