Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
be53ef4b
Commit
be53ef4b
authored
Aug 05, 2020
by
Alan (Maciej) Paruszewski
Committed by
Jarka Košanová
Aug 05, 2020
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Rewrite query to check resolved_on_default_branch
parent
3762f8b4
Changes
5
Hide whitespace changes
Inline
Side-by-side
Showing
5 changed files
with
100 additions
and
34 deletions
+100
-34
ee/app/models/ee/project.rb
ee/app/models/ee/project.rb
+6
-3
ee/app/models/vulnerability.rb
ee/app/models/vulnerability.rb
+12
-3
ee/changelogs/unreleased/218012-rewrite-query-to-fetch-reports.yml
...logs/unreleased/218012-rewrite-query-to-fetch-reports.yml
+6
-0
ee/spec/models/project_spec.rb
ee/spec/models/project_spec.rb
+62
-22
ee/spec/models/vulnerability_spec.rb
ee/spec/models/vulnerability_spec.rb
+14
-6
No files found.
ee/app/models/ee/project.rb
View file @
be53ef4b
...
@@ -233,9 +233,12 @@ module EE
...
@@ -233,9 +233,12 @@ module EE
self
.
tracing_setting
.
try
(:
external_url
)
self
.
tracing_setting
.
try
(:
external_url
)
end
end
def
latest_pipeline_with_security_reports
def
latest_pipeline_with_security_reports
(
only_successful:
false
)
all_pipelines
.
newest_first
(
ref:
default_branch
).
with_reports
(
::
Ci
::
JobArtifact
.
security_reports
).
first
||
pipeline_scope
=
all_pipelines
.
newest_first
(
ref:
default_branch
)
all_pipelines
.
newest_first
(
ref:
default_branch
).
with_legacy_security_reports
.
first
pipeline_scope
=
pipeline_scope
.
success
if
only_successful
pipeline_scope
.
with_reports
(
::
Ci
::
JobArtifact
.
security_reports
).
first
||
pipeline_scope
.
with_legacy_security_reports
.
first
end
end
def
latest_pipeline_with_reports
(
reports
)
def
latest_pipeline_with_reports
(
reports
)
...
...
ee/app/models/vulnerability.rb
View file @
be53ef4b
...
@@ -142,9 +142,18 @@ class Vulnerability < ApplicationRecord
...
@@ -142,9 +142,18 @@ class Vulnerability < ApplicationRecord
def
resolved_on_default_branch
def
resolved_on_default_branch
return
false
unless
findings
.
any?
return
false
unless
findings
.
any?
latest_successful_pipeline_for_default_branch
=
project
.
latest_successful_pipeline_for_default_branch
# We can't just use project.latest_successful_pipeline_for_default_branch
latest_pipeline_with_vulnerability
=
finding
.
pipelines
.
order
(
created_at: :desc
).
first
# because there's no guarantee that it actually ran the security jobs
latest_pipeline_with_vulnerability
!=
latest_successful_pipeline_for_default_branch
# See https://gitlab.com/gitlab-org/gitlab/-/issues/218012
latest_successful_pipeline
=
project
.
latest_pipeline_with_security_reports
(
only_successful:
true
)
# Technically this shouldn't ever happen.
# If an vulnerability was discovered, then we must have ran a scan of the
# appropriate type at least once.
return
false
unless
latest_successful_pipeline
finding
.
pipelines
.
exclude?
(
latest_successful_pipeline
)
end
end
def
user_notes_count
def
user_notes_count
...
...
ee/changelogs/unreleased/218012-rewrite-query-to-fetch-reports.yml
0 → 100644
View file @
be53ef4b
---
title
:
Fetch latest successful pipeline with security jobs to check if vulnerability
was resolved
merge_request
:
38452
author
:
type
:
changed
ee/spec/models/project_spec.rb
View file @
be53ef4b
...
@@ -1513,41 +1513,81 @@ RSpec.describe Project do
...
@@ -1513,41 +1513,81 @@ RSpec.describe Project do
end
end
describe
'#latest_pipeline_with_security_reports'
do
describe
'#latest_pipeline_with_security_reports'
do
let
(
:project
)
{
create
(
:project
)
}
let
(
:only_successful
)
{
false
}
let!
(
:pipeline_1
)
{
create
(
:ci_pipeline
,
project:
project
)
}
let!
(
:pipeline_2
)
{
create
(
:ci_pipeline
,
project:
project
)
}
let!
(
:pipeline_3
)
{
create
(
:ci_pipeline
,
project:
project
)
}
subject
{
project
.
latest_pipeline_with_security_reports
}
let_it_be
(
:project
)
{
create
(
:project
)
}
let_it_be
(
:pipeline_1
)
{
create
(
:ci_pipeline
,
:success
,
project:
project
)
}
let_it_be
(
:pipeline_2
)
{
create
(
:ci_pipeline
,
project:
project
)
}
let_it_be
(
:pipeline_3
)
{
create
(
:ci_pipeline
,
:success
,
project:
project
)
}
context
'when legacy reports are used'
do
subject
{
project
.
latest_pipeline_with_security_reports
(
only_successful:
only_successful
)
}
before
do
create
(
:ee_ci_build
,
:legacy_sast
,
pipeline:
pipeline_1
)
context
'when all pipelines are used'
do
create
(
:ee_ci_build
,
:legacy_sast
,
pipeline:
pipeline_2
)
context
'when legacy reports are used'
do
before
do
create
(
:ee_ci_build
,
:legacy_sast
,
pipeline:
pipeline_1
)
create
(
:ee_ci_build
,
:legacy_sast
,
pipeline:
pipeline_2
)
end
it
'returns the latest pipeline with security reports'
do
is_expected
.
to
eq
(
pipeline_2
)
end
end
end
it
"returns the latest pipeline with security reports"
do
context
'when new reports are used'
do
is_expected
.
to
eq
(
pipeline_2
)
before
do
create
(
:ee_ci_build
,
:sast
,
pipeline:
pipeline_1
)
create
(
:ee_ci_build
,
:sast
,
pipeline:
pipeline_2
)
end
it
'returns the latest pipeline with security reports'
do
is_expected
.
to
eq
(
pipeline_2
)
end
context
'when legacy used'
do
before
do
create
(
:ee_ci_build
,
:legacy_sast
,
pipeline:
pipeline_3
)
end
it
'prefers the new reports'
do
is_expected
.
to
eq
(
pipeline_2
)
end
end
end
end
end
end
context
'when new reports are used'
do
context
'when only successful pipelines are used'
do
before
do
let
(
:only_successful
)
{
true
}
create
(
:ee_ci_build
,
:sast
,
pipeline:
pipeline_1
)
create
(
:ee_ci_build
,
:sast
,
pipeline:
pipeline_2
)
end
it
"returns the latest pipeline with security reports"
do
context
'when legacy reports are used'
do
is_expected
.
to
eq
(
pipeline_2
)
before
do
create
(
:ee_ci_build
,
:legacy_sast
,
pipeline:
pipeline_1
)
create
(
:ee_ci_build
,
:legacy_sast
,
pipeline:
pipeline_2
)
end
it
"returns the latest succesful pipeline with security reports"
do
is_expected
.
to
eq
(
pipeline_1
)
end
end
end
context
'when
legacy
used'
do
context
'when
new reports are
used'
do
before
do
before
do
create
(
:ee_ci_build
,
:legacy_sast
,
pipeline:
pipeline_3
)
create
(
:ee_ci_build
,
:sast
,
pipeline:
pipeline_1
)
create
(
:ee_ci_build
,
:sast
,
pipeline:
pipeline_2
)
end
end
it
"prefers the new reports"
do
it
'returns the latest successful pipeline with security reports'
do
is_expected
.
to
eq
(
pipeline_2
)
is_expected
.
to
eq
(
pipeline_1
)
end
context
'when legacy used'
do
before
do
create
(
:ee_ci_build
,
:legacy_sast
,
pipeline:
pipeline_3
)
end
it
'prefers the new reports'
do
is_expected
.
to
eq
(
pipeline_1
)
end
end
end
end
end
end
end
...
...
ee/spec/models/vulnerability_spec.rb
View file @
be53ef4b
...
@@ -267,7 +267,7 @@ RSpec.describe Vulnerability do
...
@@ -267,7 +267,7 @@ RSpec.describe Vulnerability do
describe
'#resolved_on_default_branch'
do
describe
'#resolved_on_default_branch'
do
let_it_be
(
:project
)
{
create
(
:project
,
:repository
,
:with_vulnerability
)
}
let_it_be
(
:project
)
{
create
(
:project
,
:repository
,
:with_vulnerability
)
}
let_it_be
(
:pipeline_with_vulnerability
)
{
create
(
:
ci_pipeline
,
:success
,
project:
project
,
sha:
project
.
commit
.
id
)
}
let_it_be
(
:pipeline_with_vulnerability
)
{
create
(
:
ee_ci_pipeline
,
:success
,
:with_sast_report
,
project:
project
,
sha:
project
.
commit
.
id
)
}
let_it_be
(
:vulnerability
)
{
project
.
vulnerabilities
.
first
}
let_it_be
(
:vulnerability
)
{
project
.
vulnerabilities
.
first
}
let_it_be
(
:finding1
)
{
create
(
:vulnerabilities_occurrence
,
vulnerability:
vulnerability
,
pipelines:
[
pipeline_with_vulnerability
])
}
let_it_be
(
:finding1
)
{
create
(
:vulnerabilities_occurrence
,
vulnerability:
vulnerability
,
pipelines:
[
pipeline_with_vulnerability
])
}
let_it_be
(
:finding2
)
{
create
(
:vulnerabilities_occurrence
,
vulnerability:
vulnerability
,
pipelines:
[
pipeline_with_vulnerability
])
}
let_it_be
(
:finding2
)
{
create
(
:vulnerabilities_occurrence
,
vulnerability:
vulnerability
,
pipelines:
[
pipeline_with_vulnerability
])
}
...
@@ -276,14 +276,22 @@ RSpec.describe Vulnerability do
...
@@ -276,14 +276,22 @@ RSpec.describe Vulnerability do
context
'Vulnerability::Finding is present on the pipeline for default branch'
do
context
'Vulnerability::Finding is present on the pipeline for default branch'
do
it
{
is_expected
.
to
eq
(
false
)
}
it
{
is_expected
.
to
eq
(
false
)
}
end
context
'Vulnerability::Finding is not present on the pipeline for default branch'
do
context
'but pipeline is failed'
do
before
do
let!
(
:unsucessful_pipeline_with_vulnerability
)
{
create
(
:ee_ci_pipeline
,
:with_sast_report
,
:failed
,
project:
project
,
sha:
project
.
commit
.
id
)
}
project
.
instance_variable_set
(
:@latest_successful_pipeline_for_default_branch
,
pipeline_without_vulnerability
)
it
{
is_expected
.
to
eq
(
false
)
}
end
end
end
let_it_be
(
:pipeline_without_vulnerability
)
{
create
(
:ci_pipeline
,
:success
,
project:
project
,
sha:
project
.
commit
.
id
)
}
context
'Vulnerability::Finding is not present on the latest pipeline without security job'
do
let!
(
:pipeline_without_security_job
)
{
create
(
:ee_ci_pipeline
,
:success
,
project:
project
,
sha:
project
.
commit
.
id
)
}
it
{
is_expected
.
to
eq
(
false
)
}
end
context
'Vulnerability::Finding is not present on the pipeline for default branch'
do
let!
(
:pipeline_without_vulnerability
)
{
create
(
:ee_ci_pipeline
,
:success
,
:with_sast_report
,
project:
project
,
sha:
project
.
commit
.
id
)
}
it
{
is_expected
.
to
eq
(
true
)
}
it
{
is_expected
.
to
eq
(
true
)
}
end
end
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment