Cirrus-ci-docs: View logs during build

Created on 31 Jan 2019  路  16Comments  路  Source: cirruslabs/cirrus-ci-docs

During a page reload, all logs of an unfinished task would be deleted. Is there a way of retaining them or viewing them before the task is finished? Thanks!

enhancement high-priority

Most helpful comment

Cirrus now caches last 100Kb of logs of currently running tasks and when you expand the logs they will be loaded while new logs continue to appear as they come. 馃檶

All 16 comments

Hey @Wetitpig, sorry about that! Right now only new log lines are available while task is progressing. Added this enhancement to a roadmap. 馃檶

Nice!

@fkorotkov Also could console output highlighting be enabled? Thank you!

@Wetitpig do you have an example where it doesn't work quite well? Cirrus CI already tried to highlight ansi output.

For example, words like warning and note in this build should be highlighted, as seen here. Thanks!

I鈥檓 interested to see if we could implement methods like the ones the python library colorama does.

@Wetitpig @RDIL created #155 about the coloring issue.

@Wetitpig I'm not an expert on the CIrrus internals. I examined this behavior from the POV from what is logged into the google storage buckets. It appears the updates only happen after the run finishes. That implies Cirrus-CI is caching the output internally before recording to persistent storage. To me, that means it may be a heavy-ask, for Cirrus to track per-client indexes into that cache. It's also likely to be similarly difficult to sync. the internal cache with the bucket object (for direct monitoring). Though I agree the current situation is less than ideal, it does encourage keeping your script-sections short and quick, which seems to be a general "best practice" anyway :smile: Point is...I don't expect a solution in this space to happen any time soon.

Live logs seldom work. If we expand the step node while tasks are running, it rarely shows anything until the task is over (we often need to refresh the page to see the content of log).
Sometimes, however, I see [object Object] while waiting for live logs:

image

Edit:
after few more minutes of wait, it looked like this:
image

Hi @fkorotkov IMO the lack of logs during execution is a critical issue for the steps requiring live information. That's for example the case for continuous deployment pipelines.

@simonbrandhof agreed. Will prioritize it. 馃檶

Cirrus now caches last 100Kb of logs of currently running tasks and when you expand the logs they will be loaded while new logs continue to appear as they come. 馃檶

Super

I still do not see the logs while the task is running.

@probonopd is it always not working for you or occasionally?

Now that you are saying it: Occasionally... Will keep watching it.

Was this page helpful?
0 / 5 - 0 ratings