[ https://issues.jboss.org/browse/SWSQE-93?page=com.atlassian.jira.plugin.s... ] Filip Brychta edited comment on SWSQE-93 at 4/5/18 9:09 AM: ------------------------------------------------------------ There is a ongoing effort to create general RedHat GitLab instance [1]. It's not ready yet and it's not clear when it will be. Goal is to have only one GitLab instance and merge all other instances [2]. I see following options: # continue using hawkular-qe-utils (gerrit) until https://gitlab.corp.redhat.com is ready and move # create new gerrit project and move to https://gitlab.corp.redhat.com when it's ready # create new repo in https://gitlab.cee.redhat.com (cee team instance), if the https://gitlab.corp.redhat.com, we will have to move there because cee instance will be canceled probably # create new gerrit project and stay there unless there will be some issue with that I like 2) because we will probably need just two internal repos, one for internal tooling and one for internal tests (see SWSQE-121). Majority will be in public repo. Also we can later decide if we want to move to https://gitlab.corp.redhat.com or not. 3) is also fine but it will require additional work if https://gitlab.corp.redhat.com is approved and ready [1] - https://projects.engineering.redhat.com/browse/PNTSYSOPS-2390 [2] - https://mojo.redhat.com/docs/DOC-1127529 was (Author: fbrychta): There is a ongoing effort to create general RedHat GitLab instance [1]. It's not ready yet and it's not clear when it will be. Goal is to have only one GitLab instance and merge all other instances [2]. I see following options: # continue using hawkular-qe-utils (gerrit) until https://gitlab.corp.redhat.com is ready # create new gerrit project and move to https://gitlab.corp.redhat.com when it's ready # create new repo in https://gitlab.cee.redhat.com (cee team instance), if the https://gitlab.corp.redhat.com, we will have to move there because cee instance will be canceled probably # create new gerrit project and stay there unless there will be some issue with that I like 2) because we will probably need just two internal repos, one for internal tooling and one for internal tests (see SWSQE-121). Majority will be in public repo. Also we can later decide if we want to move to https://gitlab.corp.redhat.com or not. 3) is also fine but it will require additional work if https://gitlab.corp.redhat.com is approved and ready [1] - https://projects.engineering.redhat.com/browse/PNTSYSOPS-2390 [2] - https://mojo.redhat.com/docs/DOC-1127529 -- This message was sent by Atlassian JIRA (v7.5.0#75005)