-
Notifications
You must be signed in to change notification settings - Fork 38
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
Truncate Logs from bottom up #423
Comments
Yes, I think a duplicate of #343 |
Hey @timja do you know when the checks-api-plugin update will be reflected in Jenkins Installer? Do we need a version update of this plugin to use that one? |
It should be there now I released it yesterday, no you don’t need to update the version here |
I can see it released at https://plugins.jenkins.io/checks-api/ It requires Jenkins 2.426.3 |
Hi @timja I want to make another PR to the checks-api-plugin, this one did not quite capture what I needed. I'm running into a bunch of issues trying to run the integration tests on my local machine. Are there any instructions on how to run those locally? |
should run them fine on maven 3.9.9+ and Java 17+ Try that, otherwise provide more details. |
Confirmed maven and Java version. Running
|
Weird. Can you provide:
and the full build log please. |
Details
|
Can you try with Java 17 or 21 please? We aren't testing / supporting Java 23 yet |
I see, adjusting maven to point to java 17 solved the issue, thank you for your help! |
What feature do you want to see added?
Hi,
Due to the GitHub character limit on the GitHub Checks api (see background here: #345), our logs often get truncated. We are wondering if you are open to truncating from the bottom of the logs up rather than the existing top down now, since most relevant failure logs are at the bottom. Or, is there an easy way you could make this configurable?
Thank you!
Upstream changes
No response
Are you interested in contributing this feature?
No response
The text was updated successfully, but these errors were encountered: