NPM / NodeBuild

Node.js projects using Jenkins with Opsera Managed Jobs. Chain a native build step and an optional Jenkins Job step in the same pipeline for flexible Node workflows.

Prerequisites

• Jenkins tool registered in Opsera Tool Registry

• Opsera Managed Job created in Jenkins tool for Node buildsSCM account with Node.js project repository registered

Pipeline setup

1

Create Node build step

Tool = Jenkins, Step Type = Build. In Step Settings: Jenkins Tool = your registered Jenkins instance, Jenkins Job Type = Opsera Managed Job, Tool Job = the Node job.

2

Configure source

Select Account, Repository, and Branch Name. Add Parameter Selection entries and enter the required build commands (e.g. npm install, npm run build).

3

Add Jenkins Job step (optional)

For custom job-level configuration, add a second Jenkins step after the build step with the same field structure. Use this to run tests, lint, or post-build tasks as separate pipeline stages.

Points to remember

• Always selectOpsera Managed Job as Job Type — this ensures Opsera manages job provisioning, resource allocation, and log capture automatically.

• Use separate pipeline steps for install, build, and test phases to get granular per-step logs and failure isolation.

• Parameter Selection entries in Step Settings are the correct place to inject environment variables (e.g.NODE_ENV=production) — do not hardcode these in commands.