We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Install or upgrade a JX in the current namespace
Which would clone & do the helm install/update.
We could get clever and check if the ‘init’ command is required and run that?
Also if no kubectl context we could prompt the user to create a kube cluster.
Should use this (unless in batch mode) https://github.com/AlecAivazis/survey
To let the user know the cluster / context / namespace to be installed.
In one click can accept the defaults or use the completion to switch contexts or enter a new namespace
The text was updated successfully, but these errors were encountered:
Merge pull request jenkins-x#2 from dwnusbaum/NGPIPELINE-161
bba3311
Handle fan-in/fan-out for workspaces with nested and parallel stages
Merge pull request jenkins-x#2 from garethjevans/1_13
614342c
chore: bump go to 1.13
rawlingsj
No branches or pull requests
Install or upgrade a JX in the current namespace
Which would clone & do the helm install/update.
We could get clever and check if the ‘init’ command is required and run that?
Also if no kubectl context we could prompt the user to create a kube cluster.
Should use this (unless in batch mode)
https://github.com/AlecAivazis/survey
To let the user know the cluster / context / namespace to be installed.
In one click can accept the defaults or use the completion to switch contexts or enter a new namespace
The text was updated successfully, but these errors were encountered: