buildserver | Tools for managing the Mixxx build server and build VMs | Build Tool library

I'm trying to reach each build in my local TFS 2015 server which has the "Retain Indefinitely" flag (BuildDetail.KeepForever Property) yet the QueryBuilds() function takes too long to get all of the builds.

TFS 2015 'Retain Indefinitely' Web GUI Menu Option

All I actually need is the KeepForever and the DropLocation properties.

I Found out you can get better efficiency using the IBuildDetailSpec interface yet I couldn't find an option in which I'll get the KeepForever property.

My current code snippet:

I have a couple of webapps I am adding gitversion to. Main problem - GitVersion is generating a MajorMinorPatchTag where the Major is in the format yyyymmdd. Aside from this not being a valid major version, I want the usual versioning 0.1.3.alpha.1 in the example below but I am getting 20201021.1.1.

I have removed all the old build tags from the repo so it does not appear to be finding this from tags. Is there anywhere else I can force it to ignore previous build versions and use the semver starting from the gitversion.yml/next-version setting?

Detail below:

The gitversion.yml is simple:

Our buildserver needs to release apps to App Center. App Center allows me to provide a release note file.

The problem is, our ReleaseNotes.md contains ALL the versions and become to big to for App Center to accept it.

The notes are formatted like this:

In our dev environment we have lots of repos, lots of builds and lots of buildservers, and most of the time things work just like they should - however, we are seeing an increase in builds that fail because of timeouts.

These timeouts are not happening because we are getting close to the limit, but because something "gets stuck/blocked" in the pipeline and it stays on that step until timeout kills the build.

To better debug why that happens, we need to be able to query what builds fails because of this timeout, so we for instance can see, if it is a particular build server or agent that has this problem.

We can not find anything in the API that would give us the timeout error, but we can see that the UI is able to deduct it somehow:

So far we have narrowed it down to query all builds with completed status (through this API), but we get no completion reason, and buildtimes are never exact the same as the timeout of the build defintion, so "guessing" it from the execution plan will also be a bit shaky.

How can we filter our builds down to only the builds that have timed out?

We use a “Visual Studio Offline Layout” to deploy VS 16.6 to both developers and buildservers with mixed internet connections (offline / proxy / direct). Up until lately, the installation/update from previous VS instances (16.3 to be exact) worked quite well.

Currently, we cannot use the offline layout to install the local cached version of Visual Studio any more, because computers connected to the internet want to update “Visual Studio Installer” prior to installing anything.

The call to vs_Professional.exe update --wait --norestart --noweb --noUpdateInstaller ... fails with exit code '1' pretty quick after it was invoked. Looking at the dd_ logs in TEMP, we find:

I have a number of gradle projects with a multi-project build stucture.

I use gradle build cache on our buildserver to only run tests in projects with changes or projects which dependsOn projects with changes. This works great and saves a lot of build time.

The problem is: Gradle projectA depends on a non gradle projectB, and I don't know how to set this dependency. projectB produces a docker used by projectA, and if an error is introduced in projectB, the tests in projectA doesn't run and the error goes into production.

So the question is how do you make a gradle "dependsOn" for any change in a non gradle project.

Sometime in the past 2-3 hours, my builds have started failing on this step:

My setup is: I have a solution that had different dotnet4.6 applications (services) in it. Now we added a dotnet core project inside this solution. I can build and debug it, but this doesn't create an executable. In Visual Studio I can rightclick -> Publish... it. I created two profiles (x86 and x64) that should create nice binaries in /bin/Publish/x86 or /x64. In VS this works. The application is self-contained and works on different unprepared machines.

But now I Need to move that process to the buildserver. I messed around with dotnet publish but in the end i get stuck because other components of the solution are not clean dotnet core and so the build fails. So I need to stick with MSBuild.

The current attempt is: "C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\15.0\Bin\MSBuild.exe" NewProject\NewProject.csproj /p:DeployOnBuild=true /p:UsePublishProfile=true /p:PublishProfile=x64Profile.

This says it finished building successfully, but I don't see any results. Also it doesn't make any difference, if I remove all properties and just call msbuild and *.csproj. It just builds the new project in bin/Debug, as dll, not exe.

I also messed around with p:PublishProfile="NewProject\Properties\PublishProfiles\x64Profile.pubxml" and /p:PublishUrl="NewProject\bin\Publish\x64" but it doesn't change anything.

I read a few articles on SO, telling that VS doesn't just call msbuild with parameters but does internal API calls. Still, I need a solution. I need the build server to create an executable. Is there a way to trigger msbuild to create thath?

Hi I have a superproject that contains a submodule. The submodule is tracked by a branch name and not by a sha commit number. On our buildserver I would like to pull as minimum as possible. So I tried