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!

    Deploy Configuration File according to server environment

    Scheduled Pinned Locked Moved Support
    buildmaster
    3 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

      One of the more powerful improvements to the latest Buildmaster is the relationship between pipelines and deployment plans. It dramatically simplifies things here at TLG for code deployment orchestration.

      I'm able to deploy webcode in a deployment plan and allow the pipeline configuration decide where it needs to go based on what environment stage I'm in.

      I'm wondering if this also extends to configuration variables.

      For example, my aforementioned scenario of webcode and pipeline stages might have the set of stages {dev,qa,staging,production}. An application using that pipeline could have a deployment file called example.config with the set of environments {dev,qa,staging,production} (the same as the pipeline).

      Can I call a 'deploy config file' action and let the pipeline stage and associated environment pick the corresponding config file instance?

      This feature would really bring the end-to-end deployment process full circle for our organization!

      Product: BuildMaster
      Version: 5.6.8

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

        Are you referring to the Configuration Files stored in the Assets portion of the application? If so, as long as the instance name of the configuration files matches the environment name set in the pipeline stage... the following operation should do what you want:

        Deploy-ConfigFile
        (
            ConfigFileName: example.config,
            Instance: $EnvironmentName,
            To: E:\Path\to\targetDir
        );
        
        1 Reply Last reply Reply Quote 0
        • ? This user is from outside of this forum
          Guest
          last edited by

          This is exactly what I was looking for, thank you!

          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