Opened 3 years ago

Last modified 3 years ago

#64180 new defect

Remove azure pipelines

Reported by: ryandesign (Ryan Carsten Schmidt) Owned by: admin@…
Priority: Normal Milestone:
Component: server/hosting Version:
Keywords: Cc:
Port:

Description

Per Azure:

The macOS-10.14 environment is deprecated and will be removed on December 10, 2021. For more details see https://devblogs.microsoft.com/devops/hosted-pipelines-image-deprecation/

We use GitHub Actions for macOS 10.15 and later, so we no longer have any need for Azure Pipelines and everything related to it can be deleted from MacPorts.

Change History (6)

comment:1 Changed 3 years ago by jmroot (Joshua Root)

In 999867a094363e006d14bd714be9558933b526be/macports-base (master):

Remove Azure workflow for base

See: #64180

comment:2 Changed 3 years ago by jmroot (Joshua Root)

In db864c775fb9d5e6369308ccf10ec253a4e19fb1/macports-ports (master):

Remove Azure workflow for ports

See: #64180

comment:3 Changed 3 years ago by l2dy (Zero King)

GitHub organization admins should remove Azure Pipelines integration and revoke all permissions related to it.

comment:4 Changed 3 years ago by ryandesign (Ryan Carsten Schmidt)

If you can tell me were to go and what to click I'll do it...

comment:5 Changed 3 years ago by l2dy (Zero King)

comment:6 in reply to:  5 Changed 3 years ago by ryandesign (Ryan Carsten Schmidt)

Replying to l2dy:

Please check out these pages:

  1. https://github.com/organizations/macports/settings/installations
  2. https://github.com/organizations/macports/settings/oauth_application_policy

We should also remove Travis CI if it exists.

Thanks. There are too many settings screens to know where anything is anymore!

At (1) both Azure Pipelines and Travis CI were listed as installed GitHub apps. I suspended both of them. Before completely uninstalling them I see that Travis CI was listed as having access to macports/upt-macports and Azure Pipelines had access to that and macports/buildbot-macports-custom-views so we should figure out whether those still need that access or no.

I see these CI configuration files for those projects:

At (2) Travis CI and Travis CI for Open Source were still listed but already denied, and Azure Pipelines (OAuth) was listed as approved; I changed it to denied. I assume that since Travis was already denied here, the .travis.yml files above can't have been used for anything anymore and could be removed, but I don't know about the azure-pipelines.yml file.

Note: See TracTickets for help on using tickets.