Skip to content

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

Open
@ryanrichter94

Description

@ryanrichter94

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

Metadata

Metadata

Assignees

Labels

0 - _TriagingNew tickets that need to be hashed out a bit more before they hit the backlog.BreakingChangeA breaking change requires a major version bump (pre v1 does not apply in the same way).EnhancementEnhancements are things that are improvements or features.Priority_LOWRepresents tickets that are of lower priority and can be taken care of whenever.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions