@stevedennis and @inedo-engineer I appreciate that. I really didn't care about reputation except that it was preventing me from replying back to my tickets and saying thank you. It said my reputation wasn't high enough to have that many posts and I had to wait a while before I could say "Thank you" on another post. Maybe when you turned that feature off you fixed that issue too. I just thought I'd let you know more details so if you upgrade again you can keep track of that.
Thank you,
Brandon

Hi @inedo-engineer , I was just curious about voting/reputation. I did some digging and I have no reputation because no one ever votes on my tickets. When I did research apparently one thing that can help is doing a good job reporting bugs. Can you tell me why bugs are not good enough? Or do you guys have a policy against voting on users stuff so the only way I can get a vote or uptick in my reputation is by non employees?

@stevedennis Thank you, I look forward to hearing back.

Thank you!!!

Thank you!!

@stevedennis

Thank you

I am trying to set up a simple IIS deploy where it deploys to an application and ensures that application exists. I filled out the wizard and then I tested it and it failed. When I researched why it failed I discovered it was not filling in the arguments correctly of the IIS:Ensure-Application command. If I click the Edit as script button I get the following script for that command:

IIS::Ensure-Application
(
    Name: /CStore.API,
    Site: WebApps,
    AppPool: DefaultAppPool,
    PhysicalPath: C:\IIS\CStore.API
);

The visual editor looks like this:

You'll notice there is no record of the Name (/CStore.API). If I fill in Application path on that form, save it, and flip back to the text editor you get this:

IIS::Ensure-Application /CStore.API
(
    Name: /CStore.API,
    Site: WebApps,
    AppPool: DefaultAppPool,
    PhysicalPath: C:\IIS\CStore.API
);

Name is still there but now you can see that same value is added else where. I'm hoping this is something you are willing to fix so I can use the Wizard as it claims to be instead of having to use a custom script. Let me know if there is anything else I can do to help.

For the record after finishing this post I went ahead and saved my manual change to the script that I did via the UI for the above info and it worked when I tested it again. I realize I have a work around but the wizard is an important feature for maintenance. I'm ok if the fix isn't quick as long as it can be added to the to do list.

Thank you,
Brandon

Hi @inedo-engineer,
In working on my project I set up a build for a .NET 6 application. I used the .NET Build Wizard and I selected to use IBS (Image Based Service). This worked great and I don't have to worry about the build server having every version of the .NET SDK we use installed, at least for that step. Now, I'm not sure what would happen if I used the option to run the unit test from within the wizard, but I couldn't because I need to pass in a filter for the tests. Due to that I created a manual script that simply just runs the unit tests with the filter. I found that there was no IBS option on DotNet::Test. I'm hoping you can add that to the list of future to dos (and hopefully not to far out). Because I had already created a BuildMaster extension I went ahead updated it to add a custom version of DotNet::Test that added that property and executed it appropriately. Took me about 15 minutes. I was hoping with it being that easy and straightforward you wouldn't mind making it an official feature.

Thank you,
Brandon

Hi @inedo-engineer,
I'm starting to set up Image-based Services to keep from having to have so many things installed on the build server. This is working great for the .NET builds but when I tried to use it for npm::Install I ran into a problem. Apparently when you activate Imaged-based Services for npm::Install it tries to execute at the root of the container which fails with Tracker "idealTree" already exists. According to my research when you the docker run command you need an additional argument of "<workdir>:/var/buildmaster-ibs" but I'm not sure how to do that with your software. I was hoping someone could give me instructions or maybe report this as a bug to be fixed.

Thank you,
Brandon

Hi @stevedennis,
I appreciate the reply but I will be honest and say it doesn't really make any sense. To my knowledge I'm not using docker desktop for this feature. I installed WSL on my machine and I'm assuming it is using that. One of the things I learned in this process is that docker desktop doesn't allow the same command line usage that WSL does. I still have Docker Desktop as well, but I'm using that for running the results of what BuildMaster is building, not anything BuildMaster itself is doing.

As far as the Id command and git, I've always had git installed. Apparently the directory with that utility is not part of the normal path. There is another directory in the install of git that is part of the path but it doesn't include the Id command. I just added the other directory to the path manually.

Either way, the question I was trying to get answered was regardless of my set up, what is the requirements for someone trying to use this feature as expected. From my digging the Inedo code is trying to run a Linux command (Id) on the box hosting the agent (not a docker container). The code is trying to get a user to apparently use in running the docker command. This is where I was hoping you or someone at Inedo could fill in the gaps.

I just want to be able to tell my company that if they want to use that feature should the have an agent running an Linux box (VM or a real one). Good news is I at least proved it "can" run on a windows box.

Thank you,
Brandon