[rnorth]

No description provided.

[bsideup]

👍

[rnorth]

Ninja fix incoming...

[rnorth]

Updating, but I have a horrible feeling that this may not work well in conjunction with our self-hosted Windows CI execution.

Will kick off a Windows build later to find out.

[rnorth]

/azp run

🤞

[azure-pipelines]

Command 'run

🤞' is not supported by Azure Pipelines.



Supported commands

• help:
• Get descriptions, examples and documentation about supported commands
• Example: help "command_name"
• list:
• List all pipelines for this repository using a comment.
• Example: "list"
• run:
• Run all pipelines or specific pipelines for this repository using a comment. Use this command by itself to trigger all related pipelines, or specify specific pipelines to run.
• Example: "run" or "run pipeline_name, pipeline_name, pipeline_name"
• where:
• Report back the Azure DevOps orgs that are related to this repository and org
• Example: "where"

See additional documentation.

[rnorth]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).

[rnorth]

Nope, it looks like it's run on Windows, but this naive change has caused our Windows build to run on Linux instead:

This will be a slightly more involved change - will move to draft so we can figure this out. We have until 20th September before the ubuntu-16.04 image becomes unavailable, I think.

[rnorth]

Not sure why this was still in draft. We have ~4 days to merge this before we hit the deprecation of the old ubuntu image in Azure pipelines, but that's OK.

[bsideup]

@rnorth IIRC you moved it to draft because of our self hosted Windows node? 😅

[rnorth]

Oh boy, I missed my own comment! Right, thanks!

4 days to merge 4 days to figure this out and merge 😅

[kiview]

Do we even have any good reason to continue maintaining Azure pipelines for the Linux build? It is basically replaced by GitHub Actions after all, isn't it?

[bsideup]

With the exception of the manual trigger support (need to refresh my knowledge on the newly added features tho)

[rnorth]

@kiview that is a very good question, which I admit I haven't given much thought to for a long time.

Unlike CircleCI I don't think we ever had any Docker/LXC quirks, so I think this Linux Azure Pipeline is mainly serving as usage documentation more than anything else.

[kiview]

@bsideup
We can run GHA manually (on PR? maybe just branch...) using workflow_dispatch, but AFAIK only via UI/Button (but with custom input fields).
But I was in this case actually referring to the Linux part of our Azure pipeline.

So my suggestion as a quick fix:

• Remove Linux job from Azure pipelines and keep our current Windows process for now.

@rnorth
Yes, regarding the environment and configuration it should be extremely similar to GitHub Actions (since they also use Azure-hosted runners).

[rnorth]

I'll amend this PR to remove the Azure Linux build, as this indeed seems like the right way forward.

The Azure Windows build should remain unchanged.

[rnorth]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).

[rnorth]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).