imperal.io
  • How it works
  • Use cases
  • Technology
  • Pricing
Login
Webbee AIWebbee Codeimperal-mcpDevelopers & SDKSecurity & Vault
Add an app · Marketplace
imperal.ioICNLI Cloud OS

One OS for everything you run. Webbee is your agent inside it, she does the work, you stay in control.

Product
  • Webbee
  • Webbee Code
  • Imperal MCP
  • Marketplace
  • Use cases
  • Pricing
  • Open panel
Resources
  • Security
  • Technology
  • Success stories
  • Blog
Developers
  • Developers
  • Docs
  • Quick start
  • SDK reference
  • Developer portal
Company
  • About
  • Contact
  • Legal
Open protocol
  • ICNLI
  • SDK on GitHub
© 2026 Imperal, Inc. · ICNLI published at icnli.org under CC BY-SA 4.0
TermsPrivacy
  1. Home
  2. /
  3. Marketplace
  4. /
  5. GitLab CI/CD

GitLab CI/CD Extension

🔄 CI/CD·by bluebeeweb·v0.1.0
Pay per use8-60 tok/action
Open in panel
0 capabilities14 actions1 installs

About this extension

Connect your own GitLab account (gitlab.com or self-managed) to see and manage CI/CD from Imperal -- pipelines (list/get/create/retry/cancel/delete), jobs (list/get/retry/cancel/play/erase/logs), runners (list/get/pause/resume/tag/delete), project and group CI/CD variables, pipeline trigger tokens, pipeline schedules (including cron variables), CI Lint validation, job artifacts (keep/delete), environments, and deployments (including approvals). Your Personal Access Token is verified against your own instance before it's saved. Scoped to CI/CD only -- repository files, merge requests, issues and project administration are out of scope.

What you get

Every capability exposed by GitLab CI/CD, metered per action and guarded by the two-step safety protocol.

  • connect_gitlabwrite

    Connect your GitLab instance by saving your Personal Access Token plus its base URL, after checking they actually work together. You'll need a Personal Access Token with the 'api' scope (or 'read_api' for read-only use) -- create it in User Settings > Access Tokens (works for both gitlab.com and your own self-managed instance). Scoped to CI/CD only -- repository files, merge requests and issues are out of scope here.

  • disconnect_gitlabwrite

    Disconnect a GitLab instance: deletes the saved Personal Access Token. Nothing in GitLab itself is changed; the token remains valid there until you revoke it yourself.

  • list_connectionsread

    List the connected GitLab instances.

  • list_pipelinesread

    List pipelines in a project, optionally filtered by ref, status, scope, source, or the username who triggered them.

  • get_pipelineread

    Read one pipeline in full -- status, timing, and its own CI/CD variables entrypoint.

  • get_pipeline_variablesread

    Read the CI/CD variables a specific pipeline run was actually triggered with.

  • get_pipeline_test_reportread

    Read a pipeline's aggregated JUnit test report, if the pipeline published one (total/success/failed/skipped/error counts per suite).

  • create_pipelinewrite

    Trigger a new pipeline run for a project on a given ref (branch/tag), optionally passing CI/CD variables.

  • retry_pipelinewrite

    Retry a failed or canceled pipeline's failed jobs.

  • cancel_pipelinewrite

    Cancel a running pipeline.

  • delete_pipelinedestructive

    Permanently delete a pipeline and its jobs/artifacts/logs. Cannot be undone.

  • list_project_jobsread

    List jobs across a project's pipelines, optionally filtered by status scope.

  • list_pipeline_jobsread

    List the jobs belonging to one pipeline, optionally filtered by status scope.

  • list_pipeline_bridgesread

    List the bridge (trigger) jobs of a pipeline -- jobs that trigger downstream/multi-project pipelines, with the downstream pipeline and project they triggered.

  • get_jobread

    Read one job in full -- status, timing, runner, and stage.

  • get_job_traceread

    Read a job's console log/trace, capped to the last N lines (traces can be very large).

  • retry_jobwrite

    Retry a failed or canceled job.

  • cancel_jobwrite

    Cancel a running job.

  • play_jobwrite

    Run a manual job that's waiting for a trigger.

  • erase_jobdestructive

    Erase a job's trace and artifacts (irreversible cleanup, job record itself stays).

  • list_runnersread

    List runners visible to you (or, with all_runners, every runner on the instance if you're an admin), optionally filtered by scope (active/paused/online/offline), type, or tags.

  • get_runnerread

    Read one runner in full -- version, IP, tags, timeout, and contact status.

  • update_runnerwrite

    Update a runner's description, pause state, tags, untagged-job acceptance, lock, access level, or max timeout. Only given fields change.

  • delete_runnerdestructive

    Permanently delete/unregister a runner. Cannot be undone.

  • list_runner_jobsread

    List jobs that ran on one specific runner, optionally filtered by status.

  • list_project_runnersread

    List runners enabled/assigned to a specific project.

  • enable_project_runnerwrite

    Enable (assign) an existing runner for a project so its pipelines can use it.

  • disable_project_runnerwrite

    Disable (unassign) a runner from a project. Does not delete the runner itself.

  • list_project_variablesread

    List CI/CD variables defined at project level.

  • get_project_variableread

    Read one project CI/CD variable's value and settings.

  • create_project_variablewrite

    Create a new project-level CI/CD variable -- key/value plus protection, masking, scope, and type settings.

  • update_project_variablewrite

    Update an existing project CI/CD variable's value/protection/masking/scope/description.

  • delete_project_variabledestructive

    Permanently delete a project CI/CD variable.

  • list_group_variablesread

    List CI/CD variables defined at group level (inherited by every project in the group).

  • get_group_variableread

    Read one group CI/CD variable's value and settings.

  • create_group_variablewrite

    Create a new group-level CI/CD variable, inherited by every project in the group.

  • update_group_variablewrite

    Update an existing group CI/CD variable's value/protection/masking/scope/description.

  • delete_group_variabledestructive

    Permanently delete a group CI/CD variable.

  • list_pipeline_triggersread

    List pipeline trigger tokens defined on a project.

  • create_pipeline_triggerwrite

    Create a new pipeline trigger token for a project -- use its token value with run_pipeline_trigger to trigger pipelines from external CI/CD systems without a full Personal Access Token.

  • update_pipeline_triggerwrite

    Update an existing pipeline trigger token's description.

  • delete_pipeline_triggerdestructive

    Permanently revoke/delete a pipeline trigger token.

  • run_pipeline_triggerwrite

    Trigger a pipeline run using a trigger token (not a Personal Access Token) -- GitLab's documented mechanism for external CI/CD systems.

  • list_pipeline_schedulesread

    List pipeline schedules (cron-triggered pipelines) defined on a project.

  • get_pipeline_scheduleread

    Read one pipeline schedule in full, including its next run time and owner.

  • create_pipeline_schedulewrite

    Create a new pipeline schedule -- a cron-triggered pipeline on a given ref.

  • update_pipeline_schedulewrite

    Update an existing pipeline schedule's description, ref, cron, timezone, or active state.

  • delete_pipeline_scheduledestructive

    Permanently delete a pipeline schedule.

  • run_pipeline_schedulewrite

    Trigger a pipeline schedule to run right now (rate-limited by GitLab to once per minute).

  • set_schedule_variablewrite

    Create or update a CI/CD variable attached to a pipeline schedule (upserts: creates if new, updates if the key already exists).

  • delete_schedule_variabledestructive

    Permanently remove a CI/CD variable from a pipeline schedule.

  • lint_ci_yamlread

    Validate raw .gitlab-ci.yml content against GitLab's CI Lint engine -- checks syntax and semantic errors before you commit a pipeline config.

  • project_lint_ci_yamlread

    Validate a project's own .gitlab-ci.yml (its current config on a ref, or explicit content), with the project's own includes/extends resolved.

  • get_job_artifacts_urlread

    Get the signed download URL for a job's artifacts archive. GitLab streams the binary archive directly rather than a JSON body, so this returns the URL to fetch rather than the archive itself.

  • keep_job_artifactswrite

    Mark a job's artifacts as kept -- exempts them from the project's expiry policy so they are never automatically deleted.

  • delete_job_artifactsdestructive

    Permanently delete a job's artifacts archive right now, ahead of its expiry policy. Cannot be undone.

  • list_environmentsread

    List environments (deployment targets like staging/production) defined on a project.

  • get_environmentread

    Read one environment in full -- its state, external URL, and deployment tier.

  • create_environmentwrite

    Create a new environment (deployment target) on a project.

  • update_environmentwrite

    Update an existing environment's name or external URL.

  • delete_environmentdestructive

    Permanently delete an environment. Cannot be undone.

  • stop_environmentwrite

    Stop an environment -- ends its active deployment (e.g. tears down a review app).

  • list_deploymentsread

    List deployments in a project, optionally filtered by environment or status.

  • get_deploymentread

    Read one deployment in full -- its environment, status, ref, and who triggered it.

  • approve_deploymentwrite

    Approve or reject a deployment awaiting manual approval (protected environments with approval rules configured).

  • bulk_retry_pipelineswrite

    Retry several pipelines in one call, by explicit pipeline ids. Continues past per-item failures and reports which succeeded.

  • bulk_cancel_pipelinesdestructive

    Cancel several running pipelines in one call, by explicit pipeline ids. Continues past per-item failures and reports which succeeded.

  • bulk_retry_jobswrite

    Retry several jobs in one call, by explicit job ids. Continues past per-item failures and reports which succeeded.

  • bulk_cancel_jobsdestructive

    Cancel several running jobs in one call, by explicit job ids. Continues past per-item failures and reports which succeeded.

  • get_failed_jobs_summaryread

    Value-add report: scan the most recent pipelines' failed jobs so recurring flaky/broken jobs stand out, instead of scrolling through every pipeline individually.

  • audit_project_ciread

    Value-add report: one-glance CI/CD health snapshot for a project -- pipeline success rate, failing pipelines, runner availability, and CI/CD variable documentation, as named check rows.

Related extensions

More extensions in CI/CD ready to enable in one click.

  • CircleCIConnect your own CircleCI account to manage pipelines, workflows, jobs, insights (success rate/duration/flaky tests), contexts (secrets), environment variables, schedules, checkout keys, webhooks,...
  • Ansible Automation PlatformConnect your own Ansible Automation Platform (Automation Controller) or open-source AWX instance to manage job templates, launch and monitor jobs, run workflows, manage projects/inventories/hosts/c...
  • NotesPersonal notes with folders, tags, full-text search, and trash management for your workspace.
  • Mail ClientMulti-provider email client - Google, Microsoft, Yahoo, IMAP. Inbox, send, reply, forward, search, archive, manage emails, contacts, custom folders/labels. Gmail batchModify for instant bulk operat...

Ready to use GitLab CI/CD?

Enable GitLab CI/CD in your Imperal workspace in one click - 10,000 free starter credits included.

Open in panel