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.

Sign up for GitHub

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

Jump to bottom

Auto-deployed release gets 'Octopus.Deployment.CreatedBy' assigned as the system user #3523

Closed
hnrkndrssn opened this issue May 25, 2017 · 2 comments
Closed

Auto-deployed release gets 'Octopus.Deployment.CreatedBy' assigned as the system user #3523

hnrkndrssn opened this issue May 25, 2017 · 2 comments
Assignees
@hnrkndrssn
Labels
feature/elastictransientenvironments kind/bug This issue represents a verified problem we are committed to solving
Milestone
3.16.3

Comments

@hnrkndrssn
Copy link

hnrkndrssn commented May 25, 2017 •
edited

Steps to reproduce:

  1. Configure Lifecycle to auto-deploy to environment
  2. Assign Lifecycle to your project
  3. Create a release for your project
  4. Observe that Octopus.Deployment.CreatedBy is assigned the SystemUser

Source: http://help.octopusdeploy.com/discussions/problems/54728-which-octopus-variable-holds-the-deployer-username
@hnrkndrssn hnrkndrssn added area/execution kind/bug This issue represents a verified problem we are committed to solving labels May 25, 2017
@hnrkndrssn hnrkndrssn changed the title Deployment ServerTask should use the CreatedBy user from the created Deployment Auto-deployed release gets 'Octopus.Deployment.CreatedBy' assigned as the system user May 26, 2017
@octoreleasebot octoreleasebot added this to the 3.16.3 milestone Aug 18, 2017
@octoreleasebot
Copy link

Release Note: Deployments triggered by auto-deploy environment in lifecycle should be assigned the user that created the release

@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.
Assignees

@hnrkndrssn hnrkndrssn

Labels
feature/elastictransientenvironments kind/bug This issue represents a verified problem we are committed to solving
Projects
None yet
Milestone
3.16.3
Development

No branches or pull requests
3 participants
@hnrkndrssn @droyad @octoreleasebot