Jx: Node quickstart application failed on the build step

[CloudGrimm]

I was trying out the node jx quickstart application and the following error happened:

The push refers to a repository [10.43.252.130:5000/cloudgrimm/node-http]

8ce8620635bc: Preparing

e52c79d3930a: Preparing

584ff91e2110: Preparing

708f04a53c2f: Preparing

f8fa530deadc: Preparing

367669efa30c: Preparing

8fd847ca0bf3: Preparing

367669efa30c: Waiting

8fd847ca0bf3: Waiting

584ff91e2110: Layer already exists

708f04a53c2f: Layer already exists

f8fa530deadc: Layer already exists

e52c79d3930a: Layer already exists

367669efa30c: Layer already exists

8fd847ca0bf3: Layer already exists

8ce8620635bc: Pushed

0.0.2: digest: sha256:34dce157309a58e4d7e5e06fd363cc9a1a2f7d1bb892caf12ffc4f814d246749 size: 1786

Build complete in 734.882064ms

Starting deploy...

time="2018-07-03T11:16:28Z" level=warning msg="image [changeme] is not used by the deployment"

error: no objects passed to apply

time="2018-07-03T11:16:28Z" level=fatal msg="deploy step: deploying manifests: exit status 1"

script returned exit code 1

[beerkeeper]

I have the same issue, both on NodeJS projects as on Gradle projects.

The command running prior to failing is skaffold run -f skaffold.yaml.
The skaffold.yaml doesn't look different with older generated versions, so I can't explain what's happening differently here.

[CloudGrimm]

could be a bug in the jx create quickstart not correctly replacing strings in the source? you on a recent jx version. Tryjx upgrade cli then run the jx import command if it doesnt work trying installing Jenkins X again following the respective system you working with then check if the jx version is the recent release.

[rawlingsj]

Any chance you can provide a bit more info so we can recreate and fix please? Is the git repo public? I wonder if we can take a look. Also what is the name of the application you created? Was there an uppercase char or anything else you can think that might be different from other projects? Thanks.

[beerkeeper]

@rawlingsj

It is actually the same issue as this person: https://github.com/jenkins-x/jx/issues/1209 (it was already referenced I see, my bad)
I used this project (https://github.com/beerkeeper/test-reactjs) which worked fine like roughly two weeks ago.
The command jx import created all the files necessary and it build/deployed.

Now, same project, this build fails on Jenkins-X. Too bad I recreated the Jenkins-X installation so I can't see older logs.
I do think I recall that the following lines didn't show up when it was building properly:

time="2018-07-03T11:16:28Z" level=warning msg="image [changeme] is not used by the deployment"
error: no objects passed to apply

But the skaffold.yaml file (with older and more recent jx import) did contain the imageName: changeme line.

Has something changed with the implementation of skaffold?

[ryandawsonuk]

I hit this error too after upgrading my jx platform version to 0.0.1677. @jstrachan advised me that the skaffold version in jx has been upgraded and now any Jenkinsfiles that use skaffold run should instead do skaffold build. My pipeline runs again after that change.

[jstrachan]

Btw yeah, we’re now on skaffold 0.9.0 and so should use skaffold build

[beerkeeper]

Thanks! After your suggestion (and actually upgrading Jenkins-X on kubernetes and recreating the buildfiles) it works like a charm!

[jstrachan]

@beerkeeper thanks for letting us know!