-
Notifications
You must be signed in to change notification settings - Fork 790
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
Cannot build a project imported with the --nested-repo option #8193
Comments
/assign |
@ankitm123 @rawlingsj @jstrachan Many thanks! |
Replace:
with (basically replace REPO_NAME with subgroup-repo)
For example, for my test I have The latest jx version has the fixes. |
@ankitm123 Can you please check if #8453 is a related issue? |
Any updates on this issue? |
Hello,
We need your help with building a project using the the
maven-quarkus-buildpack
. The project is imported with the--nested-repo
option (adding support for nested repositories in GitLab).Currently our build is failing in one of the last steps
promote-helm-release
.We tried to debug this today and found following conflicts:
step-promote-changelog
the pipeline was not able to find our Helm chart. We realized this by the fact that there was a log messageno charts
which we tracked to this script:jx/.github/workflows/jenkins-x/changelog.sh
Line 13 in 19684a1
my-organisation-my-suborganisation-my-service-name
(concatenated name with dashes). This chart folder is created during the project import with the--nested-repo
optionstep-promote-helm-release
step was failing with the error.jx/variables.sh
generated during the build we saw that theREPO_NAME
variable was not matching the directory where the chart is located. The variable had the valuemy-organisation/my-suborganisation/my-service-name
(concatenated with forward slash)We are providing here the output of the build logs and the
.jx/variables.sh
cc @ankitm123 and @marziman
The text was updated successfully, but these errors were encountered: