Conversation
133425e to
9cf91bc
Compare
|
There's a handful of other references to CircleCI, should we clean those up as well? |
.circleci/config.yml
Outdated
There was a problem hiding this comment.
Just to clarify, is the intention to keep this around? I would have expected the config to be removed altogether.
There was a problem hiding this comment.
Nope. The real step is to click the big red button on the CircleCI website, I just wanted this to be green for now since CircleCI complained when I deleted the file.
changelog: Internal, Continuous Integration, Remove CircleCI
9cf91bc to
9583647
Compare
thank you for catching, deleted these |
| # Disable lograge when computing coverage and not in CircleCI, where lograge is required. | ||
| # This enables scanning for view test coverage with `rake test:scan_log_for_view_coverage` | ||
| config.lograge.enabled = !ENV['COVERAGE'] || ENV['CI'] |
There was a problem hiding this comment.
Just to confirm, should we still be enabling this given the other half of the condition?
| # Disable lograge when computing coverage and not in CircleCI, where lograge is required. | |
| # This enables scanning for view test coverage with `rake test:scan_log_for_view_coverage` | |
| config.lograge.enabled = !ENV['COVERAGE'] || ENV['CI'] | |
| # Disable lograge when computing coverage, where lograge is required. | |
| # This enables scanning for view test coverage with `rake test:scan_log_for_view_coverage` | |
| config.lograge.enabled = !ENV['COVERAGE'] |
There was a problem hiding this comment.
It didn't impact the current coverage calculation (https://gitlab.login.gov/lg/identity-idp/-/jobs/51849), so it seems ok for now.
With #6614 live, we should be able to drop CircleCI if we want 🙂