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

YAMLException: can not read a block mapping entry; a multiline key may not be an implicit key at line 22, column 13: displayName: 'npm install, build, and test' #3174

Closed
Lanremike22 opened this issue Jan 23, 2024 · 5 comments
Labels
needs-test-case Please submit a reproducible test case showcasing the issue! stale Closed (manually) after waiting on a response for 30 days.

Comments

@Lanremike22
Copy link

My original code: please can someone help review this

Node.js

Build a general Node.js project with npm.

Add steps that analyze code, save build artifacts, deploy, and more:

https://docs.microsoft.com/azure/devops/pipelines/languages/javascript

trigger:

  • master

pool:
vmImage: ubuntu-latest

steps:

  • task: NodeTool@0
    inputs:
    versionSpec: '10.x'
    displayName: 'Install Node.js'

  • script: |
    npm install
    npm run build
    npm test
    displayName: 'npm install, build, and test'

@zachleat
Copy link
Member

are there tabs in your yaml? it’s likely a whitespace problem

@Lanremike22
Copy link
Author

Lanremike22 commented Jan 24, 2024 via email

@uncenter
Copy link
Contributor

If you could put your YAML code inside markdown fenced code blocks, it would make it easier to read your issue.

@zachleat zachleat added the needs-test-case Please submit a reproducible test case showcasing the issue! label Feb 12, 2024
@zachleat zachleat added the stale Closed (manually) after waiting on a response for 30 days. label Mar 22, 2024
@zachleat
Copy link
Member

This is an automated message to let you know that this issue requires additional input from the original poster and for the health of the repository issue tracker the issue will be closed. This is to help alleviate issues hanging open waiting for a response from the original poster.

Do not let the issue’s closing deter you. After you’ve supplied the required information, the issue will be reopened. Thanks!

@zachleat zachleat closed this as not planned Won't fix, can't repro, duplicate, stale Mar 22, 2024
@zachleat
Copy link
Member

Related #2126

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-test-case Please submit a reproducible test case showcasing the issue! stale Closed (manually) after waiting on a response for 30 days.
Projects
None yet
Development

No branches or pull requests

3 participants