-
Notifications
You must be signed in to change notification settings - Fork 28
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
Output pipeline summary #66
Conversation
e8595dd
to
bff4661
Compare
I've just realised those URLs are API urls - I'll work out where the display urls are hidden. |
bff4661
to
b65b844
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, need to test out myself, not sure if using blueoceans internals is the best
src/main/java/io/jenkins/plugins/checks/status/BuildStatusChecksPublisher.java
Outdated
Show resolved
Hide resolved
26ca1c3
to
5b2d618
Compare
I've removed links for now, until we can work out how to make them useful, as there doesn't appear to be a way to easily deep link to a flow node. |
5b2d618
to
f4ffe8c
Compare
Tests failure example here: Compilation failure: Example for inspiration of how the CloudBees SCM reporter shows failures: it would be good if we could get the script that caused the failure in there |
Should be easy enough, will have a play tomorrow. Even bumping to Not that the version fettling particularly matters right now, but it'd be nice to get something green. |
I think you can add an exclusion for that |
For the table view, maybe you'll need: https://github.github.com/gfm/#tables-extension- |
src/test/java/io/jenkins/plugins/checks/status/BuildStatusChecksPublisherITest.java
Show resolved
Hide resolved
To be honest I’m not sure the Graph is terrible interesting, in larger pipelines it will be huge, aren’t we just interested in failed steps? And the input and output of those steps. Along with the stage / branch it failed on |
This new design will push the full tree view into ChecksOutput text, and summarise results in the summary: Summary
|
e5836cd
to
af2ae02
Compare
Once again, thwarted by |
Junit has some code around limiting the output if you check it’s publisher |
When you are developing a new feature you should increase the minor version in |
👍 That’s fine, but my frustration is that revapi passes locally! |
|
Co-authored-by: Tim Jacomb <21194782+timja@users.noreply.github.com>
src/main/java/io/jenkins/plugins/checks/status/BuildStatusChecksPublisher.java
Show resolved
Hide resolved
src/main/java/io/jenkins/plugins/checks/status/FlowExecutionAnalyzer.java
Outdated
Show resolved
Hide resolved
src/main/java/io/jenkins/plugins/checks/status/FlowExecutionAnalyzer.java
Outdated
Show resolved
Hide resolved
src/main/java/io/jenkins/plugins/checks/status/FlowExecutionAnalyzer.java
Show resolved
Hide resolved
src/main/java/io/jenkins/plugins/checks/status/BuildStatusChecksPublisher.java
Outdated
Show resolved
Hide resolved
Any other planned work? I'll try test it out soon |
Nothing planned for now |
New lines don't seem to be working for the build log / some issue: also see what happens with ansi colours: https://github.com/timja-org/junit-attachments-test/pull/7/checks?check_run_id=1801300909 tbh I think it might just be a spacing issue with the markdown needing another new line |
Yep, missing a trailing newline...I think just that... |
Fixed with another new line: Possible enhancement would be to strip ansi colour code's before sending |
If you prefer we ship we can do that and create a new issue for the above ^^ |
Ahh the mysteries of GitHub flavoured markdown |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
An amazing feature, huge thanks!!!
src/main/java/io/jenkins/plugins/checks/status/FlowExecutionAnalyzer.java
Outdated
Show resolved
Hide resolved
src/main/java/io/jenkins/plugins/checks/status/FlowExecutionAnalyzer.java
Outdated
Show resolved
Hide resolved
Successful build! 🚀 I'm looking forward to updating this plugin in Jenkins. |
Co-authored-by: Kezhi Xiong <august.xkz@gmail.com>
FYI https://github.community/t/undocumented-65535-character-limit-on-requests/117564/5?u=jglick |
ended up being implemented here btw: jenkinsci/github-checks-plugin#101 and API side: #68 |
Relating to jenkinsci/github-checks-plugin#89
Very much a draft, as I've bent a lot of plumbing to get this working, which I'll fix if it's felt this is something worth pursuing.
This piggy-backs on the logic from the
FlowGraphTable
to generate a simple textual representation of the pipeline graph.It produces an output that looks something like:
In progress
Unstable: something went wrong
Complete
Unstable: something went wrong
Error: hudson.AbortException: something went very wrong
Note that I've removed the checkout listener, as that will now be handled by the graph listener.