You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Previously, an actively running Actions' job would only stream the logs generated after the page was loaded. Logs emitted prior to the page loading would only be available after the job completed. This made it challenging to monitor the progress of jobs as they were running, particularly those that could take a long time to complete.
This feature includes improvements to the way we stream logs and will also show the previous 1,000 lines when visiting the logs of an actively running job.
Intended Outcome
Customers will now be able to visit the logs of a running job and immediately get context of its progress and status. This enable developers to understand if a workflow is behaving as expected much faster.
How will it work?
Upon visiting the logs of an actively running Actions jobs, customers will now see the previous 1,000 lines of logs and any new lines emitted thereafter.
The text was updated successfully, but these errors were encountered:
Summary
Previously, an actively running Actions' job would only stream the logs generated after the page was loaded. Logs emitted prior to the page loading would only be available after the job completed. This made it challenging to monitor the progress of jobs as they were running, particularly those that could take a long time to complete.
This feature includes improvements to the way we stream logs and will also show the previous 1,000 lines when visiting the logs of an actively running job.
Intended Outcome
Customers will now be able to visit the logs of a running job and immediately get context of its progress and status. This enable developers to understand if a workflow is behaving as expected much faster.
How will it work?
Upon visiting the logs of an actively running Actions jobs, customers will now see the previous 1,000 lines of logs and any new lines emitted thereafter.
The text was updated successfully, but these errors were encountered: