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!

    Workflow using nugetpackage. Use different feeds for different deployment domain

    Scheduled Pinned Locked Moved Support
    progetworkflowsgitdeployablesbuildmaster
    2 Posts 2 Posters 11 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.
    • T Offline
      tbl_5153
      last edited by

      This is our setup.
      On build in JEnkins we create a deployable nuget package that is published to Proget.

      We use GitFlow, thus all development not done on master or hotfix, will create a nuget artifact that is published to a feed named Development.

      Any code pushed to out Master branch in git will, via Jenkins, create a nuget artifact on a feed named Production.

      Problem.
      In BuildMaster (from now on named BM), when you setup a workflow you define a Buildstep.
      In this buildstep we retrieve the nugetpackage.
      But the buildstep is used for all the deployment domain.
      We deploy to domains named: Development, Staging, Production.

      We want a package on the Proget feed Development to be deployed in the deployment domain Development ONLY.
      The deployment domains, Staging and Production, should use the Proget feed Production.

      Currently i do not see this as something that is possible, but i am also a BM beginner and we are looking at BM as our Continues Deployment system along with other alternatives .
      I really need to know if this is possible or how i can make it work.
      Regards
      For us this is a very important feature.
      Regards

      Product: BuildMaster
      Version: 4.9.6

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

        You could use a different workflow (or in v5, "pipelines" as they will be called)... and then have a different build importer/feed on each. Alternatively, you could not use the build importer, and just have a build step download the package and incorporate it as an artifact.

        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