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

Jenkins plugin won't render spaces selector if default Octopus connection is broken #105

Open
4 tasks done
twerthi opened this issue Apr 28, 2020 · 1 comment
Open
4 tasks done
Labels

Comments

@twerthi
Copy link

twerthi commented Apr 28, 2020

Are you a customer of Octopus Deploy? Don't raise the issue here. Please contact our support team so we can triage your issue, making sure it's handled appropriately.

Prerequisites

  • I have verified the problem exists in the latest version
  • I have searched open and closed issues to make sure it isn't already reported
  • I have written a descriptive issue title
  • [] I have linked the original source of this report
  • I have tagged the issue appropriately (area/*, kind/bug, tag/regression?)

The bug

If the default Octopus Server connection in Jenkins encounters an error, such as a 403, the spaces selector will not render. If you switch the connection in your build definition to a connection that works, the spaces selector will not render. If you save, then come back into the build definition with a functional connection, the spaces selector will not render.

What I expected to happen

  • While adding a step that uses an Octopus Server connection, the spaces selector should render when I switch from once connection to another.

  • When editing an existing build definition that uses a connection other than default, the spaces selector should render.

Steps to reproduce

  1. Define multiple Octopus Deploy plugin connections, one with a 403 error

  2. Move the broken connection to the top of the list

  3. Edit a build definition and add a Push packages to Octopus step

  4. Spaces selector will not render

  5. Change the Octopus Server in the Octopus Connection section to a functional connection

  6. Spaces selector will not render

  7. Move functional connection to the top of the list to make it the default.

  8. Edit a build definition and add a Push packages to Octopus step

  9. Select a space

  10. Save build definition

  11. Manage Jenkins and move the broken connection to the top of the list

  12. Edit the definition you just saved

  13. The spaces selector is no longer rendered

Affected versions

Octopus Server:

Workarounds

Changing the order of the connections so the one that's working is the default connection.

Links

@mcasperson
Copy link
Contributor

Hi @twerthi ,

I just wanted to reach out and let you know that we have flagged this as an issue with product, but at this point we do not have capacity to assign an engineer to resolve the issue. We'll keep the issue open, but unfortunately we can not provide any guidance as to when it will be resolved. I'm sorry for the inconvenience, and we do appreciate that you took the time to report the issue.

Regards Matt

@kengel100 kengel100 transferred this issue from OctopusDeploy/Issues Apr 22, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants