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

#875 - Gated check-in in batch could possibly give a build failed #876

Merged
merged 1 commit into from
Nov 30, 2015
Merged

#875 - Gated check-in in batch could possibly give a build failed #876

merged 1 commit into from
Nov 30, 2015

Conversation

tverboon
Copy link

When multiple shelvesets are validated in a batch, it possible that some shelveset didn't pass. The overall build status is Partially Succeeded. To find out if the requested build has been rejected or not, lookup this build in the request builds collection and check the status.

@tverboon
Copy link
Author

I see that Vs2010 build is broken, this is because MS changed the interface IQueuedBuild. The Builds property is not available in 2010. Any ideas how to circumvent this? Don't really like it, but we could do a conditional build. Something like #if VS2010?

@tverboon
Copy link
Author

Sorry, I messed up my commit message. It should beVS2010 of course

@spraints
Copy link
Member

I see that Vs2010 build is broken, this is because MS changed the interface IQueuedBuild. The Builds property is not available in 2010. Any ideas how to circumvent this? Don't really like it, but we could do a conditional build. Something like #if VS2010?

I'm allergic to #if 😀 so I think something different should be done. The way we've dealt with it before is to have different code in the different VsXX projects. Almost all of it is shared in the TfsHelper.Common.cs file, but something like this could go into TfsHelper.Vs2012Base.cs. Since it's just a small piece of QueueGatedCheckinBuild, the new code could get pulled into a protected virtual method that's empty in TfsHelper.Common.cs and that has the new implementation in Vs2012Base.

@tverboon
Copy link
Author

I'm allergic to #if

Me too! Will see if I can implement your proposal tomorrow

@tverboon
Copy link
Author

Should be working now. I was trying to clean up the pull request, but my lack of experience only made it worse.

@tverboon
Copy link
Author

Is it possible to retry a build, cause it failed on installation of nuget package?

@pmiossec
Copy link
Member

Done.

@pmiossec
Copy link
Member

I'm sorry to have to tell you, but even if the contribution seems very good (!), you end up with an history that is really a mess....... :(

Could you squash the history to keep only one commit?

Should be done with git rebase -i 74b7eec6526c5df6b0ea6168fd9a4240d629e8ef.
Then squash all the commits into the first one...

Then you will just have to force push.

Gated check-in in batch could possibly give a build failed. - #875
@spraints
Copy link
Member

Thanks for the contribution, and for squashing it!

spraints added a commit that referenced this pull request Nov 30, 2015
#875 - Gated check-in in batch could possibly give a build failed
@spraints spraints merged commit a462309 into git-tfs:master Nov 30, 2015
@tverboon
Copy link
Author

Your welcome, thanks for the feedback

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants