Parameterized Builds for Jenkins (Deprecated) for Atlassian
- Price
- Free plan
- Listing audit
- 58/100
Parameterized Builds for Jenkins (Deprecated) is a Atlassian Marketplace app by Kyle Nicholls. With a rating of 4.7★ from 25 reviews.
Parameterized Builds for Jenkins (Deprecated) is a Atlassian app, with a 4.7 average rating from 25 reviews, free to use, as of Sep 11, 2026.
AppRanks verdict
Generated from marketplace data as of Sep 11, 2026
Parameterized Builds for Jenkins (Deprecated) is a Atlassian app. It holds a 4.7★ average from 25 reviews on Atlassian. It is free to use.
Pros
- +4.7★ average across 25 reviews
- +Free plan available — no paid subscription needed to start
Cons
- −Only 25 reviews — the average can still move with a few new ratings
About Parameterized Builds for Jenkins (Deprecated)
How Parameterized Builds for Jenkins (Deprecated) works
Show full descriptionShow less
Jenkins base settings are configured on the admin page in Bitbucket or per project. Here you can setup the base URL for Jenkins and default authentication. Once this is setup you can start configuring and adding jobs in the Hook settings for a repository. Triggers inlcude: Branch created (can use pattern matching for branches) Push event (can use pattern matching for branches or file paths) PR events (opened, re-opened, re-scoped, declined, merged) Manual (adds a "Build in Jenkins" button to the branch action menus) Branch deleted Tag events Authentication for triggering a job can use one of 3 ways: Jenkins API token via admin page Job token via the hook settings Jenkins API token via user profile page (per user) You can add build parameters (including token, string, choice, and boolean). You can also use a custom variable "$BRANCH". During the trigger event this value will be replaced with the branch that triggered the build.