Settings and activity

  1. 14 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Product Feedback » Deployments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Jerry Nothstine commented  · 

    We have a similar issue where we have multiple packages that all are required for a single deployment. Would love to be able to download all of them in a single step instead of having to have multiple steps.

    Jerry Nothstine supported this idea  · 
  2. 6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Product Feedback » Deployments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Jerry Nothstine supported this idea  · 
  3. 27 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Product Feedback » Deployments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Jerry Nothstine commented  · 

    I have almost exactly the same problem. I have multiple customer code bases and generate a different nuget package from each custome (customerA.nupkg, customerB.nupkg) Each package is different than the other and is released at different times with different version numbers. When I create a release for a project, it has to know the customer name so it can get a list of all the versions of the nuget package for that customer. With the multiple tenant feature, this doesn't work because when I create the release, I don't know the customer name.

    Maybe it would be better to select the nuget packages when I deploy to a specific tenant so I could pick the nuget package then. Once a create a deployment, I would want that deployment to always use the nuget package that was selected when it was first created.

    Jerry Nothstine supported this idea  ·