-
Notifications
You must be signed in to change notification settings - Fork 20
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
shellcheck: use a new version of run-shellcheck.sh
#182
Conversation
... to configure maximum amount of wall-clock time taken by a single shellcheck process Related: https://issues.redhat.com/browse/OSH-655 Closes: csutils#182
... to configure maximum amount of wall-clock time taken by a single shellcheck process Related: https://issues.redhat.com/browse/OSH-655 Closes: csutils#182
... to configure maximum amount of wall-clock time taken by a single shellcheck process Related: https://issues.redhat.com/browse/OSH-655 Closes: csutils#182
... to configure maximum amount of wall-clock time taken by a single shellcheck process Related: https://issues.redhat.com/browse/OSH-655 Closes: csutils#182
... to configure maximum amount of wall-clock time taken by a single shellcheck process Related: https://issues.redhat.com/browse/OSH-655 Closes: csutils#182
... so that we get equivalent scan results to the old version of the shellcheck plug-in. Related: https://issues.redhat.com/browse/OSH-655 Closes: csutils#182
... so that we get equivalent scan results to the old version of the shellcheck plug-in. Related: https://issues.redhat.com/browse/OSH-655 Closes: csutils#182
... so that we get equivalent scan results to the old version of the shellcheck plug-in. Related: https://issues.redhat.com/browse/OSH-655 Closes: csutils#182
... so that we get equivalent scan results to the old version of the shellcheck plug-in. Related: https://issues.redhat.com/browse/OSH-655 Closes: csutils#182
... so that we get equivalent scan results to the old version of the shellcheck plug-in. Related: https://issues.redhat.com/browse/OSH-655 Closes: csutils#182
... initially developed for Konflux CI. The updated version runs more processes of `shellcheck` in parallel, each of them with a strictly set timeout (currently 30s of wall-clock time). Related: https://issues.redhat.com/browse/OSH-655 Resolves: https://issues.redhat.com/browse/OSH-733
... that do not support `--format=json1`. Related: https://issues.redhat.com/browse/OSH-655
... so that we get equivalent scan results as if we scanned all scripts at once. Related: https://issues.redhat.com/browse/OSH-655
... so that we get equivalent scan results as if we scanned all scripts at once. Related: https://issues.redhat.com/browse/OSH-655
... to configure maximum amount of wall-clock time taken by a single shellcheck process Related: https://issues.redhat.com/browse/OSH-655
... to configure maximum number of scripts scanned by a single shellcheck process Related: https://issues.redhat.com/browse/OSH-655
... so that we get equivalent scan results to the old version of the shellcheck plug-in. Related: https://issues.redhat.com/browse/OSH-655 Closes: csutils#182
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Thank you, @kdudka.
@kdudka What about adding a simple ShellCheck test to CI? diff --git a/tests/simple_build/shellcheck.fmf b/tests/simple_build/shellcheck.fmf
new file mode 100644
index 0000000..f73f614
--- /dev/null
+++ b/tests/simple_build/shellcheck.fmf
@@ -0,0 +1,11 @@
+summary: Test analysis using GCC analyzer
+test: ./test.sh
+framework: beakerlib
+environment:
+ TEST_PACKAGE: dracut
+ TEST_TOOL: shellcheck
+component:
+ - csmock
+recommend:
+ - csmock
+duration: 1h |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
... so that we get equivalent scan results to the old version of the shellcheck plug-in. Also remove the filter for `note` events, which were specific to the `gcc` output of ShellCheck. Related: https://issues.redhat.com/browse/OSH-655 Closes: csutils#182
@kdudka The following patch should fix the test failures on C9S hosts: diff --git a/tests/simple_build/test.sh b/tests/simple_build/test.sh
index 9c0106e..3e684da 100755
--- a/tests/simple_build/test.sh
+++ b/tests/simple_build/test.sh
@@ -7,6 +7,10 @@ TEST_PACKAGE="${TEST_PACKAGE:-}"
TEST_TOOL="${TEST_TOOL:-}"
TEST_USER="csmock"
+# Add CS Koji
+BEAKERLIB_rpm_fetch_base_url+=( "https://kojihub.stream.centos.org/kojifiles/packages/" )
+BEAKERLIB_rpm_packageinfo_base_url+=( "https://kojihub.stream.centos.org/koji/" )
+
rlJournalStart
rlPhaseStartSetup
# use the latest csutils in the Testing Farm
|
... so that we get equivalent scan results to the old version of the shellcheck plug-in. Also remove the filter for `note` events, which were specific to the `gcc` output of ShellCheck. Related: https://issues.redhat.com/browse/OSH-655
Thanks for review and testing! |
... initially developed for Konflux CI. The updated version runs more processes of
shellcheck
in parallel, each of them with a strictly set timeout (by default 30s of wall-clock time).Related: https://issues.redhat.com/browse/OSH-655
Resolves: https://issues.redhat.com/browse/OSH-733