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!

    DeployableId Discrepency in Deployment Plan

    Scheduled Pinned Locked Moved Support
    buildmaster
    2 Posts 1 Posters 0 Views
    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.
    • ? This user is from outside of this forum
      Guest
      last edited by

      I believe there is a bug that causes an action group to lose its DeployableId or have it reset to zero.

      I have not been able to pin down the precise circumstances, but the symptom which I have encountered is that I have one Action Group that, for example, gets labeled source and sets Assembly versions attributes. I then have another action group which builds the source. I sometimes find that the first action group has its work and source directory set differently to the second.

      In the case I had to today was it was _SVCTMP_A14_S0 and _SVCTMP_A14_S16. When I exported the Deployment plan I could see that there was no DeployableId="16" for the action group in question. Adding this and reimporting the plan solved the problem.

      I not sure how the DeployableId got lost/reset - possibly because I copied the action group from another deployment plan, perhaps because I already had one of the same name in the deployment plan?

      Product: BuildMaster
      Version: 4.1.3

      1 Reply Last reply Reply Quote 0
      • ? This user is from outside of this forum
        Guest
        last edited by

        This can sometimes happen if you import a plan from an application that only has a single deployable. It is possible that a deployment plan could be created without being assigned to a deployable, and since applications with a single deployable are designed to hide deployables from the UI, it's difficult to determine what would have caused this.

        From the UI, the easiest way to ensure that the correct deployables are assigned to an action group is to add a 2nd "dummy" deployable that will re-enable the ability to see assigned deployables from the UI perspective. This will then display the deployable name on the action group as it did before v4.0.

        1 Reply Last reply Reply Quote 0

        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