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.
Artifacts are files created as part of a build process that often contain metadata about that build's jobs like test results, security scans, etc. These 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. These artifacts can provide a wealth of knowledge to development teams and the users they support.
Job Artifacts and Pipeline Artifacts are both included in the scope of Build Artifacts to empower GitLab CI users to more effectively manage testing capabilities across their software lifecycle in both the gitlab-ci.yml or as the latest output of a job.
For information about storing containers or packages or information about release evidence see the Package Stage direction page.
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.
Interested in joining the conversation for this category? Please join us in the issues where we discuss this topic and can answer any questions you may have. Your contributions are more than welcome.
This page is maintained by the Product Manager for Pipeline Insights, Jocelyn Eillis (E-mail).
In 15.8 we continue to focus on resolving storage calculations errors for Build Artifacts as we prioritize storage consumption gitlab&5754. In parallel, we are focusing on usability enhancements for Build Artifact management gitlab&8715, starting with the UI capabilities gitlab&8311. We started working on the Artifacts page MVC gitlab#33418 in 15.6, which we are targeting to release in 15.9.
There are no planned features in Build Artifacts in FY24, however, Pipeline Insights will support high priority bug fixes for this category during this time.
The Gitlab Sales teams are looking for more complex ways for customers to make use of Ultimate and Premium features like SAST and DAST with monorepos by letting customers namespace parts of reports to more granular analysis or combining Matrix Builds and Metrics Reports.
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.
One of our most complicated request, is to handle the expire_at experience in self-managed customers better. Today, our implementation deletes data for both GitLab.com and self-managed users - rather than allowing more control for our self-managed customers.
Although we have made improvements to expiration of artifacts, we continue to see customer struggles with reliability for removal of these expired artfacts and ensuring cleanup methods are removing all items.
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 those pipeline failures.
The team is also investigating performance issues related to the build artifact feature set as part of our focus on Availability and Performance.
To meet our long term vision that enables users to more easily use and manage their Build Artifacts we will need to add and improve the usability of artifact in the UI. In addition to UI improvements, we need to provide user-friendly solutions for build artifacts management via API, for example, an API to upload artifacts directly to GitLab without them being generated by a pipeline.