The following page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features or functionality remain at the sole discretion of GitLab Inc.
| Stage | Verify |
| Maturity | Minimal |
| Content Last Reviewed | 2025-05-19 |
Thanks for visiting this category direction page on Job Artifacts in GitLab. This page belongs to the Verify Stage and is maintained by Rutvik Shah (E-Mail).
This category covers the experiences related to the artifacts generated by a CI/CD pipeline or a job.
For specific information and features related to display of artifact data, check out the GitLab Features and for information about administration of artifacts please reference the Job Artifact documentation. You may also be looking for one of the related direction pages from the Verify Stage.
This direction page is a work in progress, and everyone can contribute:
Job Artifacts are created as an output of a pipeline or job. This includes both the job’s artifacts, job logs and pipeline artifacts. Artifacts can be used for reports that are displayed directly in GitLab or can be published to GitLab Pages or in some other way for users to review. Artifacts can provide a wealth of information to development teams and the users they support.
For information about storing containers or packages or information about release evidence see the Package Stage direction page.
We aim to help users optimize their storage usage from Job Artifacts and build a cohesive pipeline experience with the following capabilities:
Improved Artifact Management Experience with API enhancements and UX capabilities.
Create a more cohesive pipeline integration experience for complex pipelines such as Seamless artifact handling for child/parent pipelines.
For FY26 (ending January 2026):
We will be improve and maintain our Job Artifacts functionality with a focused approach:
Bug Resolution: We are prioritizing the resolution of critical S1 and S2 issues that have exceeded their service level objectives. By addressing these high-impact problems first, we aim to improve reliability and ensure our users experience consistent performance.
Feature Development: Our primary focus involves streamlining artifact handling for parent/child pipelines. This enhancement will enable more sophisticated pipeline architectures, giving teams greater flexibility in designing complex project workflows and improving overall system efficiency.
Community Collaboration: We actively welcome and support community contributions that enhance Job Artifacts functionality.
The team will finalize planning and begin implementing the MVC for streamline artifact handling for parent/child pipelines.
We are currently working on a POC to allow jobs in an upstream pipeline to reference artifacts from a downstream pipelines
Although we do not plan on adding new features this year, we welcome and support community contributions that align with our category vision. You can find our list of issues ready for contribution here. If you have an issue that is not on this list, but you feel passionate about it and want to contribute, please tag @rutshah in the issue and we will work with you to determine a path forward and connect you with our community contribution team to ensure your success.
The most popular customer request is for the ability to support the generation of multiple artifacts per job to reduce the need for pipeline logic to make select files available to later jobs.
The Gitlab quality team has requested the ability to upload artifacts from a job when it fails due to a timeout to assist in debugging pipeline failures.