Github Actions

[marcomelloni]

This pull request introduces new CI workflows for the MATLAB Agent and Simulation Bridge projects, while also deprecating an older workflow for Simulation Bridge tests. Additionally, it updates the pytest.ini configuration to include code coverage reporting. These changes aim to streamline CI processes and enhance test reporting.

CI Workflow Additions:

• .github/workflows/matlab-agent-ci.yml: Added a new CI workflow for the MATLAB Agent, including steps for linting, formatting checks, testing, and building distribution artifacts.
• .github/workflows/simulation-bridge-ci.yml: Added a new CI workflow for the Simulation Bridge, with similar steps to the MATLAB Agent workflow, but includes coverage reporting and artifact uploads.

CI Workflow Deprecation:

• .github/workflows/simulation-bridge-tests.yml: Removed the older Simulation Bridge test workflow, consolidating its functionality into the new CI workflow.

Test Configuration Update:

• pytest.ini: Updated pytest settings to enable coverage reporting, including branch coverage and XML output for integration with tools like Codecov.

[codecov]

Welcome to Codecov 🎉

Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests.

Thanks for integrating Codecov - We've got you covered ☂️

[prasadtalasila]

@marcomelloni Some suggestions:

1. Please have separate github actions for Matlab and Simulation Bridge. For example, see different workflows and one workflow. The trick is to trigger a workflow only if changes happen in certain directories.
2. Run the unit and integration tests. The Matlab specific tests can be skipped of course.
3. Upload artifacts (whl and zip files). The results of poetry build can be uploaded to the build page. Please see this example and this can be done at the end of each workflow file.
4. It is probably better to consolidate the three action files into one. The sequence of checks could be formatting, linting, testing, coverage reporting, building and uploading artifacts.

[prasadtalasila]

please remember to set expiration time of one hour for the artifacts.

[marcomelloni]

One hour isn’t supported, so the shortest possible setting is 1 day

[prasadtalasila]

@marcomelloni Please copy the simulation-bridge-ci.yml into matlab-agent-ci.yml and adapt it for Matlab Agent. Thanks.

[marcomelloni]

.github/workflows/matlab-agent-ci.yml I added a new CI workflow for the MATLAB Agent, excluding tests and the uploading in codecov.

.github/workflows/simulation-bridge-ci.yml It's now one-single job. I set expiration time of one day for the artifacts because one hour isn’t supported

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud