Skip to content
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

pipe job output in $EDITOR #889

Open
teto opened this issue Feb 22, 2024 · 0 comments
Open

pipe job output in $EDITOR #889

teto opened this issue Feb 22, 2024 · 0 comments

Comments

@teto
Copy link

teto commented Feb 22, 2024

this is a longshot but I had these crazy ideas:

  1. we have one messy jobs where I would like to have the job collapsible sections locally https://docs.gitlab.com/ee/ci/jobs/#custom-collapsible-sections (and see/convert them into neovim "folds")
  2. we also have playwright's logs, a software to check the rendering of a website against snapshots. The dream would be to display those images in the job output. As far as gitlab is concerned, I dont think this will ever be possible, not in the next 3 years at least. But with lab, I think it could be possible to have the picture shown in terminal via sixel/ the kitty protocol or timg. Even if it's not possible to get the raw bytes, what would be possible if I could pipe the job into my own program is to postprocess it:
  • identify some sections in the output to create the folds
  • identify paths towards images and display them in the terminal via https://github.com/hzeller/timg for instance (or image.nvim within neovim). This implies that I retreive the artifacts from the job I guess. This could be done by the postprocessing script but I would like to plug that into lab ci view that can find the latest sent pipeline (I dont want to write this part).

What do you think ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant