I'm trying to use an npm package I created in my Artifacts feed, I got my .npmrc file in place to go directly to azure feed, first time I run 'npm install' noticed that there are a lot of new npm packages coming because of the upstream configuration I have in 'Upstream sources' section in my feed, but after that if I want to add a new package reference in my project I got an error saying 'No matching version found for #' this is because package is not there in artifacts feed but in this case shouldn't it go to 'https://registry.npmjs.org/' to get the package reference and place it in upstream packages in Azure feed?
here is the code I have in my .npmrc file
registry=https://pkgs.dev.azure.com/<enterprise-name>/_packaging/<feed-name>/npm/registry/
always-auth=true
It seems that you don't have the required permission to UpStream source of that private feed. You can follow my steps to locate the issue and resolve it:
1.Go Feed Settings to make sure npmjs is set as Upstream source. And use the Move up button to move npmjs source to the top of the list (List of Upstream source).
2.Go Views tab in feed settings and check who can access the #Local view. Note:
#local contains all packages pushed to this feed and all packages saved from an upstream source
Try editing the #Local view and make people in current org can access it. Also you can choose Specific People, but you need to grant access to yourself.
3.Make sure the Account/PAT you use for authentication is the same account you use to configure in web Portal. (The local account used by the authentication must have the access to the #Local view in feed)
If that not helps, check whether the package version you're looking for exists in even UpStream source and share the details of error message here. More details please refer to this document carefully.
Related
General: I develop an Azure DevOps extension with tasks and pipeline decorators. Testing on local Azure DevOps Server instance. Extension loaded through manage extensions from local hard drive. Let's say that I installed the extension first time with version 1.0.0 and a node_modules dependency "3rdPartyDep" with version 2.0.0, which has transitive dependencies with vulnerabilities.
Scenario:
Upgrade "3rdPartyDep" to version 3.0.0 with fixed vulnerabilities. Build new version of my extension, say 1.0.1. Create the .vsix, update the extension in the Azure DevOps Server.
Run a pipeline, which fails because I did not check the "3rdPartyDep" changes and there are breaking changes and the extension fails to run.
Rollback the "3rdPartyDep" library to 2.0.0 because I have no time now to check what is broken in there right now as I have other things to debug and implement, repackage the extension, increase version to 1.0.2, update extension in Azure DevOps Server.
Run the pipeline. It fails with the same exception, as if I didn't rollback. I look into the agent taks folder and I see that the node_modules with the "3rdPartyDep" library is pointing to 3.0.0, which is wrong because I rolled back the version.
I open the generated .vsix archive and check that the node_modules inside contains the correct 2.0.0 version, so no problems of packaging or building from my side.
I make a conclusion that Azure DevOps stores somewhere a cached version of the extension with the node_modules including the wrong version of the "3rdPartyDep". I search that cache folder over internet to find out where it is, and I also search with a search tool all my machine, including words in file. Nowhere to be found. There is no location on my machine with such node_modules containing the 3.0.0 version. It might be stored in some encrypted DB?
I uninstall completely the extension, and install it back. I see that Azure DevOps has a history for the extension, and the cache is not cleared. Any pipeline fails, even if my .vsix does not contain this dependency.
I'm stuck.
Questions:
Where extensions are actually cached inside Azure DevOps Server?
Why updating, uninstalling and installing does not fix the problem?
Is there any way to fix this? What can I do? I do not want to reinstall the server completely. Moreover, this raises concerns about how node_modules are managed and cached and what happens at the clients and the cloud.
You could try the following items:
Try to clean the browser cache, and check whether you have increase the version number in the task.json.
Try to perform Delete task -- Save definition -- add task again process.
Delete Azure DevOps Server cache, which can be followed in this link.
Uninstall the extension from CollectionSettings, remove the extension from local Manage Extensions. Then upload again the extension and install it in the collection.
I am trying to publish a package to gitlab pypi registry. What is the repository url we need to use to publish to a group package registry?.
I tried using this https://gitlab.example.com/api/v4/groups/id/packages/pypi
but it is throwing 404 now found.
The api https://gitlab.example.com/api/v4/groups/id/packages/ returns a empty array for me.
But when I manually take the registry from the UI pypy, npm etc are present.
Publishing to individual project repositories is working fine.
https://gitlab.example.com/api/v4/projects/id/packages/pypi
I run into the same problem.
As far as I understand, groups don't have their own registries. If you go in your group settings, you won't see the option to activate it.
Groups are only placeholders to organize projects, they don't hold any data.
What you see in the UI when clicking on the group registry is the aggregation of all the registries of the projects inside that group.
This is only a search UI, not a registry per se.
Bottom-line is that you have to publish your artefacts to a specific project.
Note that you can have a dedicated project to hold only your registry, and have all your code repositories publish in the same registry.
We are using Azure Devops to publish a private nuget server. Currently we have only published 5 of our own nuget packages, however a subset of third-party nuget packages are also showing. I do not have any upstream sources enabled.
Is this normal behavior? I am able to delete them, but it's not clear how they are ending up there in the first place. We are not pushing them. Any help is appreciated.
Rob
Try to open the packages that not yours, and check the Publisher in the package. Publisher lists Who and How publish the package.
I forked application to android studio and when I try to make a pull request:
I get :
Can't Create Pull Request
Push failed:
failed to push some refs to 'https://github.com/projectname.git'
What is the right way to do that?
Note :
I can commit and update my projects but I can't make pull request to other projects.
This is obviously an authentication problem. There are WAY too many unknowns, so I doubt anyone can give you a definitive answer. Here are the steps to investigate in order to solve it:
Is your GitHub Account authenticated with your Android Studio installation? Check your Android Studio Settings.
In order to authenticate you need to generate an Access Token through your Github account settings and use that token as seen in the picture above. When generating a new token, normally I would advise you to be careful with the permissions you grant to it. For debugging your issue, generate a new one with full access to everything and delete it as soon as you resolve your issue.
Last, if both of the above steps are done correctly and you still can't open a PR. Make sure the repository you trying to open a PR on, allows third party users to perform such actions.
NOTE: You can always commit code in your local repository. That lives in your local environment (a.k.a. your computer) and you have full permission to do whatever you please with it. That doesn't mean the changes you do locally, will be reflected in the remote repository (a.k.a. the one hosted at Github servers).
First you need to install git client and configure with Android studio then you need to enable git into android studio from VCS option. and then you can see on toolbar 2 icon will come for push and pull request.
by these two option you can do pull and push very easly.
please have look this.
http://prntscr.com/hgvbxw
reference-https://javapapers.com/android/android-studio-git-tutorial/
I would like to use Azure git deployment with a product I am working on. We reference a 3rd party library which is privately supplied and not available on Nuget.
Azure syncs with the git repo as you would expect, but when it compiles it fails with errors saying it is unable to find the types within the 3rd party library.
The library is checked in to git in the bin folder.
How can I get Azure to reference this library when compiling?
There should be nothing special about doing this on Azure Web Apps vs doing it locally. If your assembly is committed and you reference it from its committed location, everything should just work.
If it doesn't, please try running through the steps in this document to help identify the issue.
You should be able to use standard NuGet practices to make this work. Looking at the documentation for Package Sources you just need to add the package source (like myget.org) to the nuget.config file place this at the same level as you *.sln file.