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!

    DeployableName variable not being set

    Scheduled Pinned Locked Moved Support
    buildmaster
    4 Posts 3 Posters 2 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.
    • J Offline
      jstarbird_7831
      last edited by

      I have an app I am working with right now and the DeployableName is no longer being set unless I specify in the top of plan. I was told before that I did not need to set a plan to a specific deployable.
      Is that the case? Is this a bug?

      This app only has 1 Deployable set and it is set to the release.
      The Release Template also has it set to this deployable as the default.

      Product: BuildMaster
      Version: 5.6.11

      1 Reply Last reply Reply Quote 0
      • benB Offline
        ben inedo-engineer
        last edited by

        Hello Jon,

        There is no deployable set in OtterScript deployment plans unless the execution is inside a for deployable DeployableName block. (for deployable blocks are displayed as General blocks in the visual editor.) Deployables use a separate working directory from the rest of the execution by default.

        The person who told you you don't need to set the deployable may have meant that your plan doesn't need deployables. Deployables are just for organization, so you can think of deployables as folders. Everything that isn't in a deployable goes into one folder, and each deployable is a separate folder next to the default one.

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

          Thanks for the info.

          The way it was explained before was that since the plan was executing under that App then it would use the default deployable set for that release unless otherwise specified to use a different one.

          This was a new app setup so all my other apps/plans had it set anyway so not a major thing for me I just wanted to clarify.

          1 Reply Last reply Reply Quote 0
          • benB Offline
            ben inedo-engineer
            last edited by

            Ah, I think the confusion here is because of the different meanings of the word "set".

            If you don't select the deployables in the release template, it will have the default deployables available in executions. That is, if you do for deployable Foo and Foo is a deployable in the application, it will execute the code inside the block.

            However, you can select specific deployables for a release and the for deployable Foo block will only be run if Foo is selected.

            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