Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GitLab Load Platform and Platform Management #6

Open
jateodoro opened this issue Apr 25, 2016 · 6 comments
Open

GitLab Load Platform and Platform Management #6

jateodoro opened this issue Apr 25, 2016 · 6 comments

Comments

@jateodoro
Copy link

Hi, I'm John Arcy Teodoro, an Accenture DevOps resource in the PDC.

We've been using the ADOP Generation 5, and made some customization wherein we use GitLab instead of Gerrit. With this, we've edited the docker-compose file of the Gen5 for it to come with GitLab.

Using GitLab as our SCM Tool, we have customized this platform management as well, such that it will be compatible with GitLab. Basically we have just transformed the shell scripts to configure Gerrit into GitLab API calls.

Here are the links for the customized Load Platform and Platform Management:
https://github.com/arcyteodoroacn/adop-b-framework-gitlab-load-platform
https://github.com/arcyteodoroacn/adop-b-framework-gitlab-platform-management

@nickdgriffin
Copy link
Contributor

This is great stuff!

Would you be able to create the platform-management repository as a fork of this one please so that I can clone it and see the delta?

As I'm not familiar with GitLab, what is the purpose of creating groups and adding users to them? Is it not using the groups in LDAP?

Just trying to understand the difference between the two so I can have a think about how we can easily support both Gerrit and GitLab together, as well as potentially other SCM systems.

@jateodoro
Copy link
Author

Hi Nick,

Sure! I will do that.

The GitLab container configuration is already connected to the LDAP that comes with the Gen 5. I will add the GitLab config of the edited ADOP Gen 5 docker-compose.yml on the Read Me file of the GitLab Platform Management.

Comparing GitLab to BitBucket, a "Group" is equivalent to a Project and a "Project" is to a Repository.

The GitLab is configured to connect to the LDAP that comes with the Core Gen 5. However, the users are needed to log-on to GitLab before they get actually listed and be recognized by GitLab, thus they cannot be assigned to a Group nor a Project until they do so. This serves as a by-pass to that problem, as there are no GitLab API call to do an LDAP Login (however, there is an API Call to do a normal user log in). Still, after the users log-on to GitLab, you will be able to see their profile with some LDAP information like their CN.

@nickdgriffin
Copy link
Contributor

Thanks for the explanation - that's very similar to what happens in Gerrit then. Starting to think we'd benefit from a standard interface for SCM providers that the jobs could call and pick the SCM provider that is present and act accordingly.

@jateodoro
Copy link
Author

jateodoro commented Apr 28, 2016

I've added a "/compose" folder on the GitLab Load Platform for the edited docker compose files of the ADOP Core Gen 5 with the GitLab configs.

https://github.com/arcyteodoroacn/adop-b-framework-gitlab-load-platform/tree/master/compose

@jateodoro
Copy link
Author

Hi Nick,

I've already forked the Accenture Platform Management and I've pushed the GitLab modifications into it.

@kramos
Copy link
Contributor

kramos commented Jan 23, 2017

@nickdgriffin how does this link into pluggable scm?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants