Azure-pipelines-agent: Yaml Builds specified for Default queue run in Hosted VS2017

[jwittner]

Are we accepting PRs against the preview docs?

queue: Default

results in builds running in Hosted VS2017 while

queue:
  name: Default

runs the builds in Default.

The docs refer to the former failing example.

[ericsciple]

the docs are correct. it's possible something has regressed on the service, although we haven't had any other reports. I'll try to repro

[jwittner]

I saw somewhere else in the docs, the latter example, and it fixed my problem. I'll have to search my history.

[jwittner]

We're continuing to see strangeness around this. Several new builds (using the latter examples above) create definitions that incorrectly build on Hosted VS 2017. We have to go in and modify the queue to Default manually via the browser.

@ericsciple It's starting to look like a regression.

[jwittner]

Is this the best place for this issue? Or is there a better repo I should migrate it to? Starting to seem like a VSTS back end issue with less to do with the vsts-agent.

[ericsciple]

I think the experience is causing confusion. The queue defined on the definition in the web is the fallback, for any phases in your file that do not specify a queue.

[jwittner]

I have

queue:
  name: Default

at the very top of the .vsts-ci.yml file, when I push that to VSTS it creates a build definition. Builds triggered for that definition are running in Hosted VS2017. That's expected behavior?

[ericsciple]

That is not expected. I am also not able to reproduce that behavior. Here is what I tried:

1. Create a new repo
2. Create a file .vsts-ci.yml with the following content:

phases:
# This phase uses the Hosted Linux Preview queue
- phase: linux
  queue: Hosted Linux Preview
  steps:
  - script: pwd

# This phase falls back to the queue specified on the definition
- phase: windows
  steps:
  - script: cd

1. Confirmed the linux phase is running on Linux and windows is running on Windows (output from pwd is /opt/vsts/work/1/s and output from cd is D:\a\1\s)

I also tried this:

1. Create a new repo
2. Create a file .vsts-ci.yml with the following content:

queue: Hosted Linux Preview
steps:
- script: pwd

1. Confirmed the linux phase is running on Linux (output from pwd is /opt/vsts/work/1/s)

[jwittner]

Your examples show the former documentation, we'll try that out next time and see if it works for us and I'll report back here.

Did you try with the queue labelled as I did, via the name sub property?

[ericsciple]

I have tried that now too.

[samuel-weber]

Any news on this one?

[ericsciple]

@samuel-weber what issue are seeing specifically? I was not able to reproduce the issue.

@dakale fyi

[bryanmacfarlane]

let's re-open if we get the specific issue since we weren't able to repro