Inedo Community Forums Forums
    • Recent
    • Tags
    • Popular
    • Login

    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!

    Expectations of a resource monitor set to "Create a build in a release"

    Scheduled Pinned Locked Moved Support
    3 Posts 2 Posters 4 Views 1 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • B Offline
      brandon_owensby_2976
      last edited by

      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

      atrippA 1 Reply Last reply Reply Quote
      • atrippA Offline
        atripp inedo-engineer @brandon_owensby_2976
        last edited by

        Hi @brandon_owensby_2976 ,

        This is indeed by design. You've got two active releases that are associated with a single branch. So, a commit to that branch will trigger builds in both releases.

        From a best practices standpoint, you should not start new development work on a branch that is being validated for production. If there's an issue detected during testing, fixing that would involve undoing the new work and/or incorporating even more changes in the pipeline.

        Your best bet is to not have multiple releases targeting the same branch. If you want to start on a "new release to start new work" while a current release is in the pipeline, I would just create a branch in Git and work off that.

        Otherwise, I can't think of a work-around here without using some complex/convoluted scripting. There's just no way to programmatically "know" which release the commit was intended for.

        Hope that helps,

        Alana

        B 1 Reply Last reply Reply Quote
        • B Offline
          brandon_owensby_2976 @atripp
          last edited by

          @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

          1 Reply Last reply Reply Quote

          Hello! It looks like you're interested in this conversation, but you don't have an account yet.

          Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

          With your input, this post could be even better 💗

          Register Login
          • 1 / 1
          • First post
            Last post
          Inedo Website Home • Support Home • Code of Conduct • Forums Guide • Documentation