Skip to content

Commit 4d3710c

Browse files
KathrynEEKathrynEE
authored
Users/kaelli/update docfx.json to add archive url (#4520)
* commit changes * add archive_url to docfx.json file * updates to fix build errors on moniker zone. * continue build error fixes on moniker zone * fix remaining build errors * continue fixing last 4 build errors. * more fixes
1 parent 10d5d24 commit 4d3710c

File tree

406 files changed

+721
-802
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

406 files changed

+721
-802
lines changed

Diff for: ‎docs/artifacts/artifact-storage.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -6,13 +6,13 @@ ms.topic: conceptual
66
ms.date: 04/07/2021
77
ms.author: rabououn
88
author: ramiMSFT
9-
monikerRange: '>= tfs-2017'
9+
monikerRange: '<= azure-devops'
1010
"recommendations": "true"
1111
---
1212

1313
# Artifacts storage consumption
1414

15-
[!INCLUDE [version-gt-eq-2017](../includes/version-gt-eq-2017.md)]
15+
[!INCLUDE [version-lt-eq-azure-devops](../includes/version-lt-eq-azure-devops.md)]
1616

1717
With Azure Artifacts free-tier plan, you get two Gibibytes (GiB) of free storage to store different types of packages. When you reach your maximum storage limit, you can either upgrade to a paid subscription or delete some of your existing artifacts.
1818

Diff for: ‎docs/artifacts/artifacts-key-concepts.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -4,13 +4,13 @@ description: Important concepts for Azure Artifacts
44
ms.technology: devops-artifacts
55
ms.topic: conceptual
66
ms.date: 01/12/2022
7-
monikerRange: '>= tfs-2017'
7+
monikerRange: '<= azure-devops'
88
"recommendations": "true"
99
---
1010

1111
# Key concepts for Azure Artifacts
1212

13-
[!INCLUDE [version-gt-eq-2017](../includes/version-gt-eq-2017.md)]
13+
[!INCLUDE [version-lt-eq-azure-devops](../includes/version-lt-eq-azure-devops.md)]
1414

1515
## Immutability
1616

Diff for: ‎docs/artifacts/collaborate-with-packages.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -5,13 +5,13 @@ ms.assetid: EA33E340-EC9A-4F75-A201-82CE9685662B
55
ms.technology: devops-artifacts
66
ms.date: 01/13/2022
77
ms.topic: reference
8-
monikerRange: '>= tfs-2017'
8+
monikerRange: '<= azure-devops'
99
"recommendations": "true"
1010
---
1111

1212
# Collaborate more and build faster with componentization
1313

14-
[!INCLUDE [version-gt-eq-2017](../includes/version-gt-eq-2017.md)]
14+
[!INCLUDE [version-lt-eq-azure-devops](../includes/version-lt-eq-azure-devops.md)]
1515

1616
Your product is successful, your organization is growing, and it's time to scale up your codebase to match this success. As you scale out past 2-3 teams working in a single codebase on a single product, you may find yourself asking questions like:
1717

Diff for: ‎docs/artifacts/concepts/best-practices.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -4,13 +4,13 @@ description: Best practices to publish and consume packages from Artifacts feeds
44
ms.technology: devops-artifacts
55
ms.topic: conceptual
66
ms.date: 08/20/2021
7-
monikerRange: '>= tfs-2017'
7+
monikerRange: '<= azure-devops'
88
"recommendations": "true"
99
---
1010

1111
# Azure Artifacts: best practices
1212

13-
[!INCLUDE [version-gt-eq-2017](../../includes/version-gt-eq-2017.md)]
13+
[!INCLUDE [version-lt-eq-azure-devops](../../includes/version-lt-eq-azure-devops.md)]
1414

1515
This article contains some general guidance and best practices when it comes to producing and consuming packages in Azure Artifacts.
1616

Diff for: ‎docs/artifacts/concepts/feeds.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -5,12 +5,12 @@ ms.assetid: 21673f53-68a3-4d44-866e-ad29435a3fde
55
ms.technology: devops-artifacts
66
ms.topic: conceptual
77
ms.date: 03/03/2022
8-
monikerRange: '>= tfs-2017'
8+
monikerRange: '<= azure-devops'
99
---
1010

1111
# What are feeds?
1212

13-
[!INCLUDE [version-gt-eq-2017](../../includes/version-gt-eq-2017.md)]
13+
[!INCLUDE [version-lt-eq-azure-devops](../../includes/version-lt-eq-azure-devops.md)]
1414

1515
Artifacts Feeds are organizational constructs that allow you to store, manage, and group your packages and control who to share it with. Feeds are not package-type dependent. You can store all the following package types in a single feed: npm, NuGet, Maven, Python, and Universal packages.
1616

Diff for: ‎docs/artifacts/concepts/symbols.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -6,13 +6,13 @@ ms.custom: contperf-fy22q1
66
ms.topic: conceptual
77
ms.assetid: 6D0F0D86-2ADC-4902-AFA7-98F7EF78EE07
88
ms.date: 07/15/2021
9-
monikerRange: '>= tfs-2017'
9+
monikerRange: '<= azure-devops'
1010
"recommendations": "true"
1111
---
1212

1313
# Symbols overview
1414

15-
[!INCLUDE [version-gt-eq-2017](../../includes/version-gt-eq-2017.md)]
15+
[!INCLUDE [version-lt-eq-azure-devops](../../includes/version-lt-eq-azure-devops.md)]
1616

1717
To debug compiled executables from native languages like C and C++, you need symbol files that contain mapping information to the source code. These files are created from source code during compilation and generally have the PDB (program database) extension. Azure Artifacts offers a dedicated symbols server to publish your symbols.
1818

Diff for: ‎docs/artifacts/concepts/upstream-behavior.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -6,12 +6,12 @@ ms.topic: conceptual
66
ms.date: 02/23/2022
77
ms.author: rabououn
88
author: ramiMSFT
9-
monikerRange: '>= tfs-2017'
9+
monikerRange: '<= azure-devops'
1010
---
1111

1212
# Configure upstream behavior
1313

14-
[!INCLUDE [version-gt-eq-2017](../../includes/version-gt-eq-2017.md)]
14+
[!INCLUDE [version-lt-eq-azure-devops](../../includes/version-lt-eq-azure-devops.md)]
1515

1616
Upstream sources enables developers to use a single feed to publish and consume packages from Artifact feeds and public registries such as NuGet.org or npmjs.com. To set up upstream sources for your feed, check the box to **include packages from common public sources**. This will allow your feed to use packages from the common public registries.
1717

Diff for: ‎docs/artifacts/concepts/upstream-sources.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -5,13 +5,13 @@ ms.assetid: 7cb70122-7c5b-46c1-b07e-1382cfc7d62b
55
ms.technology: devops-artifacts
66
ms.topic: conceptual
77
ms.date: 02/16/2022
8-
monikerRange: '>= tfs-2017'
8+
monikerRange: '<= azure-devops'
99
"recommendations": "true"
1010
---
1111

1212
# Upstream sources
1313

14-
[!INCLUDE [version-gt-eq-2017](../../includes/version-gt-eq-2017.md)]
14+
[!INCLUDE [version-lt-eq-azure-devops](../../includes/version-lt-eq-azure-devops.md)]
1515

1616
Upstream sources enable you to use a single feed to store packages from different sources: the ones you publish and the ones you consume from feeds and public registries such as NuGet.org, npmjs.com, Maven Central, and PyPI. Once you enable an upstream source, any user connected to your feed can install a package from upstream and a copy will be saved to your feed.
1717

Diff for: ‎docs/artifacts/concepts/views.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -5,13 +5,13 @@ ms.assetid: 28527A09-8025-4615-A746-9D213CF8202C
55
ms.technology: devops-artifacts
66
ms.topic: conceptual
77
ms.date: 02/02/2022
8-
monikerRange: '>= tfs-2017'
8+
monikerRange: '<= azure-devops'
99
"recommendations": "true"
1010
---
1111

1212
# What are feed views?
1313

14-
[!INCLUDE [version-gt-eq-2017](../../includes/version-gt-eq-2017.md)]
14+
[!INCLUDE [version-lt-eq-azure-devops](../../includes/version-lt-eq-azure-devops.md)]
1515

1616
Feed views enable developers to share a subset of package-versions with their consumers. A common use of feed views is to share package versions that have been tested and validated but hold back on packages that are still under development and/or didn't meet a certain quality bar.
1717

Diff for: ‎docs/artifacts/feeds/feed-permissions.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -5,13 +5,13 @@ ms.assetid: 70313C3C-2E52-4FFC-94C2-41F1E37C9D26
55
ms.technology: devops-artifacts
66
ms.topic: conceptual
77
ms.date: 02/28/2022
8-
monikerRange: '>= tfs-2017'
8+
monikerRange: '<= azure-devops'
99
"recommendations": "true"
1010
---
1111

1212
# Configure permissions
1313

14-
[!INCLUDE [version-gt-eq-2017](../../includes/version-gt-eq-2017.md)]
14+
[!INCLUDE [version-lt-eq-azure-devops](../../includes/version-lt-eq-azure-devops.md)]
1515

1616
With Azure Artifacts you can publish, consume, and store different types of packages in your feed. Setting up permissions for your feed allows you to control who can access your packages.
1717

Diff for: ‎docs/artifacts/feeds/project-scoped-feeds.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Understand the difference between project-scoped and organization-s
44
ms.technology: devops-artifacts
55
ms.topic: conceptual
66
ms.date: 02/22/2022
7-
monikerRange: '>= tfs-2017'
7+
monikerRange: '<= azure-devops'
88
"recommendations": "true"
99
---
1010

Diff for: ‎docs/artifacts/feeds/views.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -5,12 +5,12 @@ ms.assetid: EB40D23E-1053-4EBF-9D1D-19CF1BBAF1C6
55
ms.technology: devops-artifacts
66
ms.topic: conceptual
77
ms.date: 02/16/2022
8-
monikerRange: '>= tfs-2017'
8+
monikerRange: '<= azure-devops'
99
---
1010

1111
# Use feed views to share packages
1212

13-
[!INCLUDE [version-gt-eq-2017](../../includes/version-gt-eq-2017.md)]
13+
[!INCLUDE [version-lt-eq-azure-devops](../../includes/version-lt-eq-azure-devops.md)]
1414

1515
Feed views are a way to enable users to share some packages while keeping other packages private. Views filter the feed to a subset of packages that meet a set of criteria defined by that view.
1616

Diff for: ‎docs/artifacts/get-started-npm.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -6,13 +6,13 @@ ms.topic: quickstart
66
ms.assetid: 5BFBA0C3-85ED-40C9-AC5F-F686923160D6
77
ms.custom: contperf-fy20q4, conterperfq3, contperf-fy21q3
88
ms.date: 02/14/2022
9-
monikerRange: '>= tfs-2017'
9+
monikerRange: '<= azure-devops'
1010
"recommendations": "true"
1111
---
1212

1313
# Get started with npm packages in Azure Artifacts
1414

15-
[!INCLUDE [version-gt-eq-2017](../includes/version-gt-eq-2017.md)]
15+
[!INCLUDE [version-lt-eq-azure-devops](../includes/version-lt-eq-azure-devops.md)]
1616

1717
With Azure Artifacts, you can publish and download npm packages from feeds and public registries such as npmjs.com. This quickstart will guide you through creating your own feed, setting up your project, and publishing and downloading npm packages to and from your Azure Artifacts feed.
1818

Diff for: ‎docs/artifacts/get-started-nuget.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -6,13 +6,13 @@ ms.custom: contperf-fy21q3
66
ms.topic: quickstart
77
ms.assetid: C5112218-DA7E-4016-986D-2D0F70DAFA44
88
ms.date: 02/18/2022
9-
monikerRange: '>= tfs-2017'
9+
monikerRange: '<= azure-devops'
1010
"recommendations": "true"
1111
---
1212

1313
# Get started with NuGet packages
1414

15-
[!INCLUDE [version-gt-eq-2017](../includes/version-gt-eq-2017.md)]
15+
[!INCLUDE [version-lt-eq-azure-devops](../includes/version-lt-eq-azure-devops.md)]
1616

1717
Developers can use Azure Artifacts to publish and consume NuGet packages both to and from feeds and public registries. A feed is an organizational construct that hosts packages. You can create public and private feeds, and you can control who can access your packages by modifying feed permissions.
1818

Diff for: ‎docs/artifacts/how-to/delete-and-recover-packages.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -6,13 +6,13 @@ ms.assetid: 10f5e81f-2518-41b9-92b6-e00c905b59b3
66
ms.custom: contperf-fy21q2, contperf-fy22q1
77
ms.topic: conceptual
88
ms.date: 02/16/2022
9-
monikerRange: '>= tfs-2017'
9+
monikerRange: '<= azure-devops'
1010
"recommendations": "true"
1111
---
1212

1313
# Delete and recover packages
1414

15-
[!INCLUDE [version-gt-eq-2017](../../includes/version-gt-eq-2017.md)]
15+
[!INCLUDE [version-lt-eq-azure-devops](../../includes/version-lt-eq-azure-devops.md)]
1616

1717
Azure Artifacts safely stores different types of packages in your feed, whether you published them directly or saved them from upstream sources. As older package versions fall out of use, you might want to clean them up either manually or automatically by using retention policies.
1818

Diff for: ‎docs/artifacts/how-to/follow-package-notifications.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -4,12 +4,12 @@ description: How to follow a package and get notified every time a new version i
44
ms.technology: devops-artifacts
55
ms.topic: conceptual
66
ms.date: 02/14/2022
7-
monikerRange: '>= tfs-2017'
7+
monikerRange: '<= azure-devops'
88
---
99

1010
# Package notification
1111

12-
[!INCLUDE [version-gt-eq-2017](../../includes/version-gt-eq-2017.md)]
12+
[!INCLUDE [version-lt-eq-azure-devops](../../includes/version-lt-eq-azure-devops.md)]
1313

1414
Notifications are a great tool to stay informed about specific changes within your project. In Azure Artifacts, when you follow a package you’ll be notified every time a new version of that package is published. A notification will be sent to your preferred email address with details about the new published version. The preferred email address is usually the email address you signed into Azure DevOps with, but you can change it from your profile page.
1515

Diff for: ‎docs/artifacts/how-to/project-scoped-feeds-pipeline-project-permissions.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -4,12 +4,12 @@ description: How to set permissions to access a project-scoped feed in a differe
44
ms.technology: devops-artifacts
55
ms.topic: conceptual
66
ms.date: 08/05/2020
7-
monikerRange: '>= tfs-2017'
7+
monikerRange: '<= azure-devops'
88
---
99

1010
# How to allow a Pipeline to access a project-scoped feed in a different project
1111

12-
[!INCLUDE [version-gt-eq-2017](../../includes/version-gt-eq-2017.md)]
12+
[!INCLUDE [version-lt-eq-azure-devops](../../includes/version-lt-eq-azure-devops.md)]
1313

1414
When a Pipeline needs to connect to a project-scoped feed in a different project, the pipeline must have access to both the project that the feed is scoped to and the feed itself.
1515
Your **Project build service** identity will look as follows:

Diff for: ‎docs/artifacts/how-to/set-up-upstream-sources.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -4,12 +4,12 @@ description: How to configure upstream sources for your Azure Artifacts feeds
44
ms.technology: devops-artifacts
55
ms.topic: conceptual
66
ms.date: 02/16/2022
7-
monikerRange: '>= tfs-2017'
7+
monikerRange: '<= azure-devops'
88
---
99

1010
# Configure upstream sources
1111

12-
[!INCLUDE [version-gt-eq-2017](../../includes/version-gt-eq-2017.md)]
12+
[!INCLUDE [version-lt-eq-azure-devops](../../includes/version-lt-eq-azure-devops.md)]
1313

1414
With upstream sources, you can use a single feed to store the packages you generate and the packages you consume from public registries such as npmjs.com, NuGet.org, Maven Central, and PyPI.org. Once you've enabled an upstream source, every time you install a package from the public registry, Azure Artifacts will save a copy of that package in your feed.
1515

Diff for: ‎docs/artifacts/maven/google-maven.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: How to add Google Maven Repository upstream source
44
ms.technology: devops-artifacts
55
ms.topic: conceptual
66
ms.date: 03/03/2022
7-
monikerRange: '>= tfs-2017'
7+
monikerRange: '<= azure-devops'
88
"recommendations": "true"
99
---
1010

Diff for: ‎docs/artifacts/maven/gradle-plugins.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: How to add Gradle Plugins upstream source
44
ms.technology: devops-artifacts
55
ms.topic: conceptual
66
ms.date: 03/11/2022
7-
monikerRange: '>= tfs-2017'
7+
monikerRange: '<= azure-devops'
88
"recommendations": "true"
99
---
1010

Diff for: ‎docs/artifacts/maven/jitpack-upstream.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: How to add JitPack upstream source
44
ms.technology: devops-artifacts
55
ms.topic: conceptual
66
ms.date: 03/22/2022
7-
monikerRange: '>= tfs-2017'
7+
monikerRange: '<= azure-devops'
88
"recommendations": "true"
99
---
1010

Diff for: ‎docs/artifacts/maven/publish-package-gradle.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -5,13 +5,13 @@ ms.technology: devops-artifacts
55
ms.reviewer: dastahel
66
ms.topic: conceptual
77
ms.date: 11/16/2021
8-
monikerRange: '>= tfs-2017'
8+
monikerRange: '<= azure-devops'
99
"recommendations": "true"
1010
---
1111

1212
# Publish Maven artifacts using Gradle
1313

14-
[!INCLUDE [version-gt-eq-2017](../../includes/version-gt-eq-2017.md)]
14+
[!INCLUDE [version-lt-eq-azure-devops](../../includes/version-lt-eq-azure-devops.md)]
1515

1616
This topic covers creating and publishing a Maven artifact to an Azure Artifacts feed with Gradle.
1717

Diff for: ‎docs/artifacts/maven/upstream-sources.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -4,13 +4,13 @@ description: How to use packages from Maven upstream
44
ms.technology: devops-artifacts
55
ms.topic: conceptual
66
ms.date: 02/15/2022
7-
monikerRange: '>= tfs-2017'
7+
monikerRange: '<= azure-devops'
88
"recommendations": "true"
99
---
1010

1111
# Use packages from Maven Central
1212

13-
[!INCLUDE [version-gt-eq-2017](../../includes/version-gt-eq-2017.md)]
13+
[!INCLUDE [version-lt-eq-azure-devops](../../includes/version-lt-eq-azure-devops.md)]
1414

1515
With upstream sources, you can use both private packages you've created and public packages from Maven Central. When you enable upstream sources in your feed, Azure Artifacts will save a copy of any packages you install from Maven central. Azure Artifacts also support other Maven upstream sources such as Google Maven Repository, Gradle Plugins, and JitPack.
1616

Diff for: ‎docs/artifacts/npm/npmrc.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -5,12 +5,12 @@ ms.assetid: A5364E3A-3918-4318-AAE0-430EA91AD5F1
55
ms.technology: devops-artifacts
66
ms.topic: conceptual
77
ms.date: 03/16/2022
8-
monikerRange: '>= tfs-2017'
8+
monikerRange: '<= azure-devops'
99
---
1010

1111
# Set up your project and connect to Azure Artifacts
1212

13-
[!INCLUDE [version-gt-eq-2017](../../includes/version-gt-eq-2017.md)]
13+
[!INCLUDE [version-lt-eq-azure-devops](../../includes/version-lt-eq-azure-devops.md)]
1414

1515
With Azure Artifacts, you can publish different types of packages to your feeds such as npm, NuGet, Python, Maven, and Universal packages. You can also install packages from feeds and public registries such as npmjs.com.
1616

Diff for: ‎docs/artifacts/npm/publish.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -5,11 +5,11 @@ ms.assetid: 85773969-1491-4242-A060-BD5D193961A0
55
ms.technology: devops-artifacts
66
ms.topic: conceptual
77
ms.date: 10/14/2021
8-
monikerRange: '>= tfs-2017'
8+
monikerRange: '<= azure-devops'
99
---
1010

1111
# Publish npm packages from the command line
1212

13-
[!INCLUDE [version-gt-eq-2017](../../includes/version-gt-eq-2017.md)]
13+
[!INCLUDE [version-lt-eq-azure-devops](../../includes/version-lt-eq-azure-devops.md)]
1414

1515
[!INCLUDE [](../includes/npm/publish.md)]

Diff for: ‎docs/artifacts/npm/scopes.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -5,12 +5,12 @@ ms.assetid: c88868bd-8101-48f3-b76d-17c858181fda
55
ms.technology: devops-artifacts
66
ms.topic: conceptual
77
ms.date: 02/15/2022
8-
monikerRange: '>= tfs-2017'
8+
monikerRange: '<= azure-devops'
99
---
1010

1111
# Use npm scopes
1212

13-
[!INCLUDE [version-gt-eq-2017](../../includes/version-gt-eq-2017.md)]
13+
[!INCLUDE [version-lt-eq-azure-devops](../../includes/version-lt-eq-azure-devops.md)]
1414

1515
Npm scopes are a way of grouping related packages together. A scope allows you to create a package with the same name as a package created by another user or Org without conflict. They allow the user to separate public and private packages by prefixing their packages with a scope `@SCOPE_NAME` and configuring the `.npmrc` file to only use an Azure Artifacts feed for that scope.
1616
With Azure Artifacts, you can publish and download both scoped and non-scoped packages to/from your Artifacts feeds or public registries. Using npm scopes is also useful with self-hosted on-premise servers that do not have internet access because setting up upstream sources in that case is not possible. Using scopes:

Diff for: ‎docs/artifacts/npm/upstream-sources.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -5,12 +5,12 @@ ms.assetid: E2DB1217-7113-4A75-A66D-3CADDB07AD37
55
ms.technology: devops-artifacts
66
ms.topic: conceptual
77
ms.date: 02/14/2022
8-
monikerRange: '>= tfs-2017'
8+
monikerRange: '<= azure-devops'
99
---
1010

1111
# Use packages from npmjs.com
1212

13-
[!INCLUDE [version-gt-eq-2017](../../includes/version-gt-eq-2017.md)]
13+
[!INCLUDE [version-lt-eq-azure-devops](../../includes/version-lt-eq-azure-devops.md)]
1414

1515
The npm client is designed to work with a single primary *registry* (what Azure Artifacts calls a *feed*). It also supports secondary *scoped* registries. Scoped registries can only be used to install packages whose names begin with the scope prefix, so their usage is more restrictive. If you want to use both private packages you've created **and** public packages from npmjs.com, we recommend using upstream sources.
1616

0 commit comments

Comments
 (0)