Azure / Azure/azure-devops-cli-extension

az pipelines run provides no identifiable output when could not queue

Open
#1,097 0 comments 2 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
682
Forks
278
Avg merge
3d 23h
Merged PRs (30d)
3

Description

### **This is autogenerated. Please review and update as needed.**

## Describe the bug

**Command Name**
`az pipelines run
Extension Name: azure-devops. Version: 0.18.0.`

**Errors:**

The problem here is when `run` command succeeds, I can see (a lotta) info that can identify the run instance, so I can go and **find** it in browser. But if it fails – then no luck for the old user:
```
Could not queue the build because there were validation errors or warnings.
```

## To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Have a simple pipeline defined with an error in yml file and try to run it with cli.

- _Put any pre-requisite steps here..._
- `az pipelines run --name {} --branch {} --open --variables {} {}`

## Expected Behavior

## Environment Summary
```
macOS-10.15.7-x86_64-i386-64bit
Python 3.8.7
Installer: HOMEBREW

azure-cli 2.18.0 *

Extensions:
azure-devops 0.18.0

```
## Additional Context

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.