Skip to content

ci: membrowse integration#10189

Merged
dgarske merged 1 commit intowolfSSL:masterfrom
michael-membrowse:master
Apr 14, 2026
Merged

ci: membrowse integration#10189
dgarske merged 1 commit intowolfSSL:masterfrom
michael-membrowse:master

Conversation

@michael-membrowse
Copy link
Copy Markdown
Contributor

Description

MemBrowse memory footprint tracking in CI (Following a discussion with wolfSSL team)

I've configured four targets in membrowse-targets.json, all on Cortex-M4 with minimal test code linked so it doesn't affect the memory tracking:

  • gcc-arm-cortex-m4
  • gcc-arm-cortex-m4-baremetal
  • gcc-arm-cortex-m4-min-ecc
  • gcc-arm-cortex-m4-tls12

It includes:

  • membrowse-targets.json - defines the build targets with setup and build commands
  • membrowse-report.yml - runs on every push to master and on PRs
  • membrowse-comment.yml - comments on PRs with a memory usage summary
  • membrowse-onboard.yml - one-time workflow to load historical reports

To get started:

  1. Create an account at membrowse.com
  2. Create a project to get an API key.
  3. Set it as a GitHub secret called MEMBROWSE_API_KEY

The workflows will handle the rest.

Full docs are available at docs.membrowse.com.

Happy to help if any questions come up during integration.

@wolfSSL-Bot
Copy link
Copy Markdown

Can one of the admins verify this patch?

@dgarske
Copy link
Copy Markdown
Contributor

dgarske commented Apr 10, 2026

Okay to test. We are in contact with contributor.

@michael-membrowse
Copy link
Copy Markdown
Contributor Author

Create a project for wolfssl on membrowse.com so the report jobs would not fail :)

@dgarske dgarske merged commit 9ed79a2 into wolfSSL:master Apr 14, 2026
407 of 422 checks passed
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.

3 participants