问题
I have set up a deployment in Octopus with the intention of blue/green deployments. I have tried two different approaches but neither of them seem to be taking any notice of the slot I have set up for it.
The two approaches are:
- deploy to staging
- swap slots
or
- deploy to staging
- deploy to production
for both of these I have the Deployment Slot set:
but neither deploy seems to take any notice of it. If I change the name to anything else i.e. -stagingslot the deployments fail. The logs I get appear to show that the deploymnet has been sucessful:
10:16:37 Info | Name : DevemoTestSlots/stagingslot 10:16:37 Info | Location : West Europe 10:16:37 Info | Type : Microsoft.Web/sites/slots 10:16:37 Info | Tags : 10:16:37 Info | Virtual Directory Config at end of Deployment: 10:16:37 Info | VirtualPath : / 10:16:37 Info | PhysicalPath : site\wwwroot 10:16:37 Info | PreloadEnabled : True 10:16:37 Info | VirtualDirectories : 10:16:37 Info | Releasing Mutex : DevemoTestSlotsstagingslot 10:16:37 Verbose | Successfully finished Deploy Staging Slot on the Octopus Server
The only issue I can think of at this point is that the DevemoTestSlotsstagingslot shows up as devemotestslots-stagingslot in the dashboard. As I said any alteration in the deployment causes a failure.
Any help targeting the slot will be appreciated.
来源：https://stackoverflow.com/questions/52588964/cant-target-staging-slot-octopus