You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have pre-installed JX on AWS and I want to add regular Jenkins to execute my automation tests on. I followed the instructions from the official JX page: https://jenkins-x.io/v3/admin/guides/jenkins/getting-started/
After executing: jx gitops jenkins add --name regularjenkins it looks like all new files were created:
New regularjenkins directory under helmfiles with hemlfile.yaml and values.yaml
New entry in .jx/gitops/source-config.yaml containing the following:
jenkinsServers:
- server: regularjenkins
After pushing these changes Kubernetes did its thing and jx-values.yaml appeared under helmfiles/regularjenkins and new namespace was created.
Still following the guide I managed to switch to the new namespace running jx ns myjenkins
and am able to get the information about the new service running kubectl get ing: jenkins <none> jenkins-regularjenkins.jx3.y-tree.uk a1d98d608ebc746f6ae9b57bb6a06aab-f1d753675891d386.elb.eu-west-2.amazonaws.com 80 21h
Obtaining the URL also works:
echo http://`kubectl get ingress jenkins -o jsonpath="{.spec.rules[0].host}"`
But if I try to obtain the admin password I get an error that it can't be found (we are using Vault to store our secrets): kubectl get secret jenkins -o jsonpath="{.data.jenkins-admin-password}" | base64 --decode
Also, when I try to open the Jenkins server URL I receive from the command above, I get 503.
Octant also displays Jenkins but its constantly loading something:
The text was updated successfully, but these errors were encountered:
I have pre-installed JX on AWS and I want to add regular Jenkins to execute my automation tests on. I followed the instructions from the official JX page:
https://jenkins-x.io/v3/admin/guides/jenkins/getting-started/
After executing:
jx gitops jenkins add --name regularjenkins
it looks like all new files were created:regularjenkins
directory underhelmfiles
with hemlfile.yaml and values.yamlAfter pushing these changes Kubernetes did its thing and jx-values.yaml appeared under helmfiles/regularjenkins and new namespace was created.
Still following the guide I managed to switch to the new namespace running
jx ns myjenkins
and am able to get the information about the new service running
kubectl get ing
:jenkins <none> jenkins-regularjenkins.jx3.y-tree.uk a1d98d608ebc746f6ae9b57bb6a06aab-f1d753675891d386.elb.eu-west-2.amazonaws.com 80 21h
Obtaining the URL also works:
But if I try to obtain the admin password I get an error that it can't be found (we are using Vault to store our secrets):
kubectl get secret jenkins -o jsonpath="{.data.jenkins-admin-password}" | base64 --decode
Also, when I try to open the Jenkins server URL I receive from the command above, I get 503.
Octant also displays Jenkins but its constantly loading something:
The text was updated successfully, but these errors were encountered: