-
-
Notifications
You must be signed in to change notification settings - Fork 18
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
Skip checkin on any shelveset #32
Comments
You're right that the shelveset builds are not treated as Gated. It would be relatively easy to detect whether this is a Shelveset build (the code is already there), but I know a few people are building to support "buddy builds" which only check in if the build succeeds. I don't know when I'll have time to fix this, I'm open to a pull request on this. The checks are already here: https://github.com/jessehouwing/vsts-tfvc-tasks/blob/master/vsts-tfvc-checkin/TfvcCheckin.ps1#L184 So it would require a quick update in the UI: https://github.com/jessehouwing/vsts-tfvc-tasks/blob/master/vsts-tfvc-checkin/task.json#L154 with a default value of False for backwards compatibility. I don't think this is different than it was in XAML builds when doing buddy builds. |
Adding this to the Gated Checkin task. |
Hi, Cheers, fre 3 juni 2016 kl 10:53 skrev Jesse Houwing notifications@github.com:
|
A review of the tasks with a short description of how you're using it would be very appreciated. |
I'd like to broaden or extend the "Skip checkin on Gated changes" feature to apply to whenever a shelveset is sent to the build. I don't think such builds are "gated" as build vNext sees it, at least we've had the issue that the changes were checked in even though this was not the intention.
The text was updated successfully, but these errors were encountered: