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

feat: add build_command option #15

Merged
merged 6 commits into from
Jul 11, 2023
Merged

feat: add build_command option #15

merged 6 commits into from
Jul 11, 2023

Conversation

b31ngd3v
Copy link
Contributor

@b31ngd3v b31ngd3v commented Jul 9, 2023

closes #11

Copy link
Contributor

@terriko terriko left a comment

Choose a reason for hiding this comment

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

We should probably have a very trivial test for this (just to avoid any regression where the build command isn't executed).

Since we don't have anything real to build, maybe a testbuild.py script that has an output you could check for, and maybe an option that gives it an error output so you can test src/scanner.py lines 42-44 too?

I'm going to merge this and file an issue for the test, though, so you're not waiting on a second review.

@terriko terriko merged commit 85ffcd0 into intel:main Jul 11, 2023
7 checks passed
@b31ngd3v b31ngd3v deleted the build branch July 14, 2023 19:24
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.

feat: scanning build output
2 participants