Jx: Set the --prefix= argument on the Jenkins command line when using exposecontroller $PATH.

Created on 25 Jun 2019  路  7Comments  路  Source: jenkins-x/jx

Summary

When using the exposecontroller flag and setting a $PATH the --prefix= argument should also be set to include that same path inside of Jenkins

Steps to reproduce the behavior

Use the --exposecontroller-pathmode=path --domain=myhost.testing.com, the expected URL is as expected and the Nginx ingress recognizes the URL prefix, however Jenkins does not. This is creating a myvalue.yaml file that sets "jenkins.Master.JenkinsUriPrefix: /jx/jenkins"

Expected behavior

The URI prefix also gets set with the same path

Kubernetes cluster

local

areinstall arejenkins kinbug lifecyclrotten prioritimportant-longterm

Most helpful comment

Issue https://github.com/jenkins-x/jx/issues/1664 looks to be related.

All 7 comments

Issue https://github.com/jenkins-x/jx/issues/1664 looks to be related.

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://jenkins-x.io/community.
/lifecycle stale

/remove-lifecycle stale

Removing label because this is still relevant but people have just not gotten to the fix

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://jenkins-x.io/community.
/lifecycle stale

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://jenkins-x.io/community.
/lifecycle rotten

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://jenkins-x.io/community.
/close

@jenkins-x-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://jenkins-x.io/community.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository.

Was this page helpful?
0 / 5 - 0 ratings