I recently installed the Sonatype OSS 3.14.0-04. I new to nexus and I am creating roles stuff. I have seen nexus 2, but I did not have any involvement in setting it up or administrative work. What I seem to be having issues with now is deleting assets as the default admin. I added a package to the hosted maven-snapshot repo and I want to delete it using the GUI. When I click on Browse this is all I see. I did read the old post here in stackoverflow How to delete a Sonatype Nexus OSS(3) Component from a Repository. But the user was able to see The components under browse.
If you click into the repository you uploaded it to, you should get a list view of all components and assets within that repository.
If you click on the item you want to delete or if it's a folder, the contents of the folder you should be able to delete them from there.
See https://help.sonatype.com/display/NXRM3/Browsing+Repositories+and+Repository+Groups for more information (specifically the last screenshot shows the delete asset button).
Related
I ran the migration utility to upgrade our Nexus 2 (2.14) to Nexus 3.40-02.
The Nexus 3 migration tool brought all the content from our 2.14 instance but subtly changed the URLs to all our Maven Repos.
For instance
https://nexus.foo.net/content/repositories/releases
became
https://nexus.foo.net/repository/releases
If I go in the Nexus 3 UI with the Admin account, browse to repostiories/settings I can see the URL but not change it.
This seems really dangerous since the Nexus URLs are encoded in poms by hundreds or more end-users consuming the jars. Why would the migration tool change the URL like this? Also I can find nothing in the Documentation about why the URL field is visible under "Settings" but cannot be changed to fix it.
Does anyone have any ideas about what went wrong?
Thanks.
The URI pattern will change after the upgrade. However you can activate a switch to enable the old URI pattern.
"By default, Nexus Repository Manager 2 uses a different URL pattern to expose repositories and repository groups than Nexus Repository Manager 3. While automated tools and CI can be reconfigured to utilize the new patterns, it is possible to change a configuration on the Nexus Repository Manager end to allow your upgrade to use the old pattern as well. This can be done in $data-dir/nexus3/etc/nexus.properties by adding:"
org.sonatype.nexus.repository.httpbridge.internal.HttpBridgeModule.legacy=true
https://help.sonatype.com/display/NXRM3/Upgrade+Procedures#UpgradeProcedures-ConfiguringLegacyURLPaths
Newbe to Team Services...
Vs2015 Desktop Community for original setup.
I stumbled through the setup of our ...visualstudio.com account and it is working on two PCs. I went down the GIT path but I'm not really clear on the process, I just kept banging on it until it worked. It is working (mostly) for two VB.Net WinForm projects on two PCs.
I'm now setting up a brand new PC and I installed VS2017. I didn't install any extra software for GIT (can't find any directions for source control install for that either, TS GIT quick start doesn't mention setting up GIT) I logged into the visualstudio cloud from the new install and cloned one of the projects from the cloud GUI. The files came down OK but the project type is evidently wrong because the Solution Explorer always lists all files and I can't open a form in the GUI. I also tried to use VS2017 to clone/download the project with the same result.
Do I need to install GIT in a fresh install of VS2017? Download from where/how to get a proper hookup with VS2017?
Why am I getting the files OK but the project type is not VB.Net Winform? Can that be tweaked or should I start over?
I was able to download using the .zip option from visualstudio.com but it isn't connected to a local or cloud repository. I'm not sure it is a good idea to connect these "out of band" files to an exisitng repository. The project is of the correct type and it builds OK and works.
Thanks!
View of solution in broken project:
It’s unnecessary to install extra software after you installed VS2017.
In short, use VS to work with git repo on VSTS (visual studio team services), you just need to connect your VSTS account in VS and clone a local repo as working copy for VSTS git repo. Operations in VS 2017 should be:
Connect your VSTS account in VS2017.
VS2017 -> team explorer -> manage connections -> connect to project.
If your VSTS account (sign up email address) hasn’t connected yet, click add an account. After that, you can select your VSTS project/repo to connect/clone.
Clone VSTS git repo locally.
If you didn’t clone git repo in step1, then right click a VSTS repo -> clone.
Work on the local repo.
After successfully cloned a repo, you are working on the local repo, you can also find the local repo’s name and branch you are working for in the right bottom of VS2017. Now the solutions should be same as what you find in VSTS.
And you can make change and commit for them. And then push your local commit(s) to VSTS git repo.
For VS2017, there are two forms to view solutions and files: solution related and all files/folders.
If you can’t find .Designer.vb and .resx files, you must use the second mode as the above graph.
To view all files/folder, you can switch the view to first mode as below graph.
How can you make multiple clones of the same repository on your local computer with GitHub Mac Desktop? After you make the first clone, the repository name disappears from the GitHub Desktop clone choice list.
Related to this, I cloned a GitHub repository onto my local machine, then decided I didn't want it in that location. I simply deleted (trashed) the old repository and tried to clone it again, but could not, because the repository name was not listed. It turned out that because the repository was still in the trash, GitHub Desktop didn't recognize it as gone. I emptied the trash and it saw that it was gone and asked if I wanted to remove the repository. I answered YES and then the repository name appeared in the clone choice list.
You can't clone the same repo twice from the GUI so, instead use command line git clone for that and then you can use the File->Add Local Repository item to select the path and it will show up.
The annoying thing is that having multiple clones of the repo in the Repository List will cause them all to have exactly the same name, because GitHub Mac Desktop doesn't show the paths. Fortunately the order doesn't change and you can always (right click->open in terminal) to see which is which.
If you want to delete a repo that you have cloned - you need to remove it in Github for Mac (right click->Remove) which just removes it from being tracked in the repository list. Now you can delete it from the Finder.
Delete from Finder and then remove from Github for Mac works too.
In my GitHub for Windows, there are two repositories that always appear on the list of GitHub repositories. One was created by me. The other was a project I stopped watching long ago.
I want to remove these items form the list of GitHub repos in GitHub for Windows.
When I move my mouse over the repo name, the pop-up menus says I can clone it etc, but 'stop tracking repository' is grayed out.
I have tried cloning the project. Then 'Stop tracking repository' is not grayed out. I click on this item. The repo does not disappear from the list of repos, but 'stop tracking...' is grayed out again,
Any suggestions on how to make these 'ghost' repos disappear from the list?
"Stop Tracking" is always grayed when used on the GitHub repo associated to my account.
It works only for my "Local repositories".
If you have deleted your repo on the GitHub side (or stopped wathcing a repo), and a "refresh" on the GitHub for Windows isn't enough to update your GitHub repo list, then you need to contact GitHub support.
I am new to this forum but i found very quick responce from active developers.
i have query with technical diffrence between "GIT" and Tortoise "SVN". if any one has work on it please give me detail description.
thanks
tousif shaikh.
You mean surely a difference between Git and svn? Tortoise is just a GUI for (mostly) svn.
Take a look at this wiki article: https://git.wiki.kernel.org/index.php/GitSvnComparison
or at this thread: https://stackoverflow.com/a/161572/1758762 :
SVN is one repo and lots of clients. GIT is a repo with lots of client repos, each with a user. It's decentralised to a point where people can track their own edits locally without having to push things to an external server.
SVN is designed to be more central where GIT is based on each user having their own GIT repo and those repos push changes back up into a central one. For that reason, GIT gives individuals better local version control.
and so long ...
SVN workflow:
The trunk directory represents the latest stable release of a
project.
Active feature work is developed within subdirectories under branches
When a feature is finished, the feature directory is merged into
trunk and removed.
Git workflow :
A Git repository stores the full history of all of its branches and
tags within the .git directory.
The latest stable release is contained within the master branch.
Active feature work is developed in separate branches.
When a feature is finished, the feature branch is merged into master
and deleted.