CI/CD logs are polluted by CLI progress in v3
See original GitHub issueAre you certain it’s a bug?
- Yes, it looks like a bug
Is the issue caused by a plugin?
- It is not a plugin issue
Are you using the latest version?
- Yes, I’m using the latest version
Is there an existing issue for this?
- I have searched existing issues, it hasn’t been reported yet
Issue description
Serverless v3 introduced a new logging interface that revamps progress reporting. While the progress logs look neat for interactive use, they introduce a lot of noise in CI/CD platforms that don’t support e.g. carriage returns in their rendered output.
Here’s an example of how they appear for us in Buildkite:

Service configuration (serverless.yml) content
N/A
Command name and used flags
serverless deploy
Command output
N/A
Environment information
Framework Core: 3.0.1 (local)
Plugin: 6.0.0
SDK: 4.3.0
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:26 (14 by maintainers)
Top Results From Across the Web
CLI progress bar - Support - Kopia Forum - Discourse
Trying to understand the CLI progress bar. Have a long running snapshot running since ... I really don't want to pollute the directory...
Read more >TI Linux CI/CD Snapshots - Texas Instruments
Disclaimer: Snapshots contain functionally verified new features or bug fixes, but the code may continue to evolve during further integration and testing.
Read more >Continuous Integration With Python: An Introduction
In this Python tutorial, you'll learn the core concepts behind Continuous Integration (CI) and why they are essential for modern software engineering teams....
Read more >Acronyms Abbreviations &Terms - FEMA Training
1) Airport, Port, and Terminal Security ... Board of Correction of Military Records ... Border Release Advance Screening & Selectivity.
Read more >Journal of Clinical Medicine - MDPI
Introduction: Chronic obstructive pulmonary disease (COPD) is the third cause of mortality and it is smoking-related. It is characterized by a non-reversible ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Not sure if this helps but most CI systems have explicitly set
CI=true
as an environment variable. Maybeserverless
should check that and use CI-appropriate logs.I’ll reopen for clarity.