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
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

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Get started Tell me more
Atlassian Community about banner
4,641,787
Community Members
 
Community Events
196
Community Groups

Failure notification emails for deployment successes being received with broken links

Simon Oliver
Simon Oliver Aug 06, 2018

I've been getting a notification failure for all 20 of my overnight deployments every day for a few days, but when I investigate, the deployments have succeeded. The links on the emails go to dead pages because they have larger id numbers than the actual logs (e.g. viewDeploymentResult.action?deploymentResultId=207454228 when the actual log is deploymentResultId=207388811)

I suspect a recent re-indexing, which is what I've told the IT dept. Has anyone encountered this before, and what is the resolution?

Answer
Watch
Like Be the first to like this
271 views

1 answer

0 votes
Foong
Foong
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Feb 11, 2019

It could be the current Bamboo server is copied to a test server.

The failure notification is coming from the test server but the Base URL in the test server is not updated so the notification email is still referring to the production server.

Reply

Suggest an answer

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

Atlassian Community Events

See all events