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

Allow slash in name #388

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Allow slash in name #388

wants to merge 1 commit into from

Conversation

XLordalX
Copy link

This adds GitLab nested group support to pipelines.

@jenkins-x-bot
Copy link
Contributor

Hi @XLordalX. Thanks for your PR.

I'm waiting for a jenkins-x or todo member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

@jenkins-x-bot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To complete the pull request process, please assign ankitm123
You can assign the PR to them by writing /assign @ankitm123 in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@sonarcloud
Copy link

sonarcloud bot commented Oct 13, 2022

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@XLordalX
Copy link
Author

/assign @ankitm123

@ankitm123
Copy link
Member

Tests would be good to ensure we don't add regression. I added some changes to support nested gitlab repos, I must have missed certain parts. Thanks for looking into this and fixing it :)

@ankitm123
Copy link
Member

Does it fix issues around jx pipeline start? Curious ...

@XLordalX
Copy link
Author

XLordalX commented Oct 13, 2022

Yes it does, it gets stuck on the pipeline wait command because it's waiting for the wrong trigger:

waiting up to 20m0s for a trigger to be added to the lighthouse configuration in ConfigMap config in namespace jx for repository: org/subgroup-subproject
you can watch the boot job to update the configuration via: jx admin log
for more information on how this works see: https://jenkins-x.io/v3/about/how-it-works/#importing--creating-quickstarts

notice how it's attempting to wait for org/subgroup-subproject instead oforg/subgroup/subproject (notice the dash was replaced with a slash) which is added to the config ConfigMap. This change fixes that.

@ankitm123
Copy link
Member

Did u try --nested-repo flag when importing?

@XLordalX
Copy link
Author

Did u try --nested-repo flag when importing?

Yes. This is with —nested-repo.

@XLordalX
Copy link
Author

@ankitm123 I'm willing to write tests for this, but I'm not sure what needs to be tested. Can you help me out a bit?

Copy link
Member

@msvticket msvticket left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is the wrong fix for the problem. The method is meant for creating k8s resource names and they can not have /. Instead some other method (possibly new) should be used.

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

Successfully merging this pull request may close these issues.

None yet

4 participants