I just upgraded my Sonatype Nexus instance from version 2.14-01 to 3.1.0-04.
I followed the upgrade steps and everything appeared to work correctly.
The problem I am having is I can no longer view the artifacts when I browse via explorer to my address:
http://XXX.XXX.XXX.XXX:8080/nexus/content/repositories/releases/aaa/bbb/bbb
Under Nexus 2.x, when I navigated to this path, I am able to see my versions and artifacts inside the specific version.
Is there a setting in Nexus I need to update to allow this functionality after the upgrade?
Thanks
There is change in the repositories location. Earlier it was content/repositories and now it is changed to repository/
To access content using old url after migration set the below property in nexus.properties.
org.sonatype.nexus.repository.httpbridge.internal.HttpBridgeModule.legacy=true
https://books.sonatype.com/nexus-book/reference3/install.html#config-legacy-url
Related
I have a 12.0.1 instance and I would like to upgrade to 12.0.2. I followed the guide here https://www.keycloak.org/docs/latest/upgrading/ however I do not seem to have the new option that was added here (https://github.com/keycloak/keycloak/commit/91a51c2dbeb770e0202e89b438fc16963a5eed21) in my UI. If I go to Server Info in the admin panel it shows 12.0.2 as the version.
What am I missing? Do I need to update the client separately? I downloaded the latest archive and copied the files from my old KEYCLOAK_HOME/standalone/ into the new folder and restarted keycloak. The DB was migrated from what I can tell but that UI options is just missing.
Do I need to do something to my existing realm to activate this feature?
Keycloak release 12.0.2 doesn't contain linked KEYCLOAK-16606 change. See the history of the commits: https://github.com/keycloak/keycloak/blob/12.0.2/federation/ldap/src/main/java/org/keycloak/storage/ldap/mappers/UserAttributeLDAPStorageMapper.java You need to build your own custom Keycloak release from the master or wait until change will be released.
I had a catalog of version 1.0.0
I made changes to the catalog with the same version, rancher still shows the old catalog.
I have read that it is because Rancher's caching mechanism.
Ok, I then incremented the version to 1.0.1
Rancher still shows the old one.
Then made increment to 1.0.2, 1.0.4 ..etc. Still the old one.
How to force Rancher to use the real catalog instead of showing some old one??
How to clear calatog cache?
rancher v2.4.3
edit: the only solution currently is to increment version in bigger steps like 1.1.x
Here is what I have found:
Rancher doesnt provide any information about the Catalog cache or any kind of possbility to reset it.But it seems it clears the cache for the catalog once the corresponding repository deleted from the Catalog page.
Clearing the cache:
Delete the helm repository then wait the clear-cache mechanism to take effect. It takes ~1 min. Then readd the repository and it seems to work.
Whether the new catalog is in effect can be checked in the Preview section on the App Launch/Upgrade Form.
To be more specific:
The caches are stored here (at least in case of dockerized Rancher):
/var/lib/rancher/management-state/catalog-cache
So -after the deletion- once you see the corresponding cache folder has been removed you are good to go.
We have a setup where Rancher-2.5.9 is used. In this Deleting a repository is not needed. A catalog refresh works fine (select the catalog, choose the menu option, and click on refresh). I can see the new version pushed a few minute back are available in the dropdown.
But unfortunately the same is not working on another setup where rancher-2.6.3 exists. Need to debug more and see if the issue is there in the setup or in the rancher version.
Our build pipeline has been working fine, producing and saving packages to our Azure DevOps artifact feed. Although, we recently started seeing a strange failure in Visual Studio 2019 when trying to upgrade one of the packages to the latest version per to the following screenshot:
As the screenshot depicts, the package version 1.0.1-preview4 does exist but the project is not upgraded to it and version 1.0.1-preview3 has to be picked up instead to upgrade! Any idea what the root cause of this issue is and how to address this problem?
I run into this issue quite frequently and it is caused by Caching. Clearing your Nuget Cache will resolve the issue. See this StackOverflow post:
Package is not found in the following primary source
Apart from cleaning the cache, also check if the version 1.0.1-preview4 is valid(unlisted or deleted?) in your list.
Then use the filter to locate the View of the 1.0.1-preview4 package. Determine the view it belongs to, #Local, #Prerelease or #Release. After that go feed settings=>Views to check the related permissions:
Make sure your local account has the permission to the View the 1.0.1-preview4 package belongs to.
I tried to find the solution of my problem on google, many blogs and tried many suggestion but nothing is working.
My problem is like this:
TeamCity Solution Build is creating artifact and publishing it but the package version is not showing in visual studio package Manager Console and not even in Octopus Library External Feed test. Because of this all my builds are failing as octopus is not able to find the latest package which is being generated in the current build.
I dont remember making any change in setting or configuration of teamcity or octopus and this issue came up suddenly. Before this everything was working fine.
Can someone please help me in solving this issue as I'm stuck here?
I have already found an alternative which can be to push packages to Octopus repository and use the package from there but I dont want to change the configurations now and trying to fix this issue first.
Having (presumably) understood the motivation behind Nuget, I want to know, whether we still require internet access to download a package which is already being downloaded earlier for different project in different solution?
I believe you can even set up your own feed stored on the file system as described here.
You can setup your own local NuGet repository as As Denis Ivin has already said.
NuGet also has its own local machine cache which keeps NuGet packages that you have installed previously (C:\Users[UserName]\AppData\Local\NuGet\Cache). You can install these by selecting the Recent packages tab in the Manage Packages dialog.
Having your own local NuGet repository is probably better since the cache could be cleared.