Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Top groups
Explore all groups
Community resources
Learn
Community resources
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Join now to unlock these features and more

Why a Bitbucket repository doesn't trigger a *parameterized* Jenkins build job?

Edited
Andreas Galek
Andreas Galek May 08, 2017

Hi,

on our own Bitbucket server I have a repository with a post-commit Jenkins hook configured in there. Every commit in the repository should trigger the configured Jenkins build job's run.

The problem is that if the Jenkins job is parameterized then the trigger doesn't work. The Jenkins job doesn't start.

How can this problem be solved? Any ideas?

Thanks in advance.

Andreas

Answer
Watch
Like Be the first to like this
395 views

1 answer

0 votes
Craig Nodwell
Craig Nodwell
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Become a leader
Feb 05, 2023

Are you passing the value down to the parameterized build?

Reply

Suggest an answer

Log in or Sign up to answer
Bitbucket
Bitbucket
TAGS
AUG Leaders

Atlassian Community Events

See all events