Determine NuGet feed dependent on Environment
FEED1 populated by the output from the build system
FEED2 populated by QA choosing version required from FEED1
FEED3 populated by QA approving a version from FEED2
A project draws from the FEEDs as follows
Integration from FEED1
QA from FEED2
UAT from FEED3
Producton from FEED3
Could be done as part of project configuration, so when setting up a project you define the feed for each environment
Or could be done at point of deployment, but this potentially allows incorrect feeds to be used
Sean Hederman commented
But there should be a capability for an approval process. Not anyone can deploy packages willy-nilly in a controlled environment. If not this, then maybe some kind of constraint system on what packages can go into what environments, maybe a "deploy quality" field?
Piers Williams commented
I too am looking for better support for 'parallel' deployment streams in Octopus (to handle branches), but I don't think the above is the way to achieve this. Fundamentally, part of Octopus' philosophy (and one I totally agree with) is that packages should be environment-neutral, and you should 'pick up' the same package the users signed off on and push it into production. In the example above, that doesn't seem to apply.