Inedo Community Forums Forums
    • Recent
    • Tags
    • Popular
    • Login
    1. Home
    2. brandon_owensby_2976
    3. Posts

    Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.

    If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!

    B Offline
    • Profile
    • Following 0
    • Followers 0
    • Topics 17
    • Posts 50
    • Groups 0

    Posts

    Recent
    • RE: Expectations of a resource monitor set to "Create a build in a release"

      @atripp

      Shortly after I sent my last response I decided to go back just see what your otterscript had to offer in respect to looking at releases and creating a build. I was surprised to see that if you call create build that the default behavior is to target the latest release which is exactly what I was looking for. Now, I will admit that using that feature doesn't target a specific branch but it still meets the criteria I was looking for and I it allows me to match on pipeline which in this case works basically the same.

      I verified the capability exists in your otter command but I haven't tested it. When I do I'll update the post so any other interested parties will know how it worked and how it could help them do the same thing.

      Thank you,
      Brandon

      posted in Support
      B
      brandon_owensby_2976
    • RE: Expectations of a resource monitor set to "Create a build in a release"

      @atripp

      I'm a little surprised by your response. One of the reasons I love your product is because it makes what you said not true at all. What I mean is that when builds are created you automatically track the commit. When I've seen multiple branches being used (I'm not talking about working branches for PR but branches for stages of releasing) it adds unnecessary complexity and risk with extra merges and what not. What I sell with your product is the need to not worry about that.

      For me I use the master/main branch as the latest version of the code despite whether it is in production or not. Once you finish your work and merge your PR a new build is created for the current version for QA to test out. Repeat for all the tickets in the sprint. Once all the tickets in that sprint are closed you can start the process of finalizing and releasing a of that version of the product. The release has already been built (stored as an artifact) and can even be rebuilt because you have linked the build to the commit. During this time people can start work on the next sprint. Whether work more work has been merged in or not only what was in that last build in the release will be sent to production. When you do send that release to production (you could even do it when you send it to staging or whatever you call the environment you test the release in, if you even use one) you tag the commit with the version number.

      Now if a patch needs to happen on the version in production you just create a patch branch off that tag. Then you create a patch release in Buildmaster using that branch. Once that is complete and released you can then merge it in to master so it is also part of the next main release.

      Now we are not here to talk about all that, but hopefully someone will find it useful. Maybe someone will look at Buildmaster a little differently after all that.

      To get back to the point of this topic we left off with how I could write a script to pick the correct release. You claimed the system wouldn't know and it would make scripting it complicated. However, the way I wrote the requirements, Buildmaster does indeed already know. The only requirement is that it goes on the latest release off that branch. Buildmaster already puts that release at the top. Since it is really that simple that is why I expected my original idea might work but again wasn't surprised it didn't. If that helps you point me to a sample great, if not then no worries.

      Thank you,
      Brandon

      posted in Support
      B
      brandon_owensby_2976
    • Expectations of a resource monitor set to "Create a build in a release"

      I'm testing out the git resource monitor feature and had an unexpected (but not shocking) result. I was testing the scenario of you creating a release it being ready for production but you aren't wanting to to release it just yet but you create a new release to start new work.

      The resource monitor is set to "Create build in a release" and match "Associated with commit branch". I was expecting it to look for the first matching release and create the build there (so hoping it would create the build on the newest release). What ended up happening instead is it created 2 builds, one in each release.

      I totally understand if this is by design but if it isn't I thought you would want to know. If it is, I'm curious if there is a way to make it work the way I said. I don't see it as an unreasonable thing that you will start working on the next release before the previous release is released to production.

      I'm guessing there is a chance you will say I'd have to go the custom script approach, if that is the case do you have any samples with that?

      Thank you,
      Brandon

      posted in Support
      B
      brandon_owensby_2976
    • Setting a local when invoking a command with Image Based Services

      I used Image Based Services when invoking my unit tests. To be clear, I realize you do not technically have the built in yet and I actually opened another note about that in which you opened a ticket for me. What I did in the meantime is I added a custom command to the extensions I built that invokes the same exact code as DotNet::Test it just uses your built in functionality to actually run the command using the Image Based Services and I added a new property for you to select which one to use.

      Even with other commands in which you already had this implemented, however, there is no way to specify local. The default locale for Linux is "invariant" and where this doesn't affect things in a high percentage of the code there are few unit tests where it is look at the returned output that includes say formatted date and that comes out differently. I do get we could update our tests accordingly as well, but when we run the code live we use a docker file that sets the local before it runs the app so we aren't really running the tests in the same way.

      What I would like, is to know if you have some way that I might have missed for handling it. If not I totally understand. The one option I am aware of is to create an image in our on repository that is the base image from IBS with the local added and then point to that in IBS. I haven't tried it yet but in theory it should work, just more to maintain.

      I'm hoping we can put aside opinions on unit testing. I realize we could fix and maybe should fix our unit tests. I do not have control over that and it would likely not look good to say we have to through all our apps and evaluate the unit tests for this solution.

      The other option is fixing it in our extension but if you guys add this feature to the DotNet:Test command then I won't want to use our extension for that command anymore.

      If you don't have anymore options but want to add it as a future enhancement then I'm good with that too.

      Thank you,
      Brandon

      posted in Support
      B
      brandon_owensby_2976
    • RE: Bug Report: Deploy IIS Site generates invalid otter script if you choose Create/Update Application (VM 2026.1)

      @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

      posted in Support
      B
      brandon_owensby_2976
    • RE: Bug Report: Deploy IIS Site generates invalid otter script if you choose Create/Update Application (VM 2026.1)

      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?

      posted in Support
      B
      brandon_owensby_2976
    • RE: Image-based Services (Containerized Builds) failing on "Build .NET Project"

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

      posted in Support
      B
      brandon_owensby_2976
    • RE: Using npm:Install with Image-based Services doesn't work

      Thank you!!!

      posted in Support
      B
      brandon_owensby_2976
    • RE: Feature Request: Allow IBS for DotNet::Test

      Thank you!!

      posted in Support
      B
      brandon_owensby_2976
    • RE: Bug Report: Deploy IIS Site generates invalid otter script if you choose Create/Update Application (VM 2026.1)

      @stevedennis

      Thank you

      posted in Support
      B
      brandon_owensby_2976
    • Bug Report: Deploy IIS Site generates invalid otter script if you choose Create/Update Application (VM 2026.1)

      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:

      86cb4c4b-94ee-4eae-a612-90af444def31-image.jpeg

      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

      posted in Support
      B
      brandon_owensby_2976
    • Feature Request: Allow IBS for DotNet::Test

      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

      posted in Support
      B
      brandon_owensby_2976
    • Using npm:Install with Image-based Services doesn't work

      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

      posted in Support
      B
      brandon_owensby_2976
    • RE: Image-based Services (Containerized Builds) failing on "Build .NET Project"

      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

      posted in Support
      B
      brandon_owensby_2976
    • RE: Image-based Services (Containerized Builds) failing on "Build .NET Project"

      I was finally able to get it to work. I'm not sure how you "expect" it to work so I am curious what you'll say about my solution. After some research I found out that if you install git for windows there is a directory with some utilities which includes an id command for windows as a part of that. I added that directory to my path and the Image based service finally worked. Is there a better way to get this to work? Perhaps this was an oversite in the coding as maybe this is standard on your computers so the the third-party dependency wasn't mentioned? I'll be curious to hear your explanation.

      Thank you,
      Brandon

      posted in Support
      B
      brandon_owensby_2976
    • RE: Image-based Services (Containerized Builds) failing on "Build .NET Project"

      I would like to try and "reopen" this topic. I didn't get back to this right away but I did some more work on this today and I'm curious if someone at Inedo might be able to supply some more details if I provide more details on what I've learned since the last posting.

      I used cursor to try and understand more of what was going on since I wasn't really following everything being said above. What it basically told me was that it has nothing to do with interacting with docker. Apparently when ImageBasedService is used it expects you are using an agent on a Linux machine as your code is explicitly calling the Id method. For the record cursor analyzed your DLLs to try and figure this out. I'm not sure how accurate it is but I'm wondering if it will at least trigger someone on your side to figure out the best way to help me or at least explain to me what is going on and what my options are.

      Here is the code it looked at

      string HostPath = ((!(await exec.GetEnvironmentVariableValueAsync("USER") != "root")) ? null : (await GetCurrentUserIdAsync(exec, context.CurrentLogScope, cancellationToken)));
      

      private static async Task<string?> GetCurrentUserIdAsync(IRemoteProcessExecuter exec, ActiveNamedScope log, CancellationToken cancellationToken)
      {
      using IRemoteProcess p = exec.CreateProcess(new RemoteProcessStartInfo
      {
      FileName = "id",
      Arguments = "-u"
      });
      // ... read stdout, then StartAsync
      }

      code_text
      

      Thank you,
      Brandon

      posted in Support
      B
      brandon_owensby_2976
    • RE: Retention Policies for PR Builds

      Hi @dean-houston,
      I think there might be a little bit of a misunderstanding. I'm not really evaluating the product. I'm selling the product. I've been using BuildMaster for over 10 years (I'm thinking 14 or 15) and most of which as a paying customer. I started a new job last year and I'm once again I've decided to try to sell your product to my employer. Previously I've just had to do a presentation on the product to get the company on board. Here, unfortunately, I need to do a little more show-n-tell rather than talk about the product. Not only that but this is the first place I've worked at that has a workflow quite like it does so it has brought up questions I didn't have to deal with, but I've never had any doubt I could/would accomplish what I needed. Since I know how hard of a sell this will be I'm trying to put extra effort in to coming up with the best demo possible and is leading to some of the questions.

      Thankfully I think I'm near the end of building what I need to build so hopefully will not be doing too many more posts on the forum. I really do appreciate all the time you and others have given to respond to my posts but I do feel a bit bad for how many and how complex my posts of been. Unfortunately I do not really know when I'll finally do the demo/presentation to my superiors, and I am kind of hoping I can wait until 2026 comes out before I do. I hate to sell a product and the version my pitch is based on is no longer the newest :-).

      Thank you,
      Brandon

      posted in Support
      B
      brandon_owensby_2976
    • RE: Retention Policy - Ability to have policy run per group (e.g. Application)

      Hi @dean-houston,

      I totally misunderstood what you wanted to the pull request for (I should have looked at the link closer). I did create one though. I made a few corrections to what I put in this post.

      Thank you,
      Brandon

      posted in Support
      B
      brandon_owensby_2976
    • RE: Retention Policy - Ability to have policy run per group (e.g. Application)

      Hi @dean-houston,
      Thank you for such a quick reply. I guess I didn't see this post as "getting it in the ether" as you would say. Maybe I was wrong about that. Certainly didn't seem to happen with the support ticket 6ish years ago, but that could be the difference been using paid support vs the open forum.

      As far as the documentation goes I can put up an attempt at what it could say, but I'd totally expect it to be edited if it were to be used. The blow can be put as a caution or warning block instead of part of the normal documentation.

      When using the Count feature please note that it does not count per application.  If you have a retention policy that is not restricted by app you can end up purging all releases for certain apps.  You may want creating a retention policy for every app if you intend using this feature.
      

      I will consider looking at the code as well and coming with a suggestion for the implementation of the enhancement I have in mind.

      Thank you,
      Brandon

      posted in Support
      B
      brandon_owensby_2976
    • RE: Retention Policy - Ability to have policy run per group (e.g. Application)

      Hi @dean-houston,

      If nothing else could you at least update the documentation. I complained about this 6 years ago after wiping out nearly all my production builds. I think you should have a warning about the fact that the conditions are not app specific when it talking about the last N item.

      Also, I never asked for a timeline, just the ability to add something for consideration in the future. A lot of companies have a place where you can make a request and even have customers vote on it so they can see the interest before considering it. I just wanted the chance to have it recorded somewhere so it could be considered when you got around to it.

      Thank you,
      Brandon

      posted in Support
      B
      brandon_owensby_2976
    • 1 / 1