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

Look Into Appending /nexus and /jenkins to Service Hosting URLs #205

Open
2 tasks done
ryanrichter94 opened this issue Jul 14, 2023 · 1 comment
Open
2 tasks done
Labels
0 - _Triaging New tickets that need to be hashed out a bit more before they hit the backlog. BreakingChange A breaking change requires a major version bump (pre v1 does not apply in the same way). Enhancement Enhancements are things that are improvements or features. Priority_LOW Represents tickets that are of lower priority and can be taken care of whenever.

Comments

@ryanrichter94
Copy link
Member

Checklist

  • I have verified this is the correct repository for opening this issue.
  • I have verified no other issues exist related to my request.

Is Your Feature Request Related To A Problem? Please describe.

Look into appending /nexus onto the nexus URL endpoint and adding a /jenkins to the jenkins URL.

Describe The Solution. Why is it needed?

Currently the Azure enviornment uses this approach. Adding /nexus to the context path in the the nexus default properties file locally. They also add a --prefix=/jenkins into the arguments section of the jenkins.xml file.

Considering doing the same change on QSG to bring them more in line with each other as enviornment solutions.

Additional Context

The difference between them would still be that QSG would run CCM, Jenkins, and Nexus over 3 different ports. Where as the C4BAE routes them all through the app gateway as 443 traffic. Effectively using the app gateway like a reverse proxy & load balancer.

Related Issues

No response

@ryanrichter94 ryanrichter94 added the Enhancement Enhancements are things that are improvements or features. label Jul 14, 2023
@ryanrichter94 ryanrichter94 self-assigned this Jul 14, 2023
@ryanrichter94 ryanrichter94 added the 0 - _Triaging New tickets that need to be hashed out a bit more before they hit the backlog. label Jul 14, 2023
@ryanrichter94
Copy link
Member Author

@JPRuskin @steviecoaster @imm0rtalsupp0rt Feel free to chime in on opinions to this proposed change.

@ryanrichter94 ryanrichter94 removed their assignment Feb 2, 2024
@ryanrichter94 ryanrichter94 added BreakingChange A breaking change requires a major version bump (pre v1 does not apply in the same way). Priority_LOW Represents tickets that are of lower priority and can be taken care of whenever. labels Jun 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0 - _Triaging New tickets that need to be hashed out a bit more before they hit the backlog. BreakingChange A breaking change requires a major version bump (pre v1 does not apply in the same way). Enhancement Enhancements are things that are improvements or features. Priority_LOW Represents tickets that are of lower priority and can be taken care of whenever.
Projects
None yet
Development

No branches or pull requests

1 participant