# CI/CD Pipeline An automated DevOps process for building, testing, and deploying software through continuous integration and continuous delivery. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Publishing Playwright HTML reports on GitLab Pages DevFeed: [Publishing Playwright HTML reports on GitLab Pages]() Original publisher: [Read original article]() Author: T.J. Maher (noreply@blogger.com) Published: 2026-08-29T23:56:10Z Content type: tutorial Language: en Sources: [T.J. Maher]() Topics: [GitLab](), [Playwright](), [CI/CD](), [CI/CD Pipeline](), [Publishing]() Tags: [bun-create-playwright](), [ci-cd](), [ci-cd-pipeline](), [github-pages](), [gitlab](), [gitlab-ci](), [playwright]() ### AI overview This tutorial explains how to add a deploy stage to a GitLab CI/CD pipeline for a Bun-based Playwright project. The stage publishes generated Playwright HTML reports, including screenshots and videos, to GitLab Pages so they can be viewed online. ### Source excerpt We've added a lot to our demo project, bun--create-playwright. We've explored setting up a Playwright framework using bun, a new package manager bundled into Claude Code. We've added typechecking, and formatting and linting. We've set up a CI/ CD pipeline for our tests using GitLab, one with three stages: Quality: We check that the formatting, linting and typechecking is correct for any changes we attempt to push to the code base. Test: We run the smoke and then the regression tests to make sure that everything still works. Report: We bundle an archive of the Playwright generated HTML report, with screenshots and videos if things fail. For this post, we will add a new stage to this GitLab pipeline: Deploy: Where we will deploy the HTML report to GitLab Pages, so we can view it online. What is GitLab Pages? GitLab Pages is a built-in feature of GitLab that allows you to publish static websites directly from a repository in GitLab. Similar to GitHub Pages, it is commonly used to host project documentation, personal blogs, portfolios, or corporate landing pages for free. From the GitLab Docs / Pages: "To use GitLab Pages, you must create a project in GitLab to upload your website's files to. These projects can be either public, internal, or private. "By default, GitLab deploys your website from a specific folder called public in your repository. You can also set a custom folder to be deployed with Pages. When you create a new project in GitLab, a repository becomes available automatically. "To deploy your site, GitLab uses its built-in tool called GitLab CI/CD to build your site and publish it to the GitLab Pages server. The sequence of scripts that GitLab CI/CD runs to accomplish this task is created from a file named .gitlab-ci.yml, which you can create and modify. A user-defined job with pages: true property in the configuration file makes GitLab aware that you're deploying a GitLab Pages website. "You can either use the GitLab default domain for GitLab Pages websit ## Examining the artifacts job of a Playwright GitLab CI / CD pipeline DevFeed: [Examining the artifacts job of a Playwright GitLab CI / CD pipeline]() Original publisher: [Read original article]() Author: T.J. Maher (noreply@blogger.com) Published: 2026-08-29T23:19:22Z Content type: tutorial Language: en Sources: [T.J. Maher]() Topics: [Playwright](), [GitLab](), [CI/CD Pipeline](), [CI/CD](), [test]() Tags: [bun-create-playwright](), [ci-cd](), [ci-cd-pipeline](), [gitlab](), [playwright](), [screenshots](), [test](), [trace](), [videos]() ### AI overview This tutorial examines how a Playwright GitLab CI/CD pipeline stores and exposes test artifacts. It explains the playwright-report, test-results, and reports/junit folders and describes generated HTML and JUnit reports, screenshots, videos, and trace reports. ### Source excerpt You may have noticed that in the GitLab CI / CD Pipeline for our Playwright project, in the .gitlab-ci.yml file, after our scripts has run, in the Test stage, there is a subsection called "artifacts" with certain paths to something called "playwright-report", "test-results", and "reports". The Playwright -> Artifacts -> Reports stage playwright: extends: .bun_playwright stage: test timeout: 30 minutes ... ... artifacts: when: always paths: - playwright-report/ - test-results/ - reports/ reports: junit: reports/junit/results.xml expire_in: 30 days https://gitlab.com/tjmaher/bun-create-playwright/-/blob/main/.gitlab-ci.yml Every time Playwright tests run, it generates proof of the test execution: screenshots capturing the state of the UI when a test failed, video recordings of an entire browser session, HTML and JUnit XML test reports, trace reports showing action logs, network requests. These artifacts, when the tests run locally, are placed by the Playwright Test runner in generated folders, playwright-report and test-results, along with a folder called reports/junit. With this post, we will be examining how this artifacts stage of the GitLab CI/ CD pipeline produces downloadable artifacts we can examine. Playwright-Report: A Playwright Test folderThe Playwright Test runner creates a folder called "playwright-report", if it doesn't already exist, and an HTML file called index.html documenting the completed test run. From Playwright.dev / Test Reporters: "Playwright Test comes with a few built-in reporters for different needs and ability to provide custom reporters. [...] All built-in reporters show detailed information about failures, and mostly differ in verbosity for successful runs. [...] HTML reporter produces a self-contained folder that contains report for the test run that can be served as a web page". The HTML Report is the one that automatically opens after you run your tests locally, or if you are using the node package manager: npx playwright show-report ## Setting up a CI/ CD pipeline with GitLab: Quality, Test and Report DevFeed: [Setting up a CI/ CD pipeline with GitLab: Quality, Test and Report]() Original publisher: [Read original article]() Author: T.J. Maher (noreply@blogger.com) Published: 2026-08-25T02:28:52Z Content type: tutorial Language: en Sources: [T.J. Maher]() Topics: [CI/CD Pipeline](), [GitLab](), [Testing](), [Playwright](), [pull-requests](), [TypeScript]() Tags: [bun-create-playwright](), [ci-cd](), [ci-cd-pipeline](), [code-reviews](), [gitlab](), [playwright](), [test](), [testing](), [typescript](), [workflows]() ### AI overview A tutorial on setting up a three-stage GitLab CI/CD pipeline for merge requests. The pipeline runs code-quality checks, smoke and regression tests, and produces a downloadable report, with stages executed sequentially and jobs within each stage running in parallel. ### Source excerpt So far, we have reviewed how to review code with ES Lint + Prettier and Typecheck, how to set up and run smoke tests, how to run all Playwright + TypeScript tests, and reviewed the HTML report of results. In this post, we are going to set up a three stage GitLab CI/ CD pipeline that will run against every merge request: Quality (lint, typecheck, prettier) --> Test ( smoke + regression ) --> Report ( Downloadable ) I haven't used GitLab since when I worked at ThreatStack back in 2020. ( See my blog entry Getting to Know GitLab and How They Test the UI ) GitLab reads .gitlab-ci.yml from the repository root and turns it into a pipeline, a set of jobs, grouped into stages, running whenever you push a change to a repository. Stages run one after another, and jobs within a stage run in parallel. If one stage fails, the stages after it are skipped. This begs the question: What is GitLab? What is CI/ CD? Or a pipeline? Or a merge request? What is GitLab? GitLab began in 2011 as a side project by Ukrainian programmer Dmytro Zaporozhets, built to help developers work together on code more easily. Over time, it grew into a large open-source DevOps platform. More than just storing code, it handles code reviews, CI/CD (continuous integration and continuous delivery), and package registries. A company called GitLab Inc. was eventually created to turn the project into a commercial product. What makes GitLab different from tools that only host Git repositories (like a basic Git server) is that it bundles the entire software delivery process into one application. This includes: Merge requests - GitLab's term for proposing and reviewing code changes before they're merged into the main codebase (similar to a "pull request" in GitHub) Issue tracking - a built-in system for logging bugs, tasks, and feature requests Pipelines - automated workflows that build, test, and deploy code whenever changes are pushed So instead of stitching together separate tools for version control, testing, an ## How to Build an A/B Testing Framework for Modern CI/CD Pipelines DevFeed: [How to Build an A/B Testing Framework for Modern CI/CD Pipelines]() Original publisher: [Read original article]() Author: Aaron Newcomb Published: 2026-08-10T00:00:00Z Content type: tutorial Language: en Sources: [Harness Blog]() Topics: [A/B Testing](), [CI/CD](), [CI/CD Pipeline](), [feature flags](), [progressive delivery](), [Monitoring]() Tags: [a-b-testing](), [ci-cd](), [feature-flags](), [how-to](), [monitoring](), [progressive-delivery](), [rollback](), [verification]() ### AI overview This tutorial explains how to integrate A/B testing into CI/CD pipelines using feature flags, progressive delivery, real-time metrics, automated verification, and rollback controls. It argues that deployment should be decoupled from release so teams can validate changes before full rollout. ### Source excerpt Learn how to build an A/B testing framework in your CI/CD pipeline. Accelerate software delivery, reduce risk, and boost innovation. Start now! | Blog ## Monitoring Android Vitals with the Play Developer Reporting API DevFeed: [Monitoring Android Vitals with the Play Developer Reporting API]() Original publisher: [Read original article]() Author: Julien Salvi Published: 2026-03-19T12:41:51Z Content type: tutorial Language: en Sources: [Stories by Julien Salvi on Medium]() Topics: [Android](), [API](), [Google Play](), [Gradle](), [CI/CD Pipeline](), [Google Cloud Platform (GCP)](), [Slack]() Tags: [aircall](), [android](), [android-app-development](), [anr](), [api](), [ci-cd-pipeline](), [crash](), [google-play-developer](), [gradle](), [reporting](), [slack]() ### AI overview This tutorial explains how Aircall uses the Google Play Developer Reporting API in a Gradle task to retrieve Android Vitals, including ANR and crash metrics, and deliver daily health reporting to Slack. It covers metric-set queries, timeline aggregations, service-account authentication, data modeling, and health thresholds. ### Source excerpt At Aircall, we built an automated reporting tool that fetches our Android Vitals metrics thanks to the Play Developer Reporting API and delivers a daily health dashboard straight to Slack. All of this powered by a simple Gradle task. Discovering the API The Google Play Developer Reporting API gives programmatic access to the same quality metrics you see in the Google Play Console. It covers the core Android Vitals: ANR rate, crash rate, slow start rate, and stuck background wakelocks, the signals Google uses to determine whether your app meets the bad behavior thresholds. The API is organized around metric sets that you query with a timeline specification. Each metric set returns daily, 7-day, and 28-day user-weighted aggregates, giving you the full picture from short-term regressions to long-term trends. The key advantage over scraping the Console UI is that you can automate the entire flow and integrate it into your existing CI/CD pipeline. You will find the complete API reference in the official documentation. Build with Play VitalsSetting up the dependency We chose to implement this as a Gradle task inside our build-logic module. This keeps the reporting logic close to the project without polluting the app code. First, let's add the dependency: # libs.versions.toml googleApiReporting = "v1beta1-rev20230803-2.0.0" buildLogic-plugin-google-play-developer-reporting = { module = "com.google.apis:google-api-services-playdeveloperreporting", version.ref = "googleApiReporting" } Which can then be added to the build.gradle.kts of your build-logic module: dependencies { // API to get Google Play store vitals metrics implementation(libs.buildLogic.plugin.google.play.developer.reporting) }Authenticating with a Service Account To access the API, you need a Google Cloud Service Account with the Play Developer Reporting scope. We pass the credentials as an environment variable to keep secrets out of the repository. The Reporting client initializes the API with these credentia ## Pipeline Performance Profiling: Making CI/CD Performance, Cost, and Bottlenecks Visible DevFeed: [Pipeline Performance Profiling: Making CI/CD Performance, Cost, and Bottlenecks Visible]() Original publisher: [Read original article]() Author: Gil Chaouat Published: 2026-01-26T15:56:34Z Content type: article Language: en Sources: [Codefresh]() Topics: [CI/CD Pipeline](), [CI/CD](), [Automation]() Tags: [ci-cd](), [continuous-delivery](), [cost](), [devops](), [performance](), [pipeline](), [product-and-tools]() ### AI overview The article explains how CI/CD pipeline performance profiling can make pipeline behavior, speed, efficiency, cost, and bottlenecks observable and measurable. It also describes how CI/CD automation reduces deployment time and manual errors while providing faster feedback. ### Source excerpt Modern CI/CD pipelines are no longer just about whether builds succeed, they're about how fast, how efficiently, and at what cost they run. Pipeline Performance Profiling is designed to close this gap by making pipeline behavior observable, measurable, and explainable. The post Pipeline Performance Profiling: Making CI/CD Performance, Cost, and Bottlenecks Visible appeared first on Codefresh. ## Setting Up a CI/CD Pipeline for Power BI Report Source Control DevFeed: [Setting Up a CI/CD Pipeline for Power BI Report Source Control]() Original publisher: [Read original article]() Published: 2022-11-07T00:00:00Z Content type: tutorial Language: en Sources: [Mutt0-ds Notes]() Topics: [Azure DevOps](), [CI/CD Pipeline](), [DevOps](), [REST API](), [Git](), [active directory](), [JSON](), [API](), [dataset](), [Authentication]() Tags: [authentication](), [ci-cd-pipeline](), [dataset](), [devops](), [directory](), [environment-variables](), [git](), [json](), [repository](), [rest-api]() ### AI overview This article describes setting up a CI/CD pipeline through Azure DevOps to provide rudimentary version control for Power BI reports. Because .pbix files are binary, the pipeline uploads a report to a Power BI Premium workspace, uses the Power BI REST API and Tabular Editor 2 to extract metadata, and pushes the resulting textual representation back to a Git repository. ### Source excerpt One of the most annoying issues I have when working with Power BI files is that source control is a real pain. Considering that Microsoft... ## Focus Week Case Study: Bringing E2E Tests into the CI Pipeline DevFeed: [Focus Week Case Study: Bringing E2E Tests into the CI Pipeline]() Original publisher: [Read original article]() Author: tobi@techunicorn.builders (Tobias Mende) Published: 2021-12-25T12:34:00Z Content type: article Language: en Sources: [Tobias Mende]() Topics: [CI/CD Pipeline](), [Selenium](), [test](), [AWS Lambda]() Tags: [aws-lambda](), [case-study](), [case-study-collaboration-culture-ensemble-programming-team-programming-developer-productivity](), [ci-cd](), [e2e](), [selenium](), [tests]() ### AI overview This case study describes BRYTER's effort to bring Selenium-based end-to-end tests into its CI/CD pipeline. The tests were previously maintained by QA in a separate repository and run manually, with problems including slowness and flakiness. The team identified stabilization, parallel execution using AWS Lambda, closer alignment with production code, and CI/CD integration as key areas of work. ### Source excerpt Focus Week Case Study: Bringing E2E Tests into the CI Pipeline In my last article, I wrote about focus weeks and how my team is currently doing them at BRYTER. Today, I want to share a case study of our latest focus week. ## Fixing APK Analyzer terminal errors by selecting a compatible Java version DevFeed: [Fixing APK Analyzer terminal errors by selecting a compatible Java version]() Original publisher: [Read original article]() Author: dustin@dustn.dev (Dustin Summers) Published: 2021-12-12T10:26:38Z Content type: tutorial Language: en Sources: [Dustin Summers]() Topics: [APK](), [Java](), [CI/CD Pipeline](), [Android Studio](), [Command-line interface](), [Google]() Tags: [android-studio](), [android-xmlschema-error-apkanalyzer-troubleshooting](), [apk](), [ci-cd](), [command-line](), [error](), [java](), [jdk]() ### AI overview This tutorial addresses an APK Analyzer error encountered when running the tool from a terminal, including in a CI/CD workflow. It explains that Android Studio's bundled JDK may be incompatible and describes selecting another installed Java version, with guidance for making the change permanent. ### Source excerpt Recently, I was tasked with using Google provided tools to decompile an APK in a CI/CD pipeline. This is great, because Google provides a tool called APK Analyzer, and provide tools both within the IDE itself and options to run it via the Command Line. I can talk more about the actual task later. For now, I want to discuss the issue that I first ran into when attempting to run apkanalyzer from the terminal.