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

    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

    brandon_owensby_2976

    @brandon_owensby_2976

    1
    Profile views
    50
    Posts
    0
    Followers
    0
    Following
    Joined
    Last Online

    brandon_owensby_2976 Unfollow Follow

    Latest posts made by brandon_owensby_2976

    • 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