• Icon: Sub-task Sub-task
    • Resolution: Done
    • Icon: Major Major
    • None
    • Kiali QE Sprint 4

      We need internal git repository for things like:

      • dockerfiles for jenkins docker slaves
      • openshift templates
      • installation scripts

      Part of this task is to investigate options we have for internal git repositories (there is not just one)

            [SWSQE-93] Create internal git repository

            Based on voting I created new gerrit project: https://code.engineering.redhat.com/gerrit/#/admin/projects/kiali-qe-utils

            For push access: git clone ssh://<yourAccount>@code.engineering.redhat.com/kiali-qe-utils
            For read only: git clone http://git.host.prod.eng.bos.redhat.com/git/kiali-qe-utils.git

            You need to be part of jbossqe ldap group and have configured gerrit. Details here (it's for jon-utils but applies for kiali-qe-utils too): https://mojo.redhat.com/docs/DOC-159477

            Filip Brychta added a comment - Based on voting I created new gerrit project: https://code.engineering.redhat.com/gerrit/#/admin/projects/kiali-qe-utils For push access: git clone ssh://<yourAccount>@code.engineering.redhat.com/kiali-qe-utils For read only: git clone http://git.host.prod.eng.bos.redhat.com/git/kiali-qe-utils.git You need to be part of jbossqe ldap group and have configured gerrit. Details here (it's for jon-utils but applies for kiali-qe-utils too): https://mojo.redhat.com/docs/DOC-159477

            I like #2

            Kevin Earls (Inactive) added a comment - I like #2

            +1 on #1

            Hayk Hovsepyan added a comment - +1 on #1

            fbrychta@redhat.com I am +1 on #1

            Jeeva Kandasamy added a comment - fbrychta@redhat.com I am +1 on #1

            +1 on #2

            Matthew Mahoney added a comment - +1 on #2

            Filip Brychta added a comment - - edited

            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:

            1. continue using hawkular-qe-utils (gerrit) until https://gitlab.corp.redhat.com is ready and move
            2. create new gerrit project and move to https://gitlab.corp.redhat.com when it's ready
            3. create new repo in https://gitlab.cee.redhat.com (cee team instance), if the https://gitlab.corp.redhat.com is approved, we will have to move there because cee instance will be canceled probably
            4. 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://issues.redhat.com/browse/PNTSYSOPS-2390
            [2] - https://mojo.redhat.com/docs/DOC-1127529

            Filip Brychta added a comment - - edited 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 is approved, 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://issues.redhat.com/browse/PNTSYSOPS-2390 [2] - https://mojo.redhat.com/docs/DOC-1127529

            In my opinion: I prefer Gitlab, it is possible to use the same resources that we have on Github

            Guilherme Baufaker Rego (Inactive) added a comment - In my opinion: I prefer Gitlab, it is possible to use the same resources that we have on Github

            Matthew Mahoney added a comment - FYI Reference doc: https://mojo.redhat.com/docs/DOC-159477

            Another option for internal repository

            [ https://gitlab.cee.redhat.com/ | https://gitlab.cee.redhat.com/ ]

            Matthew Mahoney added a comment - Another option for internal repository [ https://gitlab.cee.redhat.com/ | https://gitlab.cee.redhat.com/ ]

            FYI: Another option for internal Repo
            _
            This request now can be done thru PNT DevOps One site at [1]. If you follow: Create ticket->Categories/Gerrit->Create New Gerrit Project, link should be [2].

            [1] https://redhat.service-now.com/pnt
            [2] https://redhat.service-now.com/pnt/?id=sc_cat_item&sys_id=8a97fe6113356600196f7e276144b01d _

            Matthew Mahoney added a comment - FYI: Another option for internal Repo _ This request now can be done thru PNT DevOps One site at [1] . If you follow: Create ticket->Categories/Gerrit->Create New Gerrit Project, link should be [2] . [1] https://redhat.service-now.com/pnt [2] https://redhat.service-now.com/pnt/?id=sc_cat_item&sys_id=8a97fe6113356600196f7e276144b01d _

              fbrychta@redhat.com Filip Brychta
              fbrychta@redhat.com Filip Brychta
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: