support rendering pipeline output files

[jstrachan]

it would be awesome if pipelines can generate reports (test reports, code coverage reports, lint reports, whatever) as files that get stored in a bucket - then when viewing a Pipeline we can optionally view the associated files in a PipelineActivity.

I was wondering about something like...

be able to render a file in a bucket relative to a pipeline folder in the UI

e.g. to view a pipeline/log its something like...

http://dashboard-jx.$domain/$org/$repo/$branch/$build

I wonder if we supported something like...

http://dashboard-jx.$domain/$org/$repo/$branch/$build/file/$path

which would look in a canonical bucket location (rather like we use for log files) to find the file which could be plain text or html.

Ideally we could render a similar nav bar/breadcrumb on this page so that you could navigate from the file/report to the Pipeline/log page etc.

view the list of files associated with a PipelineActivity

so when viewing a Pipeline page right now, if there are any reports in the PipelineActivity we could add a drop down menu/tree thingy so that folks could navigate from the log page to the file page?

The attachments on a PipelineActivity can be created here btw... https://github.com/jenkins-x/jx-api/blob/master/pkg/apis/jenkins.io/v1/types_pipeline.go#L66

When we've both of those things then any step could publish some reports to a bucket and from the UI we could link to a report or link to a log and navigate between all of the views via the UI

testing...

I'm working on a little linter pipeline for v3 which generates a lint output file for each language in a PR which we could then link to each report in the UI via the GitHub Checks on a PR etc

[hervelemeur]

Kinda related, how about posting (some of) these reports as comments in the PRs?

[jstrachan]

will do

[jenkins-x-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://jenkins-x.io/community.
/lifecycle stale

[jenkins-x-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://jenkins-x.io/community.
/lifecycle rotten