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!

    Reference Pipeline Server(s) in Deployment Plan

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

      I'm currently configuring Buildmaster applications to have a one-to-one deployment plan to pipeline stage configuration, but I'm interested in leveraging the fact that pipeline stages can reference servers.

      How do deployment plans interact with pipeline stage servers? For example, if I want a deployment plan to deploy an artifact to a remote server -- how do I tell it to deploy to whatever server(s) are defined in the pipeline stage?

      Thank you!

      Product: BuildMaster
      Version: 5.6.7

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

        Any servers in the pipeline stage target is functionally equivalent to:

        foreach server in @TargetServers
        {
            # the plan being executed...
        }
        
        1 Reply Last reply Reply Quote 0
        • ? This user is from outside of this forum
          Guest
          last edited by

          A slice of my build plan looks like this:

          #Deploy Artifact
          
          foreach server in @TargetServers
          {
              Deploy-Artifact Webcode
              (
                  To: $webroot
              );
          
              Exec
              (
                  FileName: /bin/chmod,
                  Arguments: -R -f a+rwx $writeabledirectories,
                  WorkingDirectory: $webroot
              );
          }
          
          I'm receiving the following error:
          
          ERROR: Could not resolve variable @TargetServers.
          
          1 Reply Last reply Reply Quote 0
          • ? This user is from outside of this forum
            Guest
            last edited by

            What I'm saying is, your plan is automatically wrapped with the equivalent of that foreach statement (@TargetServers is not an actual function, it was just an example). So if the entirety of your plan is:

            Log-Debug Displaying server name...;
            Log-Information `$ServerName = $ServerName;
            

            and if the stage targets 3 servers (for example Server1, Server2, Server3), the execution logs will be:

            DEBUG: Displaying server name...
            INFO : $ServerName = Server1
            DEBUG: Displaying server name...
            INFO : $ServerName = Server2
            DEBUG: Displaying server name...
            INFO : $ServerName = Server3
            
            1 Reply Last reply Reply Quote 0
            • ? This user is from outside of this forum
              Guest
              last edited by

              That makes much more sense! Thank you for the clarification. So I effectively do not need to specify targets in any of the Buildmaster actions that would require that information.

              Thanks for your help Tod

              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