I have been evaluating it for some time, testing different scenarios and trying different configurations. During this time, I have deleted and recreated my repositories a number of times. Each time, I have had to go back and reassign all of the permissions to each repository.
Currently, I have decided to use a single repository for common code, and then a separate repository for each product that will be produced.
Now, I am just about to take the leap and start using Plastic SCM in earnest. But before I do that, I have a question: is there a way to inherit/assign permissions on a repository from another repository? E.g. I set up all permissions on 'Repo A', and then inherit/assign those same permissions on 'Repo B'.
I am sure that I will be adding more repositories as we produce more products, and I would like to find the easiest way bring them online.
You can define a set of permissions for the repository server by right clicking a repository and clicking on Repository Server permissions:
Then all the repositories will inherit permissions from the repository server.
Hope it helps.
Related
I want to implement pre-receive hooks on the GitLab server side but we don't have access to the file system. Is there any way I can handle it with GitLab-ci? I want to get control over what can and can't be pushed to the repository.
One possible workaround would be for developers to:
push to a gateway repository
pull from an official one.
(both on GitLab)
You can then associate a job on the first one, on push:, in order to validate what has been pushed.
If validated, the job push the commit to the second official repository.
It's possible to implement pre-recieve hooks in gitLab but that comes when we have access to file system. For now, I have added gitlab-ci that will check on every merge request on protected branches and let all developers push to temp branches.
We have a Github organization, which is broken into teams.
I want to use Jenkins github plugin to just scan my teams folder, is this possible?
So far I can only get it to scan the whole org which has thousands of repos in it, or scan my user which also picks up other repos outside the team.
I have tried scanning for <ORG>/teams/<TEAM> but Jenkins seems to think that is a user and looks in the user api rather than org.
I know I could use a repo name filter, but currently the repos dont have a standard enough name to do that on and renaming them would be a pain as all links and clone would need updating.
Any help most appreciated.
I'm beginning to suspect that this is not possible. I was hoping that I could set up custom access control in Gerrit so that a particular role (defined in TF) would not have read access to a specific branch in a repo.
However, it appears that users with this role are unable to clone the repo at all. I was hoping they'd be able to clone and just not beb able to check out the restricted branch.
Just wondering if anyone else has enountered this and might be able to confirm the behaviour I'm seeing. I did see another thread here recommending gitolite for partial copies but I'm restricted to using TF/Gerrit.
Thanks!
I'm looking for a way to automatically add +2 permissions for certain refs for a lot of projects in Gerrit and unfortunately it seems there are no API calls to modify access rights, only to read them. Do you have any idea how to modify refs permissions for a big amount of projects?
I'm using Gerrit 2.9.
Thanks.
One possibility would be to create a batch script to modify the project.config for those projects and commit them back to gerrit.
This is how you can checkout the project.config for the All-Projects, it works the same for other projects: http://blog.bruin.sg/2013/04/how-to-edit-the-project-config-for-all-projects-in-gerrit/
Simply put:
Create list of project you want to change
Iterate over the lest
Checkout the refs/meta/config ref
Use script to modify project.config
Commit and push back to the server
More information about the project.config: http://gerrit-review.googlesource.com/Documentation/config-project-config.html
I followed Empower Jenkins with Artifactory video on YouTube. Basically, I added a new user to artifactory and granted it deploy permissions. Then I configured system configuration on Jenkins and tested that the configurations were right.
I created a new job and tried to set the deployment task to deploy it to artifactory. The problem is there is no repository on the dropdown.
I want to know how to fix this.
Try saving the job and reloading it.
The logic behind this behavior is to avoid a long list of repositories. Some users have hundreds of local repositories which takes a long time to display. By entering credentials, you can display a filtered list containing only relevant repositories.
There is an open issue to add a refresh button so there will be no need to save the job prior to displaying the list.
Update
This issue was resolved with the release of version 2.2.3 of the plugin. For more info see HAP-483