# gitlab-ci Published articles for gitlab-ci. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Announcing GitLab support for Appwrite Sites and Functions DevFeed: [Announcing GitLab support for Appwrite Sites and Functions]() Original publisher: [Read original article]() Author: Matej Bačo Published: 2026-09-03T00:00:00Z Content type: release Language: en Sources: [Appwrite Blog]() Topics: [Appwrite](), [GitLab](), [Deployment]() Tags: [announcements](), [cli](), [code](), [collaboration](), [deployment](), [git](), [gitlab](), [gitlab-ci](), [qr-code]() ### AI overview Appwrite announces GitLab support for Sites and Functions, allowing users to connect GitLab repositories and deploy directly, including repositories in GitLab groups. ### Source excerpt Connect a GitLab account to Appwrite and deploy Sites and Functions directly from your GitLab repositories, including projects that live inside GitLab groups. ## 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 ## How Developers Can Test Their Feature Branch Against Various Playwright Configurations Before Creating a Merge Request in GitLab CI/CD DevFeed: [How Developers Can Test Their Feature Branch Against Various Playwright Configurations Before Creating a Merge Request in GitLab CI/CD]() Original publisher: [Read original article]() Author: T.J. Maher (noreply@blogger.com) Published: 2026-08-28T20:18:08Z Content type: tutorial Language: en Sources: [T.J. Maher]() Topics: [GitLab](), [CI/CD](), [Playwright](), [YAML](), [Development]() Tags: [bun-create-playwright](), [chromium](), [ci-cd](), [firefox](), [gitlab](), [gitlab-ci](), [playwright](), [tests](), [yaml]() ### AI overview This tutorial shows how to configure a GitLab CI/CD pipeline so developers can test a feature branch before creating a merge request. It uses spec inputs in a YAML configuration to let users choose the branch, Playwright test suite, and browser, including Chromium, Firefox, WebKit, or all browsers. ### Source excerpt Developers need the option to test out their feature branch before merging it into main. In the last section, we set up a GitLab CI/CD Pipeline in our bun-create-playwright project to check every GitLab Merge Request. Now, we will be giving developers option to create a new pipeline where they can choose: Which feature branch to test against. Which test suite to execute (LoginPage tests? Secure Area? Or all of them?) Which Playwright browser to use: Chromium, Firefox, WebKit, or all. All these features can be set up using our .gitlab-ci.yaml file! Go to to bun-create-playwright, view the Pipelines section, and select the New Pipeline button. Run a New Bun-Create-Playwright Pipeline If you go to the Run new pipeline page at https://gitlab.com/tjmaher/bun-create-playwright/-/pipelines/new you can see the following default values I've set: https://gitlab.com/tjmaher/bun-create-playwright/-/pipelines/new By default: Branch name is "main", TEST_SUITE is "all", BROWSER is "all". ... But all these values can be set, with the developer choosing the options laid out in the .gitlab-ci.yaml file. Collect User Data With Spec Inputs We are going to be adding to the GitLab Pipeline we built in our last post Setting up a CI/ CD pipeline with GitLab: Quality, Test and Report. First, we are going to add a "spec" section to the header of the YAML file to define the behavior of a pipeline, and within that spec header, we will ask the person who triggered a new pipeline to set user defined inputs for the pipeline. spec: inputs: browser: description: "Browser project to run against." default: "all" options: ["all", "chromium", "firefox", "webkit"] suite: description: "Select full regression suite, or a single spec" default: "all" options: ["all", "login.spec.ts", "secure-area.spec.ts"] This is where we declare the "browser" and "suite" variables that appear when a user creates a new pipeline. We've given them a choice to run their feature branch code against: Browser: All, Chromium, Fir ## Best GitLab Alternatives in 2026 DevFeed: [Best GitLab Alternatives in 2026]() Original publisher: [Read original article]() Author: Pete Miloravac Published: 2026-07-30T12:04:04Z Content type: comparison Language: en Sources: [Semaphore Engineering]() Topics: [GitLab](), [CI/CD](), [DevSecOps](), [GitHub Actions]() Tags: [2026](), [alternatives](), [ci-cd](), [circleci](), [compare](), [cost](), [devsecops](), [enterprise-deployment](), [evaluation](), [github](), [github-actions](), [gitlab](), [gitlab-ci](), [self-hosted]() ### AI overview A comparison of Semaphore, GitHub Actions, CircleCI, and Buildkite as alternatives to GitLab for CI/CD-focused decisions. It examines execution, deployment, pricing, support, and operating models while explaining when retaining GitLab repositories may be more practical than replacing GitLab entirely. ### Source excerpt GitLab is a capable, integrated DevSecOps platform--but it is not the only sensible way to run CI/CD. Teams comparing GitLab alternatives are often trying to improve pipeline execution, simplify operations, get clearer support and cost options, or adopt a CI/CD tool that fits their existing source-control strategy. That does not automatically mean moving repositories out [...] The post Best GitLab Alternatives in 2026 appeared first on Semaphore. ## Best Bitbucket Alternatives in 2026 DevFeed: [Best Bitbucket Alternatives in 2026]() Original publisher: [Read original article]() Author: Pete Miloravac Published: 2026-07-29T11:54:28Z Content type: comparison Language: en Sources: [Semaphore Engineering]() Topics: [bitbucket](), [CI/CD](), [GitHub Actions](), [GitLab](), [Self-hosted](), [Cloud](), [Deployment](), [DevSecOps]() Tags: [2026](), [alternatives](), [bitbucket](), [ci-cd](), [circleci](), [cloud](), [compare](), [github](), [github-actions](), [gitlab](), [gitlab-ci](), [linux](), [macos](), [pipelines](), [self-hosted]() ### AI overview This comparison guide examines Bitbucket Pipelines and four alternatives--Semaphore, GitHub Actions, GitLab CI/CD, and CircleCI--to help teams choose a CI/CD platform based on source-control ecosystem, visibility, deployment control, hosting model, and operational requirements. ### Source excerpt Bitbucket Pipelines is a logical starting point for teams already using Bitbucket Cloud. It is built into the source-control experience, configured in a bitbucket-pipelines.yml file, and offers both Atlassian-hosted execution and self-hosted runners. But convenience at the repository level is not always the same thing as the best long-term CI/CD operating model. Teams evaluating Bitbucket [...] The post Best Bitbucket Alternatives in 2026 appeared first on Semaphore. ## Nix flake check + JUnit = Junix DevFeed: [Nix flake check + JUnit = Junix]() Original publisher: [Read original article]() Author: Yajo Published: 2026-07-23T12:35:46Z Content type: release Language: en Sources: [Announcements - NixOS Discourse]() Topics: [Nix](), [ci](), [GitHub](), [GitHub Actions](), [GitLab](), [Jenkins]() Tags: [announcements](), [build](), [ci](), [github](), [github-actions](), [gitlab-ci](), [jenkins]() ### AI overview Junix converts Nix JSON output into standard JUnit XML reports, allowing Nix builds and checks to integrate with JUnit-compatible CI systems such as GitLab CI, Jenkins, and GitHub Actions. It can evaluate system checks, repeat failed evaluations for full tracebacks, build local checks, include logs, and print a human-readable summary. ### Source excerpt Hi all! I'd like to share Junix, a small tool that converts Nix @nix JSON output into standard JUnit XML so you can integrate Nix builds with any JUnit-compatible CI (GitLab CI, Jenkins, GitHub Actions, etc.). Try it: cd your/flake nix run gitlab:moduon/junix check -o result.xml This will: Eval all systems checks in one shot If any eval fails, repeat that check's eval to get full traceback Build local system checks Write the JUnit XML report in result.xml with check build logs and eval failure logs, if any Print a colorful human-readable summary 9 posts - 6 participants Read full topic ## How Indeed Replaced Its CI Platform with Gitlab CI DevFeed: [How Indeed Replaced Its CI Platform with Gitlab CI]() Original publisher: [Read original article]() Author: Carl Myers Published: 2024-08-06T15:03:51Z Content type: article Language: en Sources: [Indeed]() Topics: [GitLab](), [CI/CD](), [Jenkins](), [Kubernetes](), [Amazon EC2](), [Amazon Web Services]() Tags: [aws](), [ci](), [ec2](), [gitlab](), [gitlab-ci](), [jenkins](), [kubernetes](), [unsorted]() ### AI overview Indeed's engineering platform evolved from Hudson to Jenkins and later encountered architectural and scaling limitations as the company grew and adopted AWS EC2 and Kubernetes. The article discusses replacing that CI platform with GitLab CI. ### Source excerpt Here at Indeed, our mission is to help people get jobs. Indeed is the #1 job site in the world with over 580M+ Job Seeker Profiles. For Indeed's Engineering Platform teams, we have a slightly different motto: "We help people to help people get jobs". As part of a data-driven engineering culture that has spent [...] ## Connect to Open VPN during Gitlab Pipeline DevFeed: [Connect to Open VPN during Gitlab Pipeline]() Original publisher: [Read original article]() Author: Marco Gomiero Published: 2021-06-28T00:00:00Z Content type: tutorial Language: en Sources: [Posts on Marco Gomiero]() Topics: [GitLab](), [CI/CD](), [Virtual Private Network](), [Kotlin]() Tags: [ci-cd](), [configuration](), [dependencies](), [gitlab](), [gitlab-ci](), [kotlin](), [secrets](), [server](), [vpn]() ### AI overview This tutorial explains how to connect to an OpenVPN service from a GitLab CI/CD pipeline. It describes configuring secret variables, installing dependencies, establishing the VPN connection, checking connectivity, and allowing the pipeline to download dependencies from a private Maven repository behind the VPN. ### Source excerpt Gitlab CI/CD offers the possibility to create a pipeline, which runs when something changes in the repository. A pipeline consists of one or more stages that run in order and in these stages, for example, it is possible to build the project, run the tests, create the artifacts, etc. For more information about Gitlab CI/CD, I suggest you look over the documentation. These out-of-the-box solutions really simplify the work to be done to have a CI up and running. For example, this is the configuration file (a file called .gitlab-ci.yml placed at the repository's root) needed for running all the tests of a Kotlin project. ## Теперь YouTrack интегрируется с GitLab CI/CD DevFeed: [Теперь YouTrack интегрируется с GitLab CI/CD]() Original publisher: [Read original article]() Author: ana-bartasheva (JetBrains) Published: 2021-05-28T10:41:33Z Content type: release Language: ru Sources: [JetBrains RU]() Topics: [CI/CD](), [GitLab](), [teamcity](), [Jenkins]() Tags: [ci](), [ci-cd](), [develop](), [gitlab](), [gitlab-ci](), [merge](), [project-management](), [youtrack](), [youtube]() ### AI overview JetBrains YouTrack's release adds GitLab CI/CD integration, allowing tasks to be updated automatically based on GitLab pipeline results. The release also introduces similar-task detection in YouTrack Lite and a text editor improvement in YouTrack Classic. ### Source excerpt Привет, Хабр! На связи команда JetBrains YouTrack, и у нас для вас новый релиз! Мы дополнили интеграцию с GitLab -- теперь YouTrack не только отслеживает коммиты и merge-реквесты, но и поддерживает интеграцию с GitLab CI/CD. А это значит, что задачи в YouTrack смогут обновляться автоматически -- по результатам автоматизированных сборок в GitLab CI/CD. Также мы дополнили релиз интересными улучшениями для работы с задачами. За подробностями добро пожаловать под кат! Читать далее ## Starting a TypeScript Project in 2021 DevFeed: [Starting a TypeScript Project in 2021]() Original publisher: [Read original article]() Author: Chris Hager Published: 2021-03-24T00:00:00Z Content type: tutorial Language: en Sources: [Chris Hager]() Topics: [TypeScript](), [Node.js](), [Jest](), [CI/CD](), [npm](), [Compiler](), [JavaScript]() Tags: [boilerplate](), [browser](), [deprecated](), [es6](), [esbuild](), [eslint](), [github](), [gitlab-ci](), [javascript](), [jest](), [node-js](), [npm](), [project](), [setup](), [template](), [typescript]() ### AI overview A practical guide to starting a TypeScript project with modern tooling, covering project setup, linting, Jest testing, esbuild bundling, npm publishing, continuous integration, and automatic API documentation. ### Source excerpt Moved to /2021/04/starting-a-typescript-project-in-2021/ ## Tutorial: Self-hosted CI/CD deployment in a homelab with GitLab CI, Docker, and Kubernetes DevFeed: [Tutorial: Self-hosted CI/CD deployment in a homelab with GitLab CI, Docker, and Kubernetes]() Original publisher: [Read original article]() Author: Techno Tim Published: 2020-09-12T14:00:00Z Content type: tutorial Language: en Sources: [Techno Tim]() Topics: [CI/CD](), [GitLab](), [Homelab](), [Docker](), [Kubernetes](), [Docker Image](), [kubectl](), [rancher](), [Dockerfile](), [nginx](), [React](), [Windows]() Tags: [continuous-delivery](), [continuous-integration](), [developer](), [docker](), [docker-container](), [docker-image](), [gitlab-ci](), [guide](), [homelab](), [kubectl](), [kubernetes](), [nginx](), [rancher](), [react](), [registry](), [self-hosted](), [testing](), [unit-tests](), [windows](), [wsl]() ### AI overview This tutorial explains how to set up a self-hosted development pipeline in a homelab. It covers repository setup, unit testing with a GitLab CI runner, building and publishing a Docker image to a container registry, and deploying the container to a self-hosted Kubernetes cluster with kubectl. ### Source excerpt So you're a software engineer or a developer who wants to self-host your own code in your own homelab? Well this is the tutorial for you! In this step-by-step guide we'll walk through setting up a repo, building and testing our own code (with unit tests) in a self-hosted Gitlab CI runner in our CI pipeline, then we'll build a Docker image and push it up to a container registry, then we'll use... ## Setting up GitLab CI for Android Projects DevFeed: [Setting up GitLab CI for Android Projects]() Original publisher: [Read original article]() Author: Stojan Anastasov Published: 2017-12-03T00:00:00Z Content type: tutorial Language: en Sources: [Stojan Anastasov's blog]() Topics: [GitLab](), [Android](), [ci](), [SDK](), [Command-line interface](), [Testing]() Tags: [android](), [android-testing](), [androiddev](), [command-line](), [continuous-integration](), [gitlab](), [gitlab-ci](), [sdk](), [unit-testing]() ### AI overview A tutorial for configuring GitLab CI for Android projects. It explains installing Android command-line tools and SDK packages, transferring accepted licenses to a CI server, and handling emulator limitations when running functional tests. ### Source excerpt My first experience with continuous integration was using Bitbucket in combination with Jenkins. I was pretty happy with my setup. Jenkins would run on every commit making sure my code compiles, run android lint and run my unit tests. I also set up continuous deployment using Fabric. Now, at work, we use GitLab as a code repository. GitLab also offers continuous integration. When we decided to start using continuous integration at work we decided to give GitLab a chance. It was already integrated with GitLab and to use it we just needed to install a runner. Using CI with GitLab is simple, after you install a runner you need to add a .gitlab-ci.yml file at the root of the repository. GitLab even offers template .gitlab-ci.yml files for various languages and frameworks. The android template is based on this blog post from 2016. It is a great guide but unfortunately today it doesn't work. Google introduced a few changes in the command line tools. Installing Android SDK To install the Android SDK on a CI we need to install the command line tools (scroll to the bottom to Get just the command line tools). The command line tools include the sdkmanager - a command line tool that allows you to view, install, update, and uninstall packages for the Android SDK. So instead of - wget --quiet --output-document=android-sdk.tgz https://dl.google.com/android/android-sdk_r${ANDROID_SDK_TOOLS}-linux.tgz - tar --extract --gzip --file=android-sdk.tgz we can use - wget --quiet --output-document=android-sdk.zip https://dl.google.com/android/repository/sdk-tools-linux-3859397.zip - unzip -q android-sdk.zip -d android-sdk-linux to download and install the Android SDK tools. There is also an improvement in accepting licenses for the Android SDK. After you accept the licenses on your development machine the tools will generate a licenses folder in the Android SDK root directory. You can transfer the licenses from your development machine to your CI server. To accept the licenses we can use: -