Skip to content
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

Tdj/update workflow to build on stax #465

Merged
merged 1 commit into from
Nov 21, 2023

Conversation

tdejoigny-ledger
Copy link
Contributor

@tdejoigny-ledger tdejoigny-ledger commented Nov 20, 2023

Description

Update workflow to be able to build some apps on Stax

Changes include

  • Bugfix (non-breaking change that solves an issue)
  • New feature (non-breaking change that adds functionality)
  • Breaking change (change that is not backwards-compatible and/or changes current functionality)
  • Tests
  • Documentation
  • Other (for changes that might not fit in any category)

@codecov-commenter
Copy link

codecov-commenter commented Nov 20, 2023

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (6408413) 59.47% compared to head (a6e057f) 59.47%.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #465   +/-   ##
=======================================
  Coverage   59.47%   59.47%           
=======================================
  Files          12       12           
  Lines        1683     1683           
=======================================
  Hits         1001     1001           
  Misses        682      682           
Flag Coverage Δ
unittests 59.47% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@tdejoigny-ledger tdejoigny-ledger force-pushed the tdj/update_workflow_to_build_on_Stax branch 3 times, most recently from 3a00178 to 11a2877 Compare November 21, 2023 12:21
@tdejoigny-ledger tdejoigny-ledger force-pushed the tdj/update_workflow_to_build_on_Stax branch from 11a2877 to a6e057f Compare November 21, 2023 12:23
@tdejoigny-ledger tdejoigny-ledger marked this pull request as ready for review November 21, 2023 12:43
@@ -262,6 +328,14 @@ jobs:
build_path=$(echo '${{ env.build_path_list}}' | sed -n 's/.*"${{ matrix.repo_name }}"[[:space:]]*:[[:space:]]*"\([^"]*\)".*/\1/p')
echo "build_path=$build_path" >> $GITHUB_ENV

- name: Build for Stax
run: |
if echo "${{ env.build_for_stax_list }}" | grep -q "${{ matrix.repo_name }}" || [[ "${{ inputs.run_stax }}" ]]; then
Copy link
Contributor

Choose a reason for hiding this comment

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

You can get rid of the run_stax argument I think :)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

could be useful to check if an app build on Stax...

Copy link
Contributor

Choose a reason for hiding this comment

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

I would argue that we have the app tester for this ?

Copy link
Contributor

Choose a reason for hiding this comment

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

I would argue that we have the app tester for this ?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I prefer to keep it for now because it's easier to run directly the workflow with run_stax flag in order to see which app listed in SDK CI is Ok for build and could be added in build_for_stax list

.github/workflows/build_all_apps.yml Show resolved Hide resolved
@tdejoigny-ledger tdejoigny-ledger merged commit 1a6258c into master Nov 21, 2023
288 of 458 checks passed
@tdejoigny-ledger tdejoigny-ledger deleted the tdj/update_workflow_to_build_on_Stax branch November 21, 2023 17:07
@xchapron-ledger xchapron-ledger mentioned this pull request Dec 5, 2023
6 tasks
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