Prevent publishing public packages on VSTS
up vote
-1
down vote
favorite
I created the feed to store private npm package there.
When I publish my private package from the project - some another public packages are published to this feed.
- Can I somehow prevent publishing of public packages to the feed?
- Is it ok to store public packages on the VSTS feed?
azure-devops azure-artifacts
add a comment |
up vote
-1
down vote
favorite
I created the feed to store private npm package there.
When I publish my private package from the project - some another public packages are published to this feed.
- Can I somehow prevent publishing of public packages to the feed?
- Is it ok to store public packages on the VSTS feed?
azure-devops azure-artifacts
Possible duplicate of pushing public package to azure devops feed
– Daniel Mann
Nov 7 at 13:59
2
Your feed has an upstream source. This is normal. It's caching the public packages for you.
– Daniel Mann
Nov 7 at 14:00
@DanielMann, one more question. Can I find information about that the packages is cached in the Azure DevOps documentation? I would like to dig deep into the caching of packages.
– SashaSemanyuk
Nov 7 at 14:39
docs.microsoft.com/en-us/azure/devops/artifacts/concepts/…
– Daniel Mann
Nov 7 at 15:33
add a comment |
up vote
-1
down vote
favorite
up vote
-1
down vote
favorite
I created the feed to store private npm package there.
When I publish my private package from the project - some another public packages are published to this feed.
- Can I somehow prevent publishing of public packages to the feed?
- Is it ok to store public packages on the VSTS feed?
azure-devops azure-artifacts
I created the feed to store private npm package there.
When I publish my private package from the project - some another public packages are published to this feed.
- Can I somehow prevent publishing of public packages to the feed?
- Is it ok to store public packages on the VSTS feed?
azure-devops azure-artifacts
azure-devops azure-artifacts
asked Nov 7 at 12:51
SashaSemanyuk
183313
183313
Possible duplicate of pushing public package to azure devops feed
– Daniel Mann
Nov 7 at 13:59
2
Your feed has an upstream source. This is normal. It's caching the public packages for you.
– Daniel Mann
Nov 7 at 14:00
@DanielMann, one more question. Can I find information about that the packages is cached in the Azure DevOps documentation? I would like to dig deep into the caching of packages.
– SashaSemanyuk
Nov 7 at 14:39
docs.microsoft.com/en-us/azure/devops/artifacts/concepts/…
– Daniel Mann
Nov 7 at 15:33
add a comment |
Possible duplicate of pushing public package to azure devops feed
– Daniel Mann
Nov 7 at 13:59
2
Your feed has an upstream source. This is normal. It's caching the public packages for you.
– Daniel Mann
Nov 7 at 14:00
@DanielMann, one more question. Can I find information about that the packages is cached in the Azure DevOps documentation? I would like to dig deep into the caching of packages.
– SashaSemanyuk
Nov 7 at 14:39
docs.microsoft.com/en-us/azure/devops/artifacts/concepts/…
– Daniel Mann
Nov 7 at 15:33
Possible duplicate of pushing public package to azure devops feed
– Daniel Mann
Nov 7 at 13:59
Possible duplicate of pushing public package to azure devops feed
– Daniel Mann
Nov 7 at 13:59
2
2
Your feed has an upstream source. This is normal. It's caching the public packages for you.
– Daniel Mann
Nov 7 at 14:00
Your feed has an upstream source. This is normal. It's caching the public packages for you.
– Daniel Mann
Nov 7 at 14:00
@DanielMann, one more question. Can I find information about that the packages is cached in the Azure DevOps documentation? I would like to dig deep into the caching of packages.
– SashaSemanyuk
Nov 7 at 14:39
@DanielMann, one more question. Can I find information about that the packages is cached in the Azure DevOps documentation? I would like to dig deep into the caching of packages.
– SashaSemanyuk
Nov 7 at 14:39
docs.microsoft.com/en-us/azure/devops/artifacts/concepts/…
– Daniel Mann
Nov 7 at 15:33
docs.microsoft.com/en-us/azure/devops/artifacts/concepts/…
– Daniel Mann
Nov 7 at 15:33
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
Daniel Mann is correct - you most likely have the npmjs upstream source. Because npm only supports a single registry, the upstream source is required to use both public and private packages in the same project. This is by design and recommended by the Azure Artifacts team. The "Source" column on your package list should show that these packages come from npmjs directly.
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
Daniel Mann is correct - you most likely have the npmjs upstream source. Because npm only supports a single registry, the upstream source is required to use both public and private packages in the same project. This is by design and recommended by the Azure Artifacts team. The "Source" column on your package list should show that these packages come from npmjs directly.
add a comment |
up vote
0
down vote
Daniel Mann is correct - you most likely have the npmjs upstream source. Because npm only supports a single registry, the upstream source is required to use both public and private packages in the same project. This is by design and recommended by the Azure Artifacts team. The "Source" column on your package list should show that these packages come from npmjs directly.
add a comment |
up vote
0
down vote
up vote
0
down vote
Daniel Mann is correct - you most likely have the npmjs upstream source. Because npm only supports a single registry, the upstream source is required to use both public and private packages in the same project. This is by design and recommended by the Azure Artifacts team. The "Source" column on your package list should show that these packages come from npmjs directly.
Daniel Mann is correct - you most likely have the npmjs upstream source. Because npm only supports a single registry, the upstream source is required to use both public and private packages in the same project. This is by design and recommended by the Azure Artifacts team. The "Source" column on your package list should show that these packages come from npmjs directly.
answered Nov 7 at 14:27
Alex Mullans
91321233
91321233
add a comment |
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53189815%2fprevent-publishing-public-packages-on-vsts%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Possible duplicate of pushing public package to azure devops feed
– Daniel Mann
Nov 7 at 13:59
2
Your feed has an upstream source. This is normal. It's caching the public packages for you.
– Daniel Mann
Nov 7 at 14:00
@DanielMann, one more question. Can I find information about that the packages is cached in the Azure DevOps documentation? I would like to dig deep into the caching of packages.
– SashaSemanyuk
Nov 7 at 14:39
docs.microsoft.com/en-us/azure/devops/artifacts/concepts/…
– Daniel Mann
Nov 7 at 15:33