Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
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

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.

Atlassian Community about banner
4,463,030
Community Members
 
Community Events
176
Community Groups

Job hanging due to clover artifact

I have some jobs that post some clover reports. I do this by using a script to copy the clover reports generated for the build into the current job and having bamboo detect these clover files in the "Job Miscellaneous" configuration. The logs show that everything ran successfully but the job hangs and doesn't complete. Once the job times out the job is successful and continues to the next job. Why is the job hanging? Is there a bug in bamboo's clover feature I'm not aware of? It was previously working.

 

Here is my configuration

Clover Setting.png

The output I get is shown below, everything looks fine.

Clover Log.png

1 answer

0 votes

Hi @schow-lmi3d

I can see the problem is happening when publishing the artifact. I'm not really sure if the clover plugin is the only source for this issue. I have some questions that would help us to investigate this scenario further:

  • Have you had the opportunity to check the logs to see what stack traces are showing up there?
  • What other variables you could adjust to verify if this error will keep happening or not?
    • Changing from remote agent to local agent (or vice-versa), does it help?
    • Are all the clover reports causing this issue or just this one?
    • Are you able to publish other artifacts in this build with a similar size of this one?
  • Have you checked if the file was available to be published?
  • Was this feature working before?
  • What is the OS involved and Bamboo version?

Any other details that help us to investigate this issue will be welcome =]

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events