Hello,
our developers report a inconvenient issue with Octopus.
When someone wants to redeploy application, and project require only tenants deployments, developers need to remove tenant and add it again. Then Deploy button is enabled.
I tested your flow on Octopus and It looks ok.
But when you go to Releases -> Specific release version you can see a redeploy buttons on each environments. When you click Redeploy, then you can observe situation described above.
I’m wondering if there may be a UI bug in the build that you’re running that causes the tenant to appear in the UI but not actually be loaded, which is why the deploy button remains greyed out until you remove and re-add.
I believe that the tenant box should be blank, which is what I’m seeing.
I’ll spin up a test environment on the same build as you and see if I can reproduce the behaviour, at least then you can be sure that an upgrade would resolve it.
I also figure out another very weird correlation. When we have two different releases:
and
Redeploy works only in release 0.120.0 for DEV, but not for rest other TEST, STAGE, PROD. When I pushed deployment in release 1.120.1-pjn-test to TEST. Then deploy button is active and works for DEV and TEST in 0.200.0.
Would I be correct in thinking that this project only has a single tenant associated with it?
If so, I believe I’ve found the problem. It looks like when a project only has a single tenant linked, Octopus will try to be helpful and automatically select that tenant whenever that deploy screen loads.
It seems that for some reason this auto-picking is causing problems with the re-deploy screen. I’m unsure why some releases work and some don’t but it should be enough for our engineers to investigate further.
In the meantime, the best workaround may be to click into the last deployment and use the re-deploy button there rather than using it on the release screen. That does look like it works everytime.