Several issues with TeamBuild, July CTP

Several issues with TeamBuild, July CTP

• Alberto Canabal

  Hi:
  
  Would it be possible for you to post the steps / code required to override the BeforeCompile target to remove the write-protection for the files / folders
  
  Thanks,
  Rob
  

• Phil Montalbano

  2+5) Okay, thought that that would do the trick. Proves yet again that running this kind of software in a virtual machine really is the way to go. Unfortunately, I did not... Could've easily checked out whether or not anything would break in a virtual machine, but on a real one... Nah.
  
  3) This is the log:
  Build started 8/15/2005 8:44:33 AM.
  __________________________________________________
  Project "C:\Builds\Nightly\BuildType\TeamBuild.proj" (EndToEndIteration target(s)):

  Target CoreClean:
      Removing directory "C:\Builds\Nightly\BuildType\..\sources".
      C:\Program Files\MSBuild\Microsoft\VisualStudio\v8.0\TeamBuild\Microsoft.TeamBuild.targets(154,5): error MSB3231: Unable to remove directory "C:\Builds\Nightly\BuildType\..\sources". The process cannot access the file 'C:\Builds\Nightly\sources\Pilot' because it is being used by another process.
  Done building target "CoreClean" in project "TeamBuild.proj" -- FAILED.

  Done building project "TeamBuild.proj" -- FAILED.

  Build FAILED.
  C:\Program Files\MSBuild\Microsoft\VisualStudio\v8.0\TeamBuild\Microsoft.TeamBuild.targets(154,5): error MSB3231: Unable to remove directory "C:\Builds\Nightly\BuildType\..\sources". The process cannot access the file 'C:\Builds\Nightly\sources\Pilot' because it is being used by another process.
      0 Warning(s)
      1 Error(s)

  Time Elapsed 00:00:01
  
  
  4) I wish I could. There is no log. I just get the following error:
  ---------------------------
  Microsoft Visual Studio
  ---------------------------
  TF42012: The build type Nightly was not found. Confirm that this is a valid Build Type and that all required files such as TeamBuild.proj are checked in.
  ---------------------------
  OK  
  ---------------------------
  
  Thanks again for the swift responses. Shall I file a bug for issues 3 and 4 in the feedback center
  
  Wolfgang

  
  

• Jim_Bromer

  Sure, just add this to the TeamBuild.proj file:
  
    <Target Name="BeforeCompile">
      <Message Text="Going to remove write protection"/>
      <Exec Command="attrib -R $(BuildDirectoryPath)\*.* /s" />
    </Target>
  
  Hope this helps,
  
  Wolfgang
  

• Kapil_kaash

  3) Okay, from what I hear, the Bin folder issue will be resolved as well, so I guess this issue can be regarded as fixed, or at least it will not occur in the final again.
  
  4) Okay, now I know that this happens I can recognize the problem, but it isn't really clear from the get-go. After all, the TeamBuild.proj file is checked in and the build type exists, so the error message seems to be faulty. I would suggest adding the possibility of the TeamBuild.proj file not being valid to the error message. I'm confident that this issue will be resolved though, so I will not file a bug for it.
  
  Thanks again for helping me out.
  
  Wolfgang
  

• Emoir

  Thanks for your reply and thanks for looking into it. I would like to confirm the following however: installing Team Suite on the application tier will _not_ break anything I'd hate to have to go through all the installation pains again...
  
  I did some more research on the Code Analysis issue by the way. I found a workaround for that one too. The Microsoft.VisualStudio.QualityTools.Resource assembly is located in the assembly\GAC_MSIL folder on workstations that have the VS for Testers/Team Suite installed. When I copied the Microsoft.VisualStudio.QualityTools.Resource.dll to the Common7\IDE\PublicAssemblies folder on the build server, Code Analysis ran without error. I suspect that this issue will also be solved by installing Visual Studio for Testers or Visual Studio Team Suite on the build server...
  

• Nahar

  To run tests you will need to install VS for Testers on the build server.
  
  We are looking into all of the issues that you have pointed out and will post a reply soon.
  
  Thanks,
  Amit

  
  

• halfazner

  Here is what I found out,
  
  

  2)       For CodeAnalysis to work, we require that either VS Team Suite or VS for Team Developer/Test to be present.
  

  3)       There are some cases in which the log file was not getting created and no location to the drop was present in the build report. We have fixed many of the issues in post CTP bits. Can you check if a log file is present in the build directory and what are its contents (it should in <BuildDirectory>\<TeamProject>\<BuildType>\BuildType\BuildLog.txt< xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" />

        4)       This is not a known issue. Can you provide the log
  
        5)       Yes, we do require VS for Testers or VS Team System on build machine to execute tests. You can not copy files to build machine and execute tests. This is the limitation in v1. 
  
  Unfortunately, I am not able to confirm that installing the team suite on a machine containing the application tier and build server for the July CTP bits will break anything on the server.
  

• format1337

  Thanks for the help! It probably would have taken me a while to find out how to do this.
  
  Rob
  

• ajay_dekavadiya

  3) Based on the log, it appears to be a known problem that I described in the previous post. We have fixed the issue that the build log link was not showing up in such cases. However, the build will still fail if the sources directory could not be cleaned. 
  
  4) If the teambuild proj file for the build type is broken, we give this error message when attempting to build. The error does indicate that the build type may not be valid. You are correct that there is no build log generated when this happens as the build is not kicked off. This is our present behaviour. In July CTP bits there is a bug due to which if you have a broken build type as well as a functioning build type, attempting to build the functioning build type will also throw up a dialog with this error although the build will be actually started once you clear away the dialog. This issue will be fixed. If you feel that this doesn't cover the issue, please feel free to go ahead and file a bug.
  
  Amit

  
  
• Several issues with TeamBuild, July CTP