Posts made by brandon_owensby_2976

The reason I'm using Docker.Desktop is not to run Linux on Windows but to run Docker. The goal was to mimic our dev and prod deployment which involves using helm files to update what version of a given image is deployed in a given environment. This part I have working. I just figured I'd try taking advantage of having docker installed to try out this feature of BuildMaster. I didn't expect it to be this troublesome though.

When I was working on it this morning I tried updating the tag to pull a specific version of the image to ensure it was Linux but that didn't work either. In fact it didn't change anything. I'll look at it again on Monday. Maybe someone will have some insight before then and help me out. Let me know if there is anything I add to the post to help. If I see a response over the weekend I'll definitely update the post with any requested information.

oh, and I will look up this docker run command. Unfortunately that doesn't allow me to use the built in test function in BuildMaster which could take away from part of my sales pitch. We'll see what I can do, and maybe you or someone else will think of something else.

Hi @stevedennis,
In a way I get what you are saying but either it isn't clear what I'm asking for or there is something else I'm still missing. Inedo has a registered image you can use to run BuildMaster as a whole in Docker. I take it that somehow this is different than running just the InedoAgent which is why there isn't a docker for just the InedoAgent. However, running BuildMaster on Docker means you are indeed running an agent on docker as well, it just happens to be running as part of the buildmaster web app which makes it all the more confusing. Of course maybe the version of BuildMaster that is running on the Docker doesn't include the built in agent?

The other part that doesn't make sense is you say you shouldn't be "running commands" but I'm not really wanting to do anything that different from your suggested solution which is image-based services. I realize that in my case the image would be running all the time instead of spinning it up for the one command. The primary reason I am going down this path at the moment is you don't support running the unit tests with the "image-based services". If you did, and I could get it to work (still haven't) then I likely wouldn't have a reason to go down this path.

Thank you,
Brandon

Hi @stevedennis,
As I mentioned in the original post I had already tried the image-based services although I did refer to it as containerized builds. That helps with the build part but not with the unit test part. Of course I can't get that to work at all. You actually responded to the post I have on that as well so you know I'm still working at that.

Unfortunately VMs are not an option for me at the moment. I'm trying to do this all on my laptop and so far I've been quite successful. I understand, based on your comment, I might be doing something a bit odd (I even suggested that in my original post) but wasn't expecting your reason. I do find your reason intriguing though. This job (been here almost a year) is the first time I've used Docker. They are using Docker (via Kubernetes) here to spin up web servers for web apps and APIs. Not all our apps have been migrated to this yet but they are essentially moving towards deploying all of our web apps and APIs to docker images instead of VMs. Maybe this isn't the best example but is what gave me the idea to try this, especially since I have docker running locally. In fact, the other confusing thing about what you said is that I know Inedo supports running BuildMaster in a Docker image so why not just the agent?

For the record, I'm not new to BuildMaster. I've actually been using BuildMaster for about 12 years now. I know you would typically put agents on the various servers you want to do things on and so why have one just running an agent. This is just to create a server for building. A very similar approach to the image-based services, it would support more commands than that feature does.

Bottom line is that this is my only option at the moment for this demo to have that capability fully (running both the build and unit tests in Linux). The bright side is that if I can get my other post figured out I that will be a huge plus in this direction. If anyone has any other thoughts on this I'd appreciate but I certainly understand if it isn't really feasible.

Thank you,
Brandon

Hi @stevedennis,
Actually my Docker.Desktop is set up to communicate with a Linux Docker engine. That makes me wonder what type of image it is trying to run from buildmaster though. Somewhere I think the wires are getting crossed as to what OS it is using vs what it thinks it is using.

Thank you,
Brandon

I enabled Image-based Services and had it install the default images. BuildMaster is installed on a windows server that is also running DockerDesktop so the docker.exe version command shows 29.4.1. Now I found an article on your site that didn't mention DockerDesktop but did talk about other options and said that depending what you were using depended on whether it supported Linux or not. I know my Docker does support Linux as that is what I'm using on the images running on it but when I try to kick of the build it gives me an error as if it thinks it is running on Linux but is actually on Windows. Below is the log from the build.

Screenshot showing it is set to run in a container:

Screenshot showing Image-based Services are enabled and the registered services:

Log from Build:

Using LocalAgent agent on localhost
Updating local repository for http://bitbucket1.sscs.ad:7990/scm/cdb/transaction.api.git...
Git backend: libgit2sharp
Repository path is C:\ProgramData\BuildMaster\Temp\Service\.gitrepos\bitbucket1.sscs.ad$7990$scm$cdb$transaction.api.git
Fetching from origin (http://bitbucket1.sscs.ad:7990/scm/cdb/transaction.api.git)...
Fetch completed in 00:00:00.1317612.
Exporting files to C:\ProgramData\BuildMaster\Temp\Service\_E327\...
Checking out code from de476603d1d6185ddac1708c5de9cda5a3fd8c68 to C:\ProgramData\BuildMaster\Temp\Service\_E327\...
Lookup succeeded; found commit de476603d1d6185ddac1708c5de9cda5a3fd8c68.
Looking for submodules...
No submodules in repository.
Using LocalAgent agent on localhost
Searching for files matching **.csproj in C:\ProgramData\BuildMaster\Temp\Service\_E327...
Found 11 matching files.
Reading C:\ProgramData\BuildMaster\Temp\Service\_E327\SSCS.Mapping.Generator\SSCS.Mapping.Generator.csproj...
C:\ProgramData\BuildMaster\Temp\Service\_E327\SSCS.Mapping.Generator\SSCS.Mapping.Generator.csproj loaded.
Setting Version in C:\ProgramData\BuildMaster\Temp\Service\_E327\SSCS.Mapping.Generator\SSCS.Mapping.Generator.csproj to 1.3.1...
Writing C:\ProgramData\BuildMaster\Temp\Service\_E327\SSCS.Mapping.Generator\SSCS.Mapping.Generator.csproj...
C:\ProgramData\BuildMaster\Temp\Service\_E327\SSCS.Mapping.Generator\SSCS.Mapping.Generator.csproj saved.
Reading C:\ProgramData\BuildMaster\Temp\Service\_E327\Transaction.API\Transaction.API.csproj...
C:\ProgramData\BuildMaster\Temp\Service\_E327\Transaction.API\Transaction.API.csproj loaded.
Setting Version in C:\ProgramData\BuildMaster\Temp\Service\_E327\Transaction.API\Transaction.API.csproj to 1.3.1...
Writing C:\ProgramData\BuildMaster\Temp\Service\_E327\Transaction.API\Transaction.API.csproj...
C:\ProgramData\BuildMaster\Temp\Service\_E327\Transaction.API\Transaction.API.csproj saved.
Reading C:\ProgramData\BuildMaster\Temp\Service\_E327\Transaction.Application\Transaction.Application.csproj...
C:\ProgramData\BuildMaster\Temp\Service\_E327\Transaction.Application\Transaction.Application.csproj loaded.
Setting Version in C:\ProgramData\BuildMaster\Temp\Service\_E327\Transaction.Application\Transaction.Application.csproj to 1.3.1...
Writing C:\ProgramData\BuildMaster\Temp\Service\_E327\Transaction.Application\Transaction.Application.csproj...
C:\ProgramData\BuildMaster\Temp\Service\_E327\Transaction.Application\Transaction.Application.csproj saved.
Reading C:\ProgramData\BuildMaster\Temp\Service\_E327\Transaction.Application.DTO\Transaction.Application.DTO.csproj...
C:\ProgramData\BuildMaster\Temp\Service\_E327\Transaction.Application.DTO\Transaction.Application.DTO.csproj loaded.
Setting Version in C:\ProgramData\BuildMaster\Temp\Service\_E327\Transaction.Application.DTO\Transaction.Application.DTO.csproj to 1.3.1...
Writing C:\ProgramData\BuildMaster\Temp\Service\_E327\Transaction.Application.DTO\Transaction.Application.DTO.csproj...
C:\ProgramData\BuildMaster\Temp\Service\_E327\Transaction.Application.DTO\Transaction.Application.DTO.csproj saved.
Reading C:\ProgramData\BuildMaster\Temp\Service\_E327\Transaction.CdbWin.Client\Transaction.CdbWin.Client.csproj...
C:\ProgramData\BuildMaster\Temp\Service\_E327\Transaction.CdbWin.Client\Transaction.CdbWin.Client.csproj loaded.
Setting Version in C:\ProgramData\BuildMaster\Temp\Service\_E327\Transaction.CdbWin.Client\Transaction.CdbWin.Client.csproj to 1.3.1...
Writing C:\ProgramData\BuildMaster\Temp\Service\_E327\Transaction.CdbWin.Client\Transaction.CdbWin.Client.csproj...
C:\ProgramData\BuildMaster\Temp\Service\_E327\Transaction.CdbWin.Client\Transaction.CdbWin.Client.csproj saved.
Reading C:\ProgramData\BuildMaster\Temp\Service\_E327\Transaction.Client.Shared\Transaction.Client.Shared.csproj...
C:\ProgramData\BuildMaster\Temp\Service\_E327\Transaction.Client.Shared\Transaction.Client.Shared.csproj loaded.
Setting Version in C:\ProgramData\BuildMaster\Temp\Service\_E327\Transaction.Client.Shared\Transaction.Client.Shared.csproj to 1.3.1...
Writing C:\ProgramData\BuildMaster\Temp\Service\_E327\Transaction.Client.Shared\Transaction.Client.Shared.csproj...
C:\ProgramData\BuildMaster\Temp\Service\_E327\Transaction.Client.Shared\Transaction.Client.Shared.csproj saved.
Reading C:\ProgramData\BuildMaster\Temp\Service\_E327\Transaction.Domain\Transaction.Domain.csproj...
C:\ProgramData\BuildMaster\Temp\Service\_E327\Transaction.Domain\Transaction.Domain.csproj loaded.
Setting Version in C:\ProgramData\BuildMaster\Temp\Service\_E327\Transaction.Domain\Transaction.Domain.csproj to 1.3.1...
Writing C:\ProgramData\BuildMaster\Temp\Service\_E327\Transaction.Domain\Transaction.Domain.csproj...
C:\ProgramData\BuildMaster\Temp\Service\_E327\Transaction.Domain\Transaction.Domain.csproj saved.
Reading C:\ProgramData\BuildMaster\Temp\Service\_E327\Transaction.Persistence\Transaction.Persistence.csproj...
C:\ProgramData\BuildMaster\Temp\Service\_E327\Transaction.Persistence\Transaction.Persistence.csproj loaded.
Setting Version in C:\ProgramData\BuildMaster\Temp\Service\_E327\Transaction.Persistence\Transaction.Persistence.csproj to 1.3.1...
Writing C:\ProgramData\BuildMaster\Temp\Service\_E327\Transaction.Persistence\Transaction.Persistence.csproj...
C:\ProgramData\BuildMaster\Temp\Service\_E327\Transaction.Persistence\Transaction.Persistence.csproj saved.
Reading C:\ProgramData\BuildMaster\Temp\Service\_E327\Transaction.Tests.Common\Transaction.Tests.Common.csproj...
C:\ProgramData\BuildMaster\Temp\Service\_E327\Transaction.Tests.Common\Transaction.Tests.Common.csproj loaded.
Setting Version in C:\ProgramData\BuildMaster\Temp\Service\_E327\Transaction.Tests.Common\Transaction.Tests.Common.csproj to 1.3.1...
Writing C:\ProgramData\BuildMaster\Temp\Service\_E327\Transaction.Tests.Common\Transaction.Tests.Common.csproj...
C:\ProgramData\BuildMaster\Temp\Service\_E327\Transaction.Tests.Common\Transaction.Tests.Common.csproj saved.
Reading C:\ProgramData\BuildMaster\Temp\Service\_E327\Transaction.Tests.Integration\Transaction.Tests.Integration.csproj...
C:\ProgramData\BuildMaster\Temp\Service\_E327\Transaction.Tests.Integration\Transaction.Tests.Integration.csproj loaded.
Setting Version in C:\ProgramData\BuildMaster\Temp\Service\_E327\Transaction.Tests.Integration\Transaction.Tests.Integration.csproj to 1.3.1...
Writing C:\ProgramData\BuildMaster\Temp\Service\_E327\Transaction.Tests.Integration\Transaction.Tests.Integration.csproj...
C:\ProgramData\BuildMaster\Temp\Service\_E327\Transaction.Tests.Integration\Transaction.Tests.Integration.csproj saved.
Reading C:\ProgramData\BuildMaster\Temp\Service\_E327\Transaction.Tests.Unit\Transaction.Tests.Unit.csproj...
C:\ProgramData\BuildMaster\Temp\Service\_E327\Transaction.Tests.Unit\Transaction.Tests.Unit.csproj loaded.
Setting Version in C:\ProgramData\BuildMaster\Temp\Service\_E327\Transaction.Tests.Unit\Transaction.Tests.Unit.csproj to 1.3.1...
Writing C:\ProgramData\BuildMaster\Temp\Service\_E327\Transaction.Tests.Unit\Transaction.Tests.Unit.csproj...
C:\ProgramData\BuildMaster\Temp\Service\_E327\Transaction.Tests.Unit\Transaction.Tests.Unit.csproj saved.
Performing containerized build using ".NET 6" image based service.
Using LocalAgent agent on localhost
Ensuring working directory C:\ProgramData\BuildMaster\Temp\Service\_E327 exists...
Executing dotnet publish "/var/buildmaster-ibs/Transaction.API/Transaction.API.csproj" --configuration "Release" --output "/var/buildmaster-ibs/publish" "-p:ContinuousIntegrationBuild=true" "--no-self-contained" ...
Unhandled exception: System.ComponentModel.Win32Exception (2): An error occurred trying to start process 'id' with working directory 'C:\Windows\system32'. The system cannot find the file specified.
   at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo)
   at System.Diagnostics.Process.Start()
   at Inedo.Agents.LocalProcess.Start()
   at Inedo.Agents.LocalProcess.Inedo.Agents.IRemoteProcess.StartAsync(CancellationToken cancellationToken)
   at Inedo.BuildMaster.Windows.ServiceApplication.Executions.PlanExecuter.AgentDockerHost.GetCurrentUserIdAsync(IRemoteProcessExecuter exec, ActiveNamedScope log, CancellationToken cancellationToken)
   at Inedo.BuildMaster.Windows.ServiceApplication.Executions.PlanExecuter.AgentDockerHost.ExecuteInContainerAsync(ContainerStartInfo containerStartInfo, CancellationToken cancellationToken)
   at Inedo.Extensions.DotNet.Operations.DotNet.DotNetBuildOrPublishOperation.<>c__DisplayClass63_0.<<ExecuteAsync>g__execAsync|2>d.MoveNext() in C:\Users\builds\AppData\Local\Temp\InedoAgent\BuildMaster\192.168.44.60\Temp\_E613379\Src\DotNet\InedoExtension\Operations\DotNet\DotNetBuildOrPublishOperation.cs:line 420
--- End of stack trace from previous location ---
   at Inedo.Extensions.DotNet.Operations.DotNet.DotNetBuildOrPublishOperation.ExecuteAsync(IOperationExecutionContext context) in C:\Users\builds\AppData\Local\Temp\InedoAgent\BuildMaster\192.168.44.60\Temp\_E613379\Src\DotNet\InedoExtension\Operations\DotNet\DotNetBuildOrPublishOperation.cs:line 332
   at Inedo.BuildMaster.Windows.ServiceApplication.Executions.PlanExecuter.OtterScriptExecuter.Inedo.ExecutionEngine.Executer.IExecutionHostEnvironment.ExecuteActionAsync(ActionStatement actionStatement, IExecuterContext context)
Cleaning up...
Deleting C:\ProgramData\BuildMaster\Temp\Service\_E327 on localhost...
C:\ProgramData\BuildMaster\Temp\Service\_E327 on localhost deleted.
Cleanup complete.

Let me start out by saying that I understand that at first glance you'll question why this is something I'd want to do. My primary reason for wanting to do this is that I'm trying to sell my company on using BuildMaster and I think one thing that will help is showing I can run an agent on a docker file and preferably Linux so that not only will the build happen in Linux but I can also kick of the unit tests in Linux. I looked into the containerized builds and that would solve half my issue but not the other. I've done a lot of looking around, and I know that installing the InedoAgent on a standard Linux is something you can ask support about but I haven't seen anything about putting it on a docker image for either Linux or Windows.

Thank you for that information. I've yet to fully learn all the technology used in our lifecycle but that is what I'm trying to do more of with this project (in addition to a proposal). You've been me a little extra insight I haven't gotten internally yet. We do use Argo CD. I've actually used it to the see the status of Kubernetes but I didn't realize it talked directly to git. Being that I can't afford my own license for Argo CD and it isn't free I'll focus on seeing if I can come up with a plan to manage updating the yaml files and git with BuildMaster.

As far as my original post I think you have helped me post a more succinct question. Once I get my yaml file updating in a specific directory would I use the Kubernetes plugin to have it run the command to reload the yaml or would I need to do my own manual powershell call to do that?

I'm trying to get a deployment going using Docker and Kubernetes. I have very little experience with those 2 technologies and even less when doing so with BuildMaster. So far I have successfully created an image and posted it to the image store in Pro Get. I've also got a yaml file which loads the image via Kubernetes. My next step is to have a build step that does that for me instead of having to update the yaml file manually. I have the Kubernetes extension installed but I only see 2 commands and I haven't been able to find documentation even with the ? icon on one of the commands. I was hoping someone could help me connect the dots. I'm assuming it might involve a step of me updating the yaml file from a script before running the Kubernetes command but I'm not sure.

Hi @stevedennis ,
Thank you for the response. I tried the curl you mentioned and it actually prompts me for a host password for user. Of course entering this in doesn't help. I even had an admin check and see if HTTP(s) SCM hosting is enabled on our server, and it is. We do have an older version of Bitbucket Server and here soon we are supposed to be migrating to a new one. If I don't figure this out before then I will be curious if the new server makes a difference. I haven't see anything about what versions you do or don't support.

Thank you,
Brandon

I'm trying to set up a demo of your software to show to my company. I've used your software for years but in the past I've used GitHub. Now I'm trying to use a Bitbucket Server and it is getting a 401 when trying to access the repository.

Before I go any further I'm using 2025.5 (Build 14).

When I first set it up I used the standard bitbucket path. The dropdowns worked beautifully to pick the repository in question but when it tried to clone it got a 401 error. After browsing your forums I tried setting up a generic git repository and I get the same result when it tries to clone. I'm hoping someone can either provide more information (like are are there version limitations on support) or give me some idea of how I can troubleshoot further. I'd hate for the company to miss out on this great product for something like this.