GitLab Commit is coming up on August 3-4. Learn how to innovate together using GitLab, the DevOps platform. Register for free: gitlabcommitvirtual2021.com

#305 - set back to master branch

10 jobs for feature/issue-305-auto-deploy-docker in 17 minutes and 59 seconds (queued for 3 seconds)
latest
Status Job ID Name Coverage
  Build
passed #1323653306
build

00:02:40

 
  Test
failed #1323653308
allowed to fail
code_quality

00:13:01

passed #1323653315
eslint-sast

00:02:01

failed #1323653310
allowed to fail
gemnasium-maven-dependency_scanning

00:07:35

passed #1323653312
license_scanning

00:02:22

passed #1323653313
secret_detection

00:01:08

passed #1323653316
semgrep-sast

00:10:25

passed #1323653319
spotbugs-sast

00:15:12

passed #1323653320
test

00:08:10

 
  External
passed codebeat

00:00:09

 
Name Stage Failure
failed
gemnasium-maven-dependency_scanning Test
 of vulnerability database

exit status 1
Uploading artifacts for failed job
Uploading artifacts...
WARNING: gl-dependency-scanning-report.json: no matching files
ERROR: No files to upload
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
code_quality Test
error: (CC::CLI::Analyze::EngineFailure) engine eslint failed with status 99 and stderr 
engine produced invalid output: {:message=>"Invalid JSON", :output=>"\n\n{\"type\":\"issue\",\"categories\":[\"Bug Risk\"],\"check_name\":\"eqeqeq\",\"description\":\"Expected '!==' and instead saw '!='.\",\"content\":{\"body\":\"# Require === and !== (eqeqeq)\\n\\nIt is considered good practice to use the type-safe equality operators `===` and `!==` instead of their regular counterparts `==` and `!=`.\\n\\nThe reason for this is that `==` and `!=` do type coercion which follows the rather obscure [Abstract Equality Comparison Algorithm](http://www.ecma-international.org/ecma-262/5.1/#sec-11.9.3).\\nFor instance, the following statements are all considered `true`:\\n\\n* `[] == false`\\n* `[] == ![]`\\n* `3 == \\\"03\\\"`\\n\\nIf one of those occurs in an innocent-looking statement such as `a == b` the actual problem is very difficult to spot.\\n\\n## Rule Details\\n\\nThis rule is aimed at eliminating the type-unsafe equality operators.\\n\\nExamples of **incorrect** code for this rule:\\n\\n```js\\n/*eslint eqeqeq: \\\"error\\\"*/\\n\\nif (x == 42) { }\\n\\nif (\\\"\\\" == text) { }\\n\\nif (obj.getStuff() != undefined) { }\\n```\\n\\nThe `--fix` option on the command line automatically fixes some problems reported by this rule. A problem is only fixed if one of the operands is a `typeof` expression, or if both operands are literals with the same type.\\n\\n## Options\\n\\n### always\\n\\nThe `\\\"always\\\"` option (default) enforces the use of `===` and `!==` in every situation (except when you opt-in to more specific handling of `null` [see below]).\\n\\nExamples of **incorrect** code for the `\\\"always\\\"` opti"}
Could not analyze code quality for the repository at /code
Uploading artifacts for failed job
Uploading artifacts...
WARNING: gl-code-quality-report.json: no matching files
ERROR: No files to upload
Cleaning up file based variables
ERROR: Job failed: exit code 1