New issue

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

First automated promotion to staging is failing #2288

Closed
romainverduci opened this Issue Nov 20, 2018 · 3 comments

Comments

Projects
None yet
4 participants
@romainverduci
Copy link
Member

romainverduci commented Nov 20, 2018

Summary

When creating a new spring boot app and triggering the first pipeline, the promotion to staging is failing.
If we run the master pipeline again, it will be successful.

Steps to reproduce the behavior

  1. jx create spring
  2. jx start pipeline
  3. jx get activity -f your-app -w

Jx version

The output of jx version is:

NAME VERSION
jx 1.3.574
jenkins x platform 0.0.2871
Kubernetes cluster v1.9.7-gke.11
kubectl v1.10.4
helm client v2.11.0+g2e55dbe
helm server v2.11.0+g2e55dbe
git git version 2.17.2 (Apple Git-113)

Kubernetes cluster

GKE

Operating system / Environment

Mac OS X

Expected behavior

Master should be built, released and promoted to staging.

Actual behavior

Promotion to staging is failing with the following error:

0.0.1: digest: sha256:e5f42a65bc897b36f7efdda3410a717acf2806caaf1e5a4b97cc9b0c6eeabaaf size: 1994
Build complete in 28.376902186s
changeme -> 10.27.249.185:5000/rverduci-test-org/rom-spring:0.0.1
[Pipeline] sh
[job] Running shell script
+ cat VERSION
+ jx step post build --image 10.27.249.185:5000/rverduci-test-org/rom-spring:0.0.1
no CVE provider running in the current jx namespace so skip adding image to be analysed[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Promote to Environments)
[Pipeline] dir
Running in /tmp/jenkinsTests.tmp/jenkins3983736231829834209test/workspace/job/charts/rom-spring
[Pipeline] {
[Pipeline] sh
[rom-spring] Running shell script
+ cat ../../VERSION
+ jx step changelog --version v0.0.1
Using batch mode as inside a pipeline
Using helmBinary helm with feature flag: none
Generating change log from git ref  => 5d61e01d6b16d0d78773a220cd7502cb05105aa9
error: reference "" can't be found in git repository
[Pipeline] }
[Pipeline] // dir
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
[Pipeline] // withCredentials
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
ERROR: script returned exit code 1
Finished: FAILURE
@rawlingsj

This comment has been minimized.

Copy link
Member

rawlingsj commented Dec 6, 2018

/priority important-soon

@rawlingsj

This comment has been minimized.

Copy link
Member

rawlingsj commented Dec 6, 2018

/assign rawlingsj

@rawlingsj

This comment has been minimized.

Copy link
Member

rawlingsj commented Dec 6, 2018

/area prow
/kind bug

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment