Repository navigation
feat: GitLab Ultimate page with vulnerability report screenshots and policy examples (#24) - #44
Merged
Merged
Conversation
…policy examples (#24) Signed-off-by: Nicolai Ehrhardt <245527909+predictor2718@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #24.
What changed
A new page,
/gitlab-ultimate/("GitLab Ultimate: vulnerability report and policies"). The reports page links to it from the GitLab SAST section. It is in the sitemap, but not in the header nav.SAST report: four screenshots from the test project
glsec-io/ultimate-lab:Below them is the line-shift limitation: GitLab matches findings by file and line, so a shifted line shows as fixed and new at once. A
trackingsignature didn't change that in the test.Pipeline execution policy: both files (
policy.ymlandglsec-policy.ymlwithrules: - when: always,no_repo_config,no_ignores), plus what happened in the test:.pipeline-policy-preskips the project's jobs when the policy job fails..glsec.ymlor# glsec:ignorein a merge request has no effect.vof the tag.The component reference and the glsec version are filled in from the build, the same way as in the reports page's publishing jobs, so the example follows each release. The text matches the component README, which the page links.
Scan execution policy and GL082:
SAST_DISABLEDdoesn't switch off a policy-enforced SAST job (tested on 2026-10-27), with a link to/rules/GL082/#scan-execution-policies.Screenshots
--format gitlab-sast. The only visible difference is that 1.25.0 also lists the CWE as an identifier. The first caption says so.Wording on GitLab
Checks
go test ./..., including the SEO test./reports/swings the same way; the page has no script./gitlab-ultimate/added to.github/site-checks/pages.txt.How to test