Question

I think it would be a great feature to be able to assign open cases to a repository and then block pulls from that repo to another repo via the kiln web interface until those fb cases are closed. Obviously, we wouldn't want to block all pulls or else a developer may not be able to pull the code to resolve it; I suppose this would be a kiln web/ui only restriction.

Answer 1

Thanks for the feature request, Brian.

While I appreciate the sentiment, we are unlikely to implement this feature. As you yourself have noted, the restriction could impede perfectly valid workflows (e.g., one of the cases mentioned is an inbox case, and the customer replies just before you push; do we block the push merely because the inbox case is active?), and therefore would require work-arounds that would obviate the point.

If this workflow works well for you, then you can actually realize it today through a combination of web hooks and the Kiln API. While this isn't the easiest hook in the world, it's not too bad, either:

1. Make a repository that is read-only for everyone on your team. This is your official repository
2. Add a web hook that fires whenever anyone pushes to specific repositories--say, all the branch repositories off of the main repository I just mentioned.
3. When developers push there, the web hook fires. Your script checks to see that all cases mentioned in the repository are closed. If they are, it initiates a server-side push to the official repository. If not, nothing happens.
4. You can optionally use FogBugz's URL Trigger plugin to keep the script up-to-date as cases change, so that the push can go through once everything is closed.