Skip to content

Update circleci config #2022

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

Open
wants to merge 17 commits into
base: main
Choose a base branch
from
Open

Conversation

ryanrath
Copy link
Contributor

@ryanrath ryanrath commented Apr 2, 2025

Description

Moved the code coverage installation / setup step up so that we get more
info in the coverage data.

Added an or switch to the conditions under which code coverage data is
generated so that we can easily trigger coverage generation outside of
the nightly build.

Motivation and Context

Tests performed

Checklist:

  • The pull request description is suitable for a Changelog entry
  • The milestone is set correctly on the pull request
  • The appropriate labels have been added to the pull request

ryanrath added 2 commits April 2, 2025 13:43
Moved the code coverage installation / setup step up so that we get more
info in the coverage data.

Added an `or` switch to the conditions under which code coverage data is
generated so that we can easily trigger coverage generation outside of
the nightly build.
@ryanrath ryanrath force-pushed the update-circleci-config branch from dd764eb to ebf36c4 Compare April 2, 2025 17:43
@@ -500,7 +500,7 @@ echo ${arg_r}
echo
echo $PROCESS_FILE_INSTALL_PATH

~/bin/services restart
#~/bin/services restart
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please remove this line rather than adding commented out code.

condition:
or:
- and:
- equal: [ scheduled_pipeline, << pipeline.trigger_source >> ]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please can you add some documentation to explain how to trigger code coverage capture (this could be a readme or just comments in this file)

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

Successfully merging this pull request may close these issues.

2 participants