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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

jx3 cluster incompatibility with gitlab groups/subgroups #7980

Closed
iamjohnnym opened this issue Oct 26, 2021 · 3 comments
Closed

jx3 cluster incompatibility with gitlab groups/subgroups #7980

iamjohnnym opened this issue Oct 26, 2021 · 3 comments
Assignees
Labels
area/gitlab kind/enhancement An enhancement of an existing feature

Comments

@iamjohnnym
Copy link

Issue

馃憢 Hello Comrades.

I'm looking for some guidance on integrating Jenkins-X into our platform, with Gitlab being the SCM and groups/subgroups as part of our project path.

Example git project path.

  • gitlab.com/org/group/subgroup/project

I've seen a few issues related to this but it seems they lose steam and go rotten.

Replication

  • tf repo: gitlab.com/org/terraform/jx-stack
  • jx cluster: gitlab.com/org/cluster/jx-dev
  1. Create a terraform and jenkins-x cluster project within gitlab leveraging the group/subgroup feature.
  2. Clone https://github.com/jx3-gitops-repositories/jx3-eks-vault and https://github.com/jenkins-x/terraform-aws-eks-jx into the respective projects
  3. Update (jx_git_url)[https://github.com/jenkins-x/terraform-aws-eks-jx/blob/master/variables.tf#L415] to point to the jx cluster git within gitlab
  4. Launch stack

This will fail because the jx-requirements.yaml want to treat the repo path, https://gitlab.com/org/cluster/jx-dev, incorrectly. Whenever attempting to specify the Expected Behavior, it rewrites the jx-requirements.yaml file to the Actual Behavior.

Actual Behavior:

  environments:
  - key: dev
    owner: org
    repository: jx-stack

Expected Behavior:

  environments:
  - key: dev
    owner: org
    repository: terraform/jx-stack

Related Issues

@ankitm123
Copy link
Member

This is now set correctly in the latest version.
May be we can close?

@ankitm123 ankitm123 self-assigned this Dec 11, 2021
@ankitm123 ankitm123 added area/gitlab kind/enhancement An enhancement of an existing feature labels Jan 8, 2022
@ankitm123
Copy link
Member

/close
closing this as it works now.

@jenkins-x-bot
Copy link
Contributor

@ankitm123: Closing this issue.

In response to this:

/close
closing this as it works now.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/gitlab kind/enhancement An enhancement of an existing feature
Projects
None yet
Development

No branches or pull requests

3 participants