Skip to content
cccskills
FreePublished on GitHub

jenkinsfile-test-stages

Configures Jenkins declarative pipeline test stages - `Jenkinsfile` with stages, parallel + per-agent execution, post-actions (always / failure / success), pipeline-junit-plugin for test reports, lockable resources for shared infra. Use for Jenkins-based CI (common in enterprise / regulated environments).

The English summary is being prepared. Showing the original description.

testland/qa13 stars(GitHub 13 + cccskills 0)
Works withGitLabDocker

Run score Not tested

See how to install

Files included (5)

  • SKILL.md7.3 KB
  • .tessl-plugin/plugin.json446 B
  • references/environment-and-triggers.md1.6 KB
  • references/parallel-and-matrix.md1.7 KB
  • references/post-actions.md1.2 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

jenkinsfile-test-stages

Overview

Jenkins Declarative Pipeline (introduced 2017) is the modern Jenkinsfile syntax - replaces older Scripted Pipeline for most use cases.

A Jenkinsfile defines:

  • Pipeline - top-level container.
  • Agent - where stages run (any agent / specific node / Docker container).
  • Stages - sequential or parallel phases.
  • Steps - commands within a stage.
  • Post - actions after stages (always / success / failure / unstable / changed).

When to use

  • Enterprise / regulated environments using Jenkins.
  • Existing Jenkins infrastructure; migration to GitHub Actions / GitLab CI prohibitive.
  • Self-hosted CI / specialized hardware needs (GPU, specialized drivers).

For new projects in 2026+: GitHub Actions / GitLab CI offer better managed-runner experiences. Jenkins shines in self-hosted

  • plugin-rich environments.

How to use

  1. Add a Jenkinsfile with a pipeline { agent ...; stages { ... } } block; choose agent any, a labelled node, or a Docker image for reproducibility (Steps 1-2).
  2. Define stage('Build') / stage('Test') steps that run your install + test commands via sh.
  3. Parallelize independent suites and fan across an OS × runtime matrix - references/parallel-and-matrix.md.
  4. Add a post {} block to publish JUnit XML, archive artifacts, and notify per outcome - references/post-actions.md.
  5. Inject environment {} + masked withCredentials, serialize shared infra with lock(...), and set triggers / options - references/environment-and-triggers.md.
  6. Reach for retry(2) only on genuinely non-deterministic steps; prefer quarantine.
  7. Review the anti-patterns table before committing.

Step 1 - Basic Jenkinsfile

// Jenkinsfile
pipeline {
    agent any

    stages {
        stage('Build') {
            steps {
                sh 'npm ci'
            }
        }
        stage('Test') {
            steps {
                sh 'npm test'
            }
        }
    }
}

agent any runs on any available executor; pin via agent { label 'linux' } or agent { docker { image 'node:22' } }.

Step 2 - Docker agent

pipeline {
    agent {
        docker {
            image 'node:22'
            args '-v /tmp:/tmp'
        }
    }

    stages {
        stage('Test') {
            steps {
                sh 'npm ci && npm test'
            }
        }
    }
}

Docker agents provide reproducibility - same Node version on every run.

Advanced pipeline patterns

Deeper stage recipes are split into reference files:

When to retry

stage('Test') {
    steps {
        retry(2) {
            sh 'npm test'
        }
    }
}

Use sparingly - retries hide flake. Prefer flaky-test-quarantine (in the qa-flake-triage plugin).

Worked example

A regulated team runs its suite on a self-hosted Jenkins with a shared integration database.

  1. The Jenkinsfile pins agent { docker { image 'node:22' } } so every run uses the same runtime.
  2. A Tests stage runs Unit and Integration in parallel; the E2E branch overrides its agent to a mcr.microsoft.com/playwright:v1.50.0-noble image.
  3. The Integration step wraps its work in lock(resource: 'shared-test-database') so only one build touches the DB at a time.
  4. withCredentials([...]) injects the registry token, masked in logs; environment { CI = 'true' } marks the run as CI.
  5. post { always { junit 'reports/junit/*.xml'; archiveArtifacts 'coverage/**' } } publishes results either way, and failure { slackSend(...) } pings #ci on a red build.
  6. options { timeout(time: 30, unit: 'MINUTES') } kills hung builds so they don't hold executors.

Result: reproducible runs, no DB contention across parallel builds, and test reports plus notifications on every outcome.

Anti-patterns

Anti-patternWhy it failsFix
Scripted pipeline for new codeDeclarative is the standard; better tooling support.Declarative Pipeline (Step 1).
Plaintext credentials in JenkinsfileSecret leak.withCredentials({...}) (environment-and-triggers).
No post { always {} } for artifact uploadFailure investigation incomplete.Always upload (post-actions).
Single-agent pipeline for parallel workNo parallelism; slow.Parallel stages (parallel-and-matrix).
Missing timeoutHung jobs consume executors indefinitely.options { timeout(...) } (environment-and-triggers).
Skipping agent { docker {...}}Inconsistent runtime per agent; hard to reproduce.Docker agents (Step 2).

Limitations

  • Plugin-heavy ecosystem. Updates can break things; pin versions.
  • Self-hosted infra cost. Manage Jenkins controller + agents.
  • Slower modernization. Jenkins evolves; modern features (matrix, declarative) require version bumps.
  • YAML / Groovy mix. Jenkinsfile is Groovy DSL; some teams prefer YAML.

References

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

a11y-violation-gate

Free

Builds a CI gate that fails the build on **new** WCAG / a11y violations introduced by a PR while grandfathering pre-existing violations on a per-rule / per-page baseline. Aggregates verdicts from axe-core / pa11y / Lighthouse a11y / WAVE / IBM Equal Access scans. Use when a project has accumulated a11y debt and a strict "zero violations" gate would block every PR - the ratchet pattern lets the team ship while preventing regressions.

The English summary is being prepared. Showing the original description.

testland/qa13Updated Oct 20, 2026

ab-test-validity-checklist

Free

Workflow skill that builds an A/B-test validity checklist from an experiment proposal, walking the canonical design-correctness gates - pre-registered OEC/power/guardrails, randomization unit + SRM check, assignment integrity, telemetry, peeking discipline, novelty/primacy, post-experiment SRM re-check - into a per-experiment checklist + sign-off form. Use when launching, auditing, or governing an experiment. For pitfall mechanics (guardrails, peeking) see experiment-results-interpreter's references; to read an already-valid result use experiment-results-interpreter; for per-SDK harness tests use experiment-sdk-testing - this gates DESIGN, not SDK code.

The English summary is being prepared. Showing the original description.

testland/qa13Updated Oct 20, 2026

add-to-homescreen-flow-tests

Free

The single install-flow skill: the reference contract for the PWA install flow (installability gate fields, `beforeinstallprompt` handshake, per-platform paths - Android WebAPK / iOS Share menu / Firefox no-op - and the `display-mode` post-install signal, in references/install-flow-reference.md) plus the build-an-X workflow that emits the Add-to-Home-Screen suite. Walks the four-stage timeline, emitting one test per gate cell per [web.dev/articles/install-criteria][install-criteria], the deferred-prompt → `prompt()` → `userChoice` chain per [web.dev/articles/customize-install][customize-install], the iOS Safari manual-metadata branch (`apple-touch-icon`) per [web.dev/learn/pwa/installation][learn-pwa], and the post-install `(display-mode: standalone)` MQ assertion. Output: a Playwright spec with per-stage cells plus a coverage matrix. Use when a PWA's manifest, icons, or install handler change, when install conversion drops at an unknown stage, or when triaging a flaky install assertion.

The English summary is being prepared. Showing the original description.

testland/qa13Updated Oct 20, 2026

ai-spec-coverage-mapper

Free

Build-an-X workflow that uses an LLM to map existing tests to spec sections - given a spec doc + the test suite, the LLM identifies which tests cover which sections, surfaces uncovered sections (gap), and recommends specific tests to add. Output is a coverage matrix per spec ID. Scope is mapping tests that already exist and naming the gaps, not authoring tests for new acceptance criteria. Use when a spec doc and a test suite both exist but nobody can say which requirements are actually covered - before a release sign-off, an audit, or a decision about where to spend the next round of test effort.

The English summary is being prepared. Showing the original description.

testland/qa13Updated Oct 20, 2026

ai-test-generator

Free

Generates tests from natural-language specs (acceptance criteria, user stories, requirements) using an LLM, with confidence scoring per test case (LLM self-assessment plus heuristics: assertion quality, naming, completeness), batching uncertain cases for human review, and integration with the team's existing test framework. Use when the user asks to generate unit tests from acceptance criteria, convert user stories to test cases, automate test creation from requirements, or augment a spec-driven test suite with AI-generated stubs that are then curated before merge.

The English summary is being prepared. Showing the original description.

testland/qa13Updated Oct 20, 2026

allure-reports

Free

Configures Allure Report (test-runner adapter install, `allure-results` directory wiring, `categories.json` for failure classification, `history-trend.json` retention via the copy-history-between-runs pattern), runs the Allure CLI to convert `allure-results` to a static HTML site, and uploads the report as a CI artifact. Use when the team needs richer test reporting than JUnit XML - step-level attachments, per-test history, retry tracking, and severity / epic / feature labeling across framework-agnostic adapters (pytest, Jest, JUnit, TestNG, NUnit, Mocha). As a rich static HTML report generator, it is the open-source alternative to the sunset ExtentReports (JVM/.NET per-test HTML narrative); for hosted cross-run flakiness analytics rather than a static per-run report use currents-integration.

The English summary is being prepared. Showing the original description.

testland/qa13Updated Oct 20, 2026

See all skills by testland

Report a problem with this skill