Jenkins Pipeline Setup for Salesforce
Budget: ₹400 – ₹750 INR
Our Salesforce engineering team is ready to move away from manual builds and deploys. I want a fresh Jenkins pipeline built from scratch that pulls our Bitbucket repository, runs the relevant unit-tests, packages the metadata with sfdx, and deploys automatically to our Salesforce sandboxes (and later production).
Key points you’ll be working on:
• Pipeline setup and configuration: create a clean, reproducible Jenkinsfile with stages for checkout, test execution, static code analysis, packaging, and deployment.
• New pipeline rather than modifying an existing one: the job should live in its own folder on our Jenkins server and follow shared-library best practices so we can expand later.
• Bitbucket integration: use webhooks so every push triggers the pipeline, handle branch-based environment mapping (e.g., develop → Dev Sandbox, release/* → UAT).
Acceptance criteria
• Jenkinsfile committed to the repo, fully parameterized and documented.
• Successful build triggered from a Bitbucket push, visible in Jenkins with green status when tests pass.
• Deployment logs stored as artifacts; failed steps fail the build cleanly with readable output.
• Quick setup notes so another team member can recreate the job on a new Jenkins instance in under 15 minutes.
Tools you may reference: Jenkins 2.x, Blue Ocean UI, sfdx CLI, PMD Apex, Git SSH keys.
Key points you’ll be working on:
• Pipeline setup and configuration: create a clean, reproducible Jenkinsfile with stages for checkout, test execution, static code analysis, packaging, and deployment.
• New pipeline rather than modifying an existing one: the job should live in its own folder on our Jenkins server and follow shared-library best practices so we can expand later.
• Bitbucket integration: use webhooks so every push triggers the pipeline, handle branch-based environment mapping (e.g., develop → Dev Sandbox, release/* → UAT).
Acceptance criteria
• Jenkinsfile committed to the repo, fully parameterized and documented.
• Successful build triggered from a Bitbucket push, visible in Jenkins with green status when tests pass.
• Deployment logs stored as artifacts; failed steps fail the build cleanly with readable output.
• Quick setup notes so another team member can recreate the job on a new Jenkins instance in under 15 minutes.
Tools you may reference: Jenkins 2.x, Blue Ocean UI, sfdx CLI, PMD Apex, Git SSH keys.