From 327f80924188ebf1392592aa078b67053a2a1d00 Mon Sep 17 00:00:00 2001 From: Jeremy Huard Date: Tue, 10 Feb 2026 19:50:09 +0100 Subject: [PATCH 1/2] Updated README.md --- README.md | 6 +++--- WorkshopGuide.md | 28 ++++++++++++++-------------- 2 files changed, 17 insertions(+), 17 deletions(-) diff --git a/README.md b/README.md index 8da932c..afab5cc 100644 --- a/README.md +++ b/README.md @@ -1,6 +1,6 @@ -[![MATLAB](https://github.com/simkaryote/MATLAB-SimBiology-DevOps-Workflow-Example/actions/workflows/ci.yml/badge.svg)](https://github.com/simkaryote/MATLAB-SimBiology-DevOps-Workflow-Example/actions/workflows/ci.yml) -[![Tests](https://img.shields.io/badge/Tests-Open_Test_Report-blue)](https://simkaryote.github.io/MATLAB-SimBiology-DevOps-Workflow-Example/tests/) -[![Coverage](https://img.shields.io/badge/Coverage-Open_Code_Coverage_Report-orange)](https://simkaryote.github.io/MATLAB-SimBiology-DevOps-Workflow-Example/coverage/) +[![MATLAB](https://github.com/ChezJe/MATLAB-SimBiology-DevOps-Workflow-Example/actions/workflows/ci.yml/badge.svg)](https://github.com/ChezJe/MATLAB-SimBiology-DevOps-Workflow-Example/actions/workflows/ci.yml) +[![Tests](https://img.shields.io/badge/Tests-Open_Test_Report-blue)](https://ChezJe.github.io/MATLAB-SimBiology-DevOps-Workflow-Example/tests/) +[![Coverage](https://img.shields.io/badge/Coverage-Open_Code_Coverage_Report-orange)](https://ChezJe.github.io/MATLAB-SimBiology-DevOps-Workflow-Example/coverage/) # MATLAB®/SimBiology® DevOps Workflow Example diff --git a/WorkshopGuide.md b/WorkshopGuide.md index b2cd1e4..bdc3a0b 100644 --- a/WorkshopGuide.md +++ b/WorkshopGuide.md @@ -19,19 +19,19 @@ In this workshop, you will: ## Table of Contents  [Workshop Requirements](#H_34C2FB57) - [Part 1: Getting the workshop files and configuring GitHub for automated testing and results publishing](#TMP_155c) + [Part 1: Getting the workshop files and configuring GitHub for automated testing and results publishing](#TMP_5736) - [Part 2: Generating your first tests](#TMP_0497) + [Part 2: Generating your first tests](#TMP_133e) - [Part 3: Finding existing tests and measuring coverage](#TMP_6b12) + [Part 3: Finding existing tests and measuring coverage](#TMP_4f07) - [Part 4: Updating badges, committing our changes, and pushing to GitHub](#TMP_9425) + [Part 4: Updating badges, committing our changes, and pushing to GitHub](#TMP_9895) - [Part 5: Create a pull request, watch GitHub Actions automatically test your changes and publish results](#TMP_3a37) + [Part 5: Create a pull request, watch GitHub Actions automatically test your changes and publish results](#TMP_162d) - [Part 6: Compile the App in the CI workflow and download the artifact](#TMP_83f7) + [Part 6: Compile the App in the CI workflow and download the artifact](#TMP_6581) - [Workshop wrap\-up and additional information](#TMP_2033) + [Workshop wrap\-up and additional information](#TMP_0e25) @@ -56,7 +56,7 @@ The following steps cover all of the things you will need to successfully comple - The workshop leverages the free repository and CI capabilities offered by GitHub and GitHub Actions - Go to: [**https://github.com/signup**](https://github.com/signup) - + # Part 1: Getting the workshop files and configuring GitHub for automated testing and results publishing @@ -308,7 +308,7 @@ Click on the 'Run App' shortcut to start the app in MATLAB: ![image_20.png](WorkshopGuide_media/image_20.png) - + # Part 2: Generating your first tests @@ -529,7 +529,7 @@ Congratulations! You just created multiple tests for your MATLAB code! It was easier than you thought, right? - + # Part 3: Finding existing tests and measuring coverage @@ -868,7 +868,7 @@ It looks like we've achieved full statement coverage for [`generateSimFun`](./co ![image_65.png](WorkshopGuide_media/image_65.png) - + # Part 4: Updating badges, committing our changes, and pushing to GitHub @@ -1088,7 +1088,7 @@ At this point, all of your changes will be pushed to GitHub. ![image_85.png](WorkshopGuide_media/image_85.png) - + # Part 5: Create a pull request, watch GitHub Actions automatically test your changes and publish results @@ -1249,7 +1249,7 @@ The code coverage report looks like this: Now anyone that visits your repository can immediately see the quality of your code, explore your test and code coverage results, and will have more confidence in the code you are writing! - + # Part 6: Compile the App in the CI workflow and download the artifact @@ -1350,7 +1350,7 @@ Once the `Deploy/ Release (main)` job is done, a new artifact is available at th You can now download the CTF file and upload it to your Web App Server! - + # Workshop wrap\-up and additional information From b59c0021e01c766e176befa56654e1746b666ab2 Mon Sep 17 00:00:00 2001 From: Jeremy Huard Date: Tue, 10 Feb 2026 20:00:54 +0100 Subject: [PATCH 2/2] added compilation step --- .github/workflows/ci.yml | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml index 4f92018..96432e0 100644 --- a/.github/workflows/ci.yml +++ b/.github/workflows/ci.yml @@ -99,7 +99,7 @@ jobs: - name: Run buildtool uses: matlab-actions/run-build@v2 with: - tasks: test # change to compile + tasks: compile # change to compile # Configure GitHub Pages to accept your artifact uploads - name: Setup Pages @@ -113,12 +113,12 @@ jobs: with: path: results # Upload results - # # Upload compiled CTF file to deploy Web App - # - name: Upload CTF file - # uses: actions/upload-artifact@v6 - # with: - # name: WebApp_CTF - # path: WebAppArchive/*.ctf + # Upload compiled CTF file to deploy Web App + - name: Upload CTF file + uses: actions/upload-artifact@v6 + with: + name: WebApp_CTF + path: WebAppArchive/*.ctf # Publish reports to GitHub Pages so they can be viewed in a browser - name: Deploy to GitHub Pages