Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Have $OctopusParameters['Octopus.Release.Previous.Number'] be environment-aware #1496

Closed
Dalmirog opened this issue Feb 26, 2015 · 3 comments
Milestone

Comments

@Dalmirog
Copy link

@Dalmirog Dalmirog commented Feb 26, 2015

Currently the variable $OctopusParameters['Octopus.Release.Previous.Number'] gets the previous release created. Scenario:

Dev - Has release 3.0.0
Stage - Has 3.0.0
Prod - Has 1.0.0

If we promote Stage's release to Prod, during Prod's deployment the value of this variable will be 2.0.0 instead of 1.0.0 which is the actual previous release number deployed to the current environment (prod).

@DamianMac DamianMac added this to the 3.0 milestone Mar 4, 2015
@DamianMac DamianMac added 2 - Working and removed 1 - In Sprint labels Mar 16, 2015
@PaulStovell PaulStovell modified the milestones: 3.0-pre2, 3.0-pre1 Apr 1, 2015
@PaulStovell PaulStovell modified the milestones: 3.0-pre1, 3.0-pre2 Apr 12, 2015
@Damovisa Damovisa self-assigned this Apr 16, 2015
@Damovisa Damovisa added 2 - Working and removed 1 - In Sprint labels Apr 16, 2015
@Damovisa

This comment has been minimized.

Copy link

@Damovisa Damovisa commented Apr 16, 2015

I'll add a new variable rather than change the behaviour of the existing one. This should avoid any breaking changes.

@Damovisa Damovisa added 3 - Done and removed 2 - Working labels Apr 16, 2015
@PaulStovell PaulStovell removed the 3 - Done label Apr 29, 2015
@vanessalove vanessalove modified the milestones: 3.0-release, 3.0-pre1 Jul 8, 2015
@lock

This comment has been minimized.

Copy link

@lock lock bot commented Nov 27, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately.

@lock lock bot unassigned Damovisa Nov 27, 2018
@lock lock bot locked as resolved and limited conversation to collaborators Nov 27, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
6 participants
You can’t perform that action at this time.