Skip to content
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

Javascript quickstarts fail due to git related tasks #673

Open
bdurrow opened this issue May 8, 2021 · 0 comments
Open

Javascript quickstarts fail due to git related tasks #673

bdurrow opened this issue May 8, 2021 · 0 comments

Comments

@bdurrow
Copy link
Contributor

bdurrow commented May 8, 2021

I tried to use the react and node-http quickstarts. Both of them failed to create their pipeline. jx pipeline lint reveals:

WARNING: ignoring missing user name in git credentials file: /Users/brad/.git-credentials URL: https://:@github.com
FILE                                   STATUS
.lighthouse/jenkins-x/triggers.yaml    OK
.lighthouse/jenkins-x/pullrequest.yaml failed to unmarshal YAML file .lighthouse/jenkins-x/pullrequest.yaml: failed to validate generated PipelineRun: invalid value: git-clone: spec.pipelinespec.tasks[0].taskSpec.steps[2].name
invalid value: git-merge: spec.pipelinespec.tasks[0].taskSpec.steps[3].name
.lighthouse/jenkins-x/release.yaml     failed to unmarshal YAML file .lighthouse/jenkins-x/release.yaml: failed to validate generated PipelineRun: invalid value: git-clone: spec.pipelinespec.tasks[0].taskSpec.steps[1].name

I am not sure if it is related but my cluster has a clusterTask called git-clone. Removing that git-clone clusterTask does not seem to resolve the problem.

If I remove metadata.annotations.lighthouse.jenkins-x.io/prependStepsURL: https://raw.githubusercontent.com/jenkins-x/jx3-pipeline-catalog/9ef3f3c107abc35b8f49d2e17d3af9ba5c5ef932/tasks/git-clone/git-clone-pr.yaml it sems to resolve the lint issue. I figured this out because I imported a javascript project that didn't have this problem and a diff of their pullrequest.yaml was the only difference. The working copy did not have the offending annotation.

I don't think it is related but I will mention it here: after fixing this linting problem, committing the changes and pushing them to the repo. pipelineRuns are created which in turn create taskRuns but the taskRuns never start and do not get a status block.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant