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

Component CI Pipeline #216

Closed
jlucas9 opened this issue Sep 25, 2023 · 3 comments
Closed

Component CI Pipeline #216

jlucas9 opened this issue Sep 25, 2023 · 3 comments
Assignees
Labels
DSM Distributed Systems Missions

Comments

@jlucas9
Copy link
Contributor

jlucas9 commented Sep 25, 2023

Can leverage examples from https://github.com/nasa/sample_app

Will need to update our component sample app.

@jlucas9 jlucas9 added the DSM Distributed Systems Missions label Sep 25, 2023
@Isgaroth-the-Green
Copy link
Contributor

I believe the next step is to check that the sample_app works within cFS and then compare it to the sample in NOS3 (at which point the CI tests in sample_app can be leveraged); I have not been able to get cFS compiling properly, though. It always gives an error regarding stubs, approximately
/usr/bin/ld: cannot find -lut_core_api_stubs: No such file or directory
and
/usr/bin/ld: cannot find -lcoverage-sample_lib-stubs: No such file or directory
The command (I think) which gives this error is
/usr/bin/cc -g CMakeFiles/coverage-sample_app-sample_app_uitls-testrunner.dir/coveragetest/coveragetest_sample_app_utils.c.o CMakeFiles/coverage-sample_app-sample_app_utils-object.dir/home/jstar/Documents/code/cFS/apps/sample_app/fsw/src/sample_app_utils.c.o -o coverage-sample_app-sample_app_utils-testrunner -pg --coverage -lut_core_api_stubs ../../../osal/ut_assert/libut_assert.a -lcoverage-sample_lib-stubs libcoverage-sample_app-stubs.a libcoverage-sample_app-stubs.a libsample_app_ut_common.a ../../../osal/ut_assert/libut_assert.a ../../../osal/libosal_bsp.a -lpthread -ldl -lrt

@jlucas9
Copy link
Contributor Author

jlucas9 commented Jun 13, 2024

Opted to just do NOS3 level CI and not with each component individually. So when you commit to the top level of NOS3 with the new component submodule it'll kick off, but not before then.

jlucas9 added a commit that referenced this issue Jun 13, 2024
jlucas9 added a commit that referenced this issue Jun 14, 2024
* [#216] First attempt at build workflow;

* [#216] Removed specific branches from build workflow;

* [#216] Removed sudo and added make prep;

* [#216] Added missing docker dependency;

* [#216] Break config and fsw into different runs in build.yml;

* [#216] Avoid docker in docker and run build-fsw;

* [#216] Attempt to get submodules recursively;

* [#216] Added sim job to build workflow;

* [#216] Attempt to use checkout@v4;
@jlucas9
Copy link
Contributor Author

jlucas9 commented Jun 14, 2024

Merged and squashed to dev

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
DSM Distributed Systems Missions
Projects
Archived in project
Development

No branches or pull requests

2 participants