Move Scan PORO to CE [RUN AS-IF-FOSS]
What does this MR do?
This MR is related to Port SAST and Secret Detection rails platform code to GitLab CE
As part of GSOC2021, I will be working on Port SAST and Secret Detection rails platform code to GitLab CE for the issue described in #284689. A security report is deserialized from JSON using POROs under lib/gitlab/ci/reports/security/ . The "Scan" object (Gitlab::Ci::Reports::Security::Scan) is one of the most simple and so, as first step, to get familiar with the process of running tests in RUN AS-IF-FOSS and creating a merge request, in this MR I moved the Scan PORO and scan_spec.rb from under the EE namespace to CE.
Screenshots (strongly suggested)
Does this MR meet the acceptance criteria?
Conformity
-
I have included changelog trailers, or none are needed. (Does this MR need a changelog?) -
I have added/updated documentation, or it's not needed. (Is documentation required?) -
I have properly separated EE content from FOSS, or this MR is FOSS only. (Where should EE code go?) -
I have added information for database reviewers in the MR description, or it's not needed. (Does this MR have database related changes?) -
I have self-reviewed this MR per code review guidelines. -
This MR does not harm performance, or I have asked a reviewer to help assess the performance impact. (Merge request performance guidelines) -
I have followed the style guides. -
This change is backwards compatible across updates, or this does not apply.
Availability and Testing
-
I have added/updated tests following the Testing Guide, or it's not needed. (Consider all test levels. See the Test Planning Process.) -
I have tested this MR in all supported browsers, or it's not needed. -
I have informed the Infrastructure department of a default or new setting change per definition of done, or it's not needed.
Security
Does this MR contain changes to processing or storing of credentials or tokens, authorization and authentication methods or other items described in the security review guidelines? If not, then delete this Security section.
-
Label as security and @ mention @gitlab-com/gl-security/appsec -
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team