Closed kshultzCB closed 5 years ago
You've got to install https://github.com/jenkins-x/jx-release-version (i.e., go get -u github.com/jenkins-x/jx-release-version
) to make this work. Though I recommend running that from somewhere not in a repo, 'cos it can mess up go.mod
, I think?
All fixed up now. Thanks @abayer .
Is that new? It might not be. Liam and I were looking at my environment and there was some pretty oddball stuff going on.
Summary
After successfully creating a golang-http quickstart, I change directories into that directory. When I issue
jx step create task
, the command fails. It appears to be looking for environment variables with-
s in their names, which aren't legal in bash.Steps to reproduce the behavior
Given a working JX, create a quickstart. In my particular case, I did
jx create quickstart --git-provider-url=https://github.my-company.com
and picked the golang-http quickstart when prompted.Once complete, CD into the directory where your quickstart was created.
Run
jx step create task
Expected behavior
The
jx step create task
command should proceed as expected, triggering a new pipeline run.If there's something wrong with running
jx step create task
at this point in time, a useful explanation should be provided as to why.Actual behavior
The pipeline does not get run.
The error messages describe variables and commands which are not what the user just ran. For example, Getting an error back about
jx step tag
having a problem, when the command I actually ran wasjx step create task
, is a confusing experience.The script appears to be looking for an environment variable, named
jx-release-version
, which is not found:And that variable is unlikely to be settable anyway, because bash doesn't like environment variables with
-
characters in their names. Even setting this manually fails:Jx version
The output of
jx version
is:Jenkins type
Kubernetes cluster
GKE, set up using
jx create cluster gke --tekton
Operating system / Environment