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

Duplicate variable name between Step Template and Project might cause confusions #2126

Closed
Dalmirog-zz opened this issue Nov 9, 2015 · 4 comments
Assignees
Labels
feature/usability kind/enhancement This issue represents an enhancement we are committed to adding to Octopus as some time
Milestone

Comments

@Dalmirog-zz
Copy link

If a variable is configured on a Step template with the same name as a variable on a Project/Variable Set level, the latter will prevail regardless of the value entered by the user on the step fields. This has confused a couple of users already.

We could improve this by adding a warning that says "You have duplicate variable names between the Step Template [name] and your Project or Variable Sets in use. Be aware that the latter will prevail over the values entered on the step"

@michaelnoonan michaelnoonan added kind/enhancement This issue represents an enhancement we are committed to adding to Octopus as some time feature/usability labels Nov 11, 2015
@zentron zentron assigned zentron and unassigned zentron Nov 25, 2015
@zentron zentron added ready and removed in progress labels Nov 26, 2015
@hnrkndrssn hnrkndrssn self-assigned this Dec 11, 2015
@hnrkndrssn hnrkndrssn removed their assignment Dec 14, 2015
@robpearson robpearson self-assigned this Dec 15, 2015
@robpearson
Copy link

Release Note: Added Verbose Logging when duplicate variables exist between Step Template vars and Project/VariableSet vars.

@eakoning
Copy link

Wouldn't it be possible to add a variable, just like the ones for debugging variables in Octopus Deploy to generate a warning instead of a verbose log message. Now you will see a green check mark in the dashboard and without actually explicitely opening the verbose log, you'll just never know something may have gone sideways.

@robpearson
Copy link

@eakoning This was shipped a fair time ago so it's probably a good idea to contact Octopus support if you'd like to follow-up. :)

@lock
Copy link

lock bot commented Nov 24, 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 locked as resolved and limited conversation to collaborators Nov 24, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feature/usability kind/enhancement This issue represents an enhancement we are committed to adding to Octopus as some time
Projects
None yet
Development

No branches or pull requests

7 participants