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



  • 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



  • 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.



Inedo Website HomeSupport HomeCode of ConductForums GuideDocumentation