Some users of the gitlab server are registered as developer under a given group. I would like these users to be able to create repositories under the namespace of the group.
As currently set, the users do not even have the "Namespace" field under the "Project path" field when creating new projects.
Is this possible ?
1st option you have is to change by yourself the namespace after the developer created the project:
project -> settings/gear icon -> edit project -> transfer project
2nd possible thing is to edit project_security_spec.rb or ability.rb
(i'm not familiar with that good enough to explain more...)
You could create an external service that uses the GitLab API to create the project. Using this method, you also have the chance to directly initialize the project with a README and so on.
(Don't know about the GitLab Version for this question is very old - but I came here with the same problem - so here is the answer for today)
Give the users the role "Maintainer" -> see: https://gitlab.com/help/user/permissions
Related
I'd like to add a Quick Look extension to my program, but in order to be useful, it would have to access the Core Data stack, which seems to require me to add an App Group and a provisioning profile to the project.
Until now, it has been possible for anyone to download the project from Github and compile and run it out of the box. All project targets are set to Team: None and Sign to Run Locally. If I add my provisioning profile to the project, this will no longer work. They will have to create and add their own provisioning profile and change the Signing & Capabilities settings on each of the 26 targets (there seems to be no way to do them all at once). And the profile will have to be renewed every year.
My question is, is there any way around this? Is such a major change really necessary for what amounts to accessing a file inside the program's own bundle (and another in its Application Support folder?)
EDIT: As was pointed out to me on the Apple Developer forum, you don't need a provisioning profile as long as you prefix the group name with the development team identifier. This still won't make it build out of the box, though. You will still need a developer account and set a team on every target.
I had missed that you are supposed to have a team identifier as the prefix for the group name. That still doesn't solve the problem that my project will no longer build out of the box for anyone who downloads it from Github, but it answers the question asked in the subject line.
I want to change an Azure DevOps project's Process from Scrum to Basic.
I read that:
Previously it was not possible to change between System Project Processes (eg. Scrum->Basic) in Azure Devops. Rather, it was only possible to switch between System & Inherited Processes of the same parent System Process.
But that it is now possible to switch between all Processes.
Documented Process A
According to this web page, I should be able to:
Organization Settings -> Boards -> Process -> Projects -> Scrum ->
Select "..." next to the Scrum Project -> Select "Basic" -> Save
However, this is what happens instead:
Organization Settings -> Boards -> Process -> Projects -> Scrum ->
There is no "..." next to any Projects
Documented Process B
Whilst I could not find the "Change process" option above, I could find the option mentioned on this web page:
Organization Settings -> Boards -> Process -> Processes -> Select
"..." next to the Basic Process -> "Change team projects to use Basic"
So I wonder whether this has replaced the the Documented Process A above OR whether it is in addition to it?
However, when I tried this I just get an error:
There are currently no projects available to change to the Basic
process.
AND this web page states that
Only those projects created from the Agile process or one that
inherits from Agile appear under the Available projects column.
Which seems like it is referring to the days when we could not switch between System Processes.
Other checks
I don't think this is related to permissions because I have "Basic" access, am the Project Administrator and I am also in the "Project Collection Administrators" group, which the documentation says gives me the permissions required to change a project's Process.
I have no Work Items either.
I have tried with combinations of System Project processes and inherited Project Processes. No change, still can't move to any Process based upon Basic.
The referenced web page's example is for Basic-to-Agile. I couldn't find any documented examples of the reverse: Agile->Basic, Scrum->Basic, etc. So I am wondering if this just doesn't work yet with Basic as the target?
I have submitted a Microsoft Support request without response so I am reaching out here.
There's no any limit about change one process to another. It seemed the method you tried was incorrect.
For example, here I has an project under Scrum process. Located to Scrum--> choose Projects-->then choose the ... icon for the project you want to change-->select Change process.
And then, you will see the selection about choosing process, choose one process that you want to change and save it:
Now, open the process which you chosen change just now and you will see the change has been succeed now.
You can refer this similar change way from Change a project process from Scrum to Agile
This worked for me:
First create an inherited process under Basic, say BasicEx, with all the same Work Item Types as under Scrum (this meant I had to add Bug, Feature, Impediment, Product Backlog Item), and first move to this process.
Then delete all the 4 manually created Work Item types (which will delete all associated work items, so if you want to preserve them, change them to Issue type first).
Then move the project to use the Basic process.
Then finally delete the BasicEx process.
Currently Azure DevOps supports change from inherited process template to another inherited template (with the same base process), and change only the following ways:
From Scrum to Agile.
From Agile to Scrum.
From Basic to Agile.
This is the reason you don't success to change from Scrum to Basic.
More information you can find here.
I've been through the docs several times and the best answer I can find is that all the .groovy files are loaded at initialization of the application, however, for the SaaS variant of Artifactory it says the user plugins are supported in the product matrix but there's absolutely no reference on how to get the user plugins installed and running. Maybe I'm tired and missing it but I keep ending up at this page in the wiki with no answer.
https://www.jfrog.com/confluence/display/RTF/User+Plugins#UserPlugins-PluginsLibDirectory
I am an admin user for the application but I can't see where user plugins are managed from the API, CLI or UI. Please point me in the right direction. Much appreciated!!!
create a support request. DevOps team will do it for you.
how do I delete a Team project from TFS?. I am using VS2012.
The situation is that a Team Project was created with the wrong name, and another one was created with the right name and all the code has been checked into that.
I just want to delete the wrongly created one. I cant find any specific help on this, although there are articles on how to do it on if your TFS is hosted on visualstudio.com.
Apologies if this is a noddy question but I have looked for the answer and cant find it...
Thanks in advance
Jonathan
You can use the "TFSDeleteProject" command line tool to delete the team project.
Here is the usage:
TFSDeleteproject [/q] [/force] [/excludewss] /collection:URL TeamProjectName
TFSDeleteProject permanently destroys the team project, after which it cannot be recovered. You should backup all important project data before using TFSDeleteProject.
Required permissions
To use the TFSDeleteProject command, you must be a member of the Team Foundation Administrators security group or the Project Administrators security group.
You can use the link to delete the team project using the administrator console.
How can I change the project owner in GitLab?
There are options in project settings, but in the "transfer" field, it does not recognize any username or anything. Is it possible to change the owner-permissions and root-privileges?
TL;DR
Move your project to a new group where both you and the other user are owners, then the other user must transfer it to his own namespace.
Background
The other answers obviously do not work to transfer a project to a different user, although the comments section of one is enough for someone to figure it out. Also there is this issue on GitLab itself that provides some insights.
My Situation
I installed and now administer a few instances of GitLab for a few small developer teams as well as one for my personal projects. Resultingly, I have run into numerous questions about this. I keep coming back to this question only to realize that it was never actually answered correctly.
The Namespace Problem
The issue that you face when doing this is that there can only be one owner of a project, but to transfer a project you have to own the namespace that you are transferring it to. To my knowledge there is no other way to move a project. For completeness, I'll add that the namespace here is, e.g., "gitlab.com/my-user-name/..." or "gitlab.com/my-group-name/...".
Solution
Because one user cannot "own" another namespace (not even admins), the only option to set up a scenario where two users own the same namespace is with a group. Perform the following steps to accomplish this.
Create a new group.
Add the user that you want to transfer your project to as an owner member of that group.
Transfer your project to that group (a namespace you manage because you are an owner).
Login as the other user, then transfer the group project to the "other user" namespace.
At this point you will be left as a master in the project. You can now remove yourself from the project entirely if desired.
You can add another owner to the project via:
Project -> Members -> Add members -> Select Owner as permission
Next you have to remove yourself from the project:
Project -> Members -> Click the red button behind your username
Now you left the project, and the user you entered before is now the owner.
You can basically create a group then add the project to a group, then from the group member setting add a new owner and you can leave the group yourself.
See screenshots
It is also possible to export the project and import it under a different user. This preserves commits and branches.
Settings -> Advanced -> Export Project
Then to import:
New Project -> Import Project -> Gitlab Export
If you need to do this for many projects, it's pretty convenient to do it via API:
import gitlab
gl = gitlab.Gitlab('https://gitlab.com', private_token='...')
gitlab_project = gl.projects.get("the-project-of-yours")
target_group = gl.groups.get("target-group-where-to-land")
gitlab_project.transfer_project(target_group.id)
https://docs.gitlab.com/ee/api/projects.html#transfer-a-project-to-a-new-namespace
https://docs.gitlab.com/ee/api/groups.html#transfer-project-to-group
https://github.com/python-gitlab/python-gitlab/blob/master/gitlab/v4/objects/projects.py#L461
In current version (10.2.4) you should do following:
Go to "Project" -> "Settings" -> Expand "Advanced settings" -> Scroll down to "Transfer project"
It involves multiple steps, but its possible.
Create a group and transfer project to the group
Invite new user to the group
Login with new user and transfer project to new user from group
However I think it is easier to maintain if you leave your repository in the group
Transfer menu are always at
Project => Settings => Advanced
In Gitlab 8.8.3 you are able to transfer a project.
Be careful. Changing the project's namespace can have unintended side effects ;)
Go to Project -> Settings -> Project Settings -> Scroll down to Transfer project
In GitLab Community Edition 9.3.5 if you are administrator you should go to Settings -> Members and change de role of the member you want.
For example, search John Doe, set the developer role, and now John Doe will be developer and won't be owner anymore.