Skip to content

screendriver/gitlab-pipeline-deleter

Folders and files

NameName
Last commit message
Last commit date

Latest commit

c14fc02 Β· May 23, 2025
Sep 25, 2024
Sep 25, 2024
Sep 25, 2024
Sep 20, 2023
Jul 16, 2023
Sep 29, 2020
Nov 9, 2021
Sep 25, 2024
Sep 29, 2020
Jul 16, 2023
Jul 16, 2023
Jul 15, 2023
Sep 25, 2024
Sep 20, 2023
Jul 16, 2023
Jul 18, 2023
May 23, 2025
May 23, 2025
Sep 25, 2024
Jul 18, 2023
Jul 18, 2023

Repository files navigation

gitlab-pipeline-deleter

GitHub Actions status

A Node.js CLI tool that deletes old GitLab CI pipelines.

Installation

$ npm install -g gitlab-pipeline-deleter

Usage

Usage: glpd [options] [gitlab-url] [project-id] [access-token]

Deletes old GitLab pipelines

Options:
  -d --days <days>  older than days (default: "30")
  --trace           show stack traces for errors when possible (default: false)
  -h, --help        display help for command

You can use either the command line arguments gitlab-url, project-id and access-token (the access-token needs to be owner of the project. See https://docs.gitlab.com/ee/api/pipelines.html#delete-a-pipeline for more information) or you can create a glpd.config.js configuration file that exports an object. Both CommonJS (.cjs) and ECMAScript Modules (.mjs) are supported. All of the command line arguments are supported but needs to be written in camelCase:

export default {
    gitlabUrl: 'https://example.com',
    projectId: '42',
    accessToken: '<my-token>',
    days: 30,
    trace: false,
};

If you specify command line arguments and a configuration file the command line arguments will overwrite the values in the configuration file. So the CLI arguments has always precedence.

Multiple project ids can be configured by providing a comma-separated list to the projectId argument.