Replies: 1 comment 1 reply
-
Missing an option to specify a Moreover, the assumption that the release service is the same as the packager's may need to be revised. Someone may want to release distributions to GitLab while publishing some package manager files to GitHub. Could you file a ticket for the first issue? Will get it fixed by the next release 😅 |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have/need the following setup:
A. Project A (Java project, using gradle, producing a distribution. A Cli, JAVA-BINARY). It's hosted in a deeply nested group on gitlab.com. For example gitlab.com/acme/foo/bar/ProjectA
B. A dedicated project used as a homebrew tap. For example gitlab.com/acme/foo/bar/homebrew-tap
What assumption does jreleaser do about the relationship of the above?
If I try to configure jreleaser to use repo owner+user combo using either
Jreleaser fails the release with 404. I think is caused by that jreleaser seems to
https://gitlab.com/api/v4/user/{userId}/projects
. The issue is that this returns an empty list (seems to be described in GitLab API docs https://docs.gitlab.com/ee/api/projects.html#list-user-projects)If I configure Jreleaser with
release
with an explicit Project Identifier the release works!However, this seems to confuse the Homebrew packager. It continues to push the brew Formual + overriding the README in "Project A". From my digging there seems to be some assumption that the brew packager just reuses the same repo-config as the releaser?
It doesn't matter that I've explicitly configured a different owner/user for the brew packager.
The trace from jreleaser looks like this
Notice the switch at line 4. It logs that it's working towards the repo I configured in the brew packager, but then proceeds to use the project identifier from the release.
What seems to be missing is the option to specify
projectIdentifier
for the brew packager. From what I understand the gitlabl API doesn't seem to support discovering repositories inside groups based on user identity.Beta Was this translation helpful? Give feedback.
All reactions