Skip to content

Use Ubuntu 18.04 and dotnet-buildtools-prereq docker images for enterprise linux pipeline #61001

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

Merged
merged 2 commits into from
Oct 29, 2021

Conversation

akoeplinger
Copy link
Member

@akoeplinger akoeplinger commented Oct 29, 2021

Ubuntu 16.04 is no longer available on Azure Pipelines, move to 18.04 1ES pool and the Docker images from dotnet-buildtools-prereq.

Also add a workaround for #34649 which we hit during the build.

Replaces #60261

@ghost
Copy link

ghost commented Oct 29, 2021

Tagging subscribers to this area: @Anipik, @safern, @ViktorHofer
See info in area-owners.md if you want to be subscribed.

Issue Details

Ubuntu 16.04 is no longer available on Azure Pipelines, move to 18.04 and the Docker images from dotnet-buildtools-prereq.

Author: akoeplinger
Assignees: -
Labels:

area-Infrastructure-libraries

Milestone: -

… for enterprise linux pipeline

Ubuntu 16.04 is no longer available on Azure Pipelines, move to 18.04 on 1ES pool and the Docker images from dotnet-buildtools-prereq.
@akoeplinger akoeplinger force-pushed the enterprise-linux-pipeline branch from f689101 to ad5965c Compare October 29, 2021 10:46
@akoeplinger
Copy link
Member Author

akoeplinger commented Oct 29, 2021

This replaces #60261 /cc @jkoritzinsky

I hit the same build error as that one and found out that something is blocking resolving dotnet.microsoft.com so the dotnet-install.sh can't be fetched in the docker container during the build.

It doesn't happen locally and after a bit of searching it seems specific to the Azure Pipelines hosted pool environment (actions/runner-images#798) and that one is believed to be due to a firewall rule blocking the traffic (Azure/WALinuxAgent#1673).

The other pipeline building inside docker is stress-http and that one was moved to the non-hosted pool a while ago in #35011 so this makes us consistent with that pipeline.

To get the build to work after that I also had to add a workaround for #34649 which we hit during the build.

/cc @dotnet/ncl

Copy link
Member

@safern safern left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@jkoritzinsky
Copy link
Member

Can you queue a run of the pipeline on this PR? I don’t see it in the checks.

@akoeplinger
Copy link
Member Author

akoeplinger commented Oct 29, 2021

@jkoritzinsky it was triggered and is green, you must've missed it (it's called runtime-libraries enterprise-linux in the checks). See https://dev.azure.com/dnceng/public/_build/results?buildId=1446008&view=results

@akoeplinger akoeplinger merged commit dc42fe3 into dotnet:main Oct 29, 2021
@akoeplinger akoeplinger deleted the enterprise-linux-pipeline branch October 29, 2021 17:09
@ghost ghost locked as resolved and limited conversation to collaborators Nov 28, 2021
@akoeplinger
Copy link
Member Author

/backport to release/6.0

@dotnet dotnet unlocked this conversation Dec 20, 2021
@akoeplinger
Copy link
Member Author

/backport to release/6.0

@github-actions
Copy link
Contributor

Started backporting to release/6.0: https://github.com/dotnet/runtime/actions/runs/1602706792

@ghost ghost locked as resolved and limited conversation to collaborators Jan 19, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants