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
Feature: Catch error "Project must have a description" when creating a release. #684
Comments
Hi @xrow . Am I correct with the assumption you are trying to create a release for a ci component to publish it to the new ci catalogue? These projects indeed need a project description according to the docs. But I agree with you, we could have a better error logging to improve the user experience. I will try to get some time for that in the next weeks. |
@JonasSchubert This is correct. |
Also in my tests tag_name is also problematic. Should we overwrite the default somehow or let the user figure it out? v1.0.0 is not semver according to gitlab. [root@localhost ci-tools]# curl --header 'Content-Type: application/json' --header "PRIVATE-TOKEN: glpat-XXX" |
I discovered another hidden message "Release cannot contain more than 30 components". When publishing a ci/cd catalog. |
All of this are new limitations at the GitLab side. We should not try to work around this, but instead properly surface the error message so that users know what is going on. At least for the semver issue they will change this to allow the |
@fgreinacher Agree |
A never ending story :-). Yet another message. {"message":"Build component error: Spec must be a valid json schema"} |
@xrow Can you provide a sample project that shows (some of) the silent failures you have mentioned in the original post? That would greatly help improve the behavior. 🙇 |
@fgreinacher You can do it with any repository very easy. Just remove for example the project description and add it back in later. Well here is a silent example https://gitlab.com/xrow-public/ci-tools/-/jobs/6682443516#L410
|
@xrow Thanks for sharing the logs! Starting with https://github.com/semantic-release/gitlab/releases/tag/v13.1.0 we will show the error message in the logs. Let us know if this can be further improved 🙇 |
Maybe this is new in gitlab. Each project needs to have a description before creating a release. Can you maybe add a check if that value is not emtpy and then do a proper error message? Or pass the error along from the returning response. Currently it silently fails without message. just having the info HTTPError: Response code 422 (Unprocessable Entity).
The text was updated successfully, but these errors were encountered: