-
Notifications
You must be signed in to change notification settings - Fork 789
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
GitHub repos named .github
and .github-private
are not supported
#8499
Comments
.github
and .github-private
are not supported due to limiting supported repo names to GitLab min spec.github
and .github-private
are not supported due to limiting supported repo names to GitLab min spec
.github
and .github-private
are not supported due to limiting supported repo names to GitLab min spec.github
and .github-private
are not supported due to limiting repo names to GitLab min spec
.github
and .github-private
are not supported due to limiting repo names to GitLab min spec.github
and .github-private
are not supported
Somewhat related PR - jenkins-x-plugins/jx-gitops#287 |
In regards to this error example:
The source of the issue appears to stem from the normalizing of When digging down the logic, it seems like much of the code paths end up using the ToValidValue helper method in the naming module of jenkins-x/jx-helpers, which ends up stripping characters like
What I experienced locally, is that JX3 correctly triggers a At least that is what appears to be occurring... |
The workaround we are currently using is simply to use |
Summary
GitHub supports two special case repos for Customizing your organization's profile and other functionality, which must be named
.github
or.github-private
. Currently, Jenkins-X only supports repo names that are valid Kubernetes LabelsThe relevant error message (mentioned below) outputs the following RegEx:
(([A-Za-z0-9][-A-Za-z0-9_.]*)?[A-Za-z0-9])?
This issue manifests after Pipelines are triggered by Lighthouse and are being executed on a Build Pod. The
jx-variables
Step fails to find aBuild number
often resulting in a successful Pipeline run with no recordedPipeline Activity
.Steps to reproduce the behavior
.github
or.dottest
jx import
CLI command will likely timeout due to the same issue)build Pod's log snippet
Expected behavior
The jx dashboard should show progress and log information for Pipeline.
Actual behavior
No Pipeline activity is recorded in jx dashboard, due to
jx gitops variables
step failing to "failed to find BuildNumber".Jx version
The output of
jx version
is:The text was updated successfully, but these errors were encountered: