"jx step collect" fails due to git collision

[davidcurrie]

Summary

jx step collect failed when run as part of an extension with the following error:

error: failed to collect patterns coverage.txt, coverage.html to path jenkins-x/.../PR-108/2: Have you set up a git credential helper? See https://help.github.com/articles/caching-your-github-password-in-git/
: failed to run 'git push origin HEAD' command in directory '/tmp/jenkins-x-collect613292501', output: 'fatal: protocol error: bad line length character: erro
To https://github.com/cloudbees/jx-devops-results.git
 ! [rejected]        HEAD -> gh-pages (fetch first)
error: failed to push some refs to 'https://github.com/cloudbees/jx-devops-results.git'
hint: Updates were rejected because the remote contains work that you do
hint: not have locally. This is usually caused by another repository pushing
hint: to the same ref. You may want to first integrate the remote changes
hint: (e.g., 'git pull ...') before pushing again.
hint: See the 'Note about fast-forwards' in 'git push --help' for details.'

Looks like another build must have simultaneously been trying to publish to the same repo. This caused the build to fail.

Steps to reproduce the behavior

Hard to reproduce given its timing related.

Expected behavior

Files are published.

Actual behavior

Build fails.

Jx version

The output of jx version is:

NAME               VERSION
jx                 1.3.783
jenkins x platform 0.0.3275
Kubernetes cluster v1.11.5-gke.5
kubectl            v1.12.0
helm client        v2.11.0+g2e55dbe
helm server        v2.12.2+g7d2b0c7
git                git version 2.18.0
Operating System   Mac OS X 10.14.2 build 18C54

Jenkins type

• Classic Jenkins
• Serverless Jenkins

Kubernetes cluster

GKE

Operating system / Environment

MacOS

[jenkins-x-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://jenkins-x.io/community.
/lifecycle stale

[jenkins-x-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://jenkins-x.io/community.
/lifecycle rotten

[jenkins-x-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://jenkins-x.io/community.
/close

[jenkins-x-bot]

@jenkins-x-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://jenkins-x.io/community.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.