- Feb 17, 2025
-
-
Marcel Amirault authored
-
- Feb 07, 2025
-
-
Lysanne Pinto authored
Adds redirects and updates links from UI too Changelog: changed
-
- Feb 06, 2025
-
-
Marcel Amirault authored
H1 headers needs to be in YAML frontmatter now
-
- Jan 25, 2025
-
-
Vasiliy Krasikov authored
-
- Jan 13, 2025
-
-
Marcel Amirault authored
Update offering notes with all three offerings
-
- Sep 24, 2024
-
-
Lysanne Pinto authored
Also updates the add coverage check topic
-
- Aug 30, 2024
-
-
Panos Kanellidis authored
-
- Aug 16, 2024
-
-
Panos Kanellidis authored
Also make the jacoco_coverage_reports feature flag beta type
-
- Jul 29, 2024
-
-
Lysanne Pinto authored
-
- Jul 11, 2024
-
-
Lysanne Pinto authored
-
- Apr 12, 2024
-
-
Segolene Bouly authored
-
- Apr 03, 2024
-
-
drew authored
-
- Mar 07, 2024
-
-
Amy Qualls authored
Repoint these links to their current locations.
-
- Feb 27, 2024
-
-
Suzanne Selhorn authored
Related to: #439130
-
- Jan 25, 2024
-
-
Marcel Amirault authored
Makes use of markdownlint for automated cleanup
-
- Jan 24, 2024
-
-
Suzanne Selhorn authored
Because for now, we're changing the format. Related to: gitlab-docs#1751
-
- Jan 08, 2024
-
-
Marcel Amirault authored
Try to use standard language for linking to the yaml reference, but also fix links to the correct locations
-
- Dec 06, 2023
-
-
Marcel Amirault authored
Update the links in all docs except user and admin pages
-
- Sep 29, 2023
-
-
Phil authored
The project was updated and consists of a much smaller image now which also should yield faster job execution times. See https://gitlab.com/haynes/jacoco2cobertura/-/releases/1.0.9
-
- Aug 15, 2023
-
-
Because we changed the way we do the markdown. Related to: gitlab-org/gitlab-docs#1690
-
- Aug 14, 2023
-
-
Kati Paizee authored
-
- Aug 08, 2023
-
-
- Aug 02, 2023
-
-
- Jun 07, 2023
-
-
- Jun 06, 2023
-
-
Ashraf Khamis authored
-
- May 31, 2023
-
-
Marcel Amirault authored
Pipeline artifacts are not a thing that users interact with, they are internal components of test coverage visualization and do not need to be documented. We can keep some details about the data storage though.
-
- Apr 28, 2023
-
-
In the previous example, if the second line failed and returned a nonzero exit code, it would exit the job before executing the fourth line that generates the coverage.xml required for test coverage visualization. This is painful, given that users probably want to visualize line-by-line coverage when the tests fail even more than when it passes. Switch to a one-line call that runs the tests _and_ produces a coverage report. This enables test coverage visualization regardless of if the job passes or fails, even if other future jobs are skipped by this job's failure.
-
- Apr 12, 2023
-
-
- Mar 23, 2023
-
-
- Mar 15, 2023
-
-
Evan Read authored
The programming language's official name is Go.
-
- Feb 24, 2023
-
-
Pipeline Insights becomes Pipeline Security, and many categories shifted around.
-
- Jan 23, 2023
-
-
-
Arnav Goel authored
-
- Nov 04, 2022
-
-
Suzanne Selhorn authored
Because we want to be brief. https://docs.gitlab.com/ee/development/documentation/styleguide/word_list.html#please
-
- Sep 21, 2022
-
-
Related epic: https://gitlab.com/groups/gitlab-com/-/epics/1940
-
- Jul 08, 2022
-
-
Albert authored
If a job in a child pipeline creates a coverage report, the report is included in the parent pipeline's coverage report. Changelog: added
-
- Jun 22, 2022
-
-
Marcel Amirault authored
Moves fail fast testing, load performance testing, test coverage visualization and metrics reports to ci/testing directory
-
- Jun 13, 2022
-
-
- #latest_report_builds_in_self_and_descendants - #has_report_builds_in_self_and_descendants?
-
- Jun 03, 2022
-
-
- May 26, 2022
-
-