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,456,630
Community Members
 
Community Events
176
Community Groups

MatlabEngineTest Failing in Bamboo

Hi Team,

We are trying to build maven project via bamboo cicd.  In that we are using matlab to execute our test cases.  While building test cases are failed with below matlab error.

MatlabEngineTest.initMatlab:22 » UnsatisfiedLink Failed to find the library mc...

 

Please share your valuable input to fix this error.

Note - I have installed matlab in my system and that installed location in path variable as well.

 

1 answer

0 votes

Hi @MuruganSankar

It would be great if you could share the build log errors right before this one. They would probably help us to see what could be causing this one. I'm assuming this is working on terminal, but not in Bamboo. Is that correct?

Please keep in mind that after changing/adding environment variables you need to make sure the remote agent is also restarted. If you are using a local agent you will need to restart the Bamboo server. This happens because environment variables are inherited from the parent process when Bamboo or the remote agent is started and new changes are not noticed. This is not an issue, but the way the OS works.

Suggestions for moving forward :

  • Restart the server or remote agent if necessary.
  • Check if this maven build is working from the terminal (considering the agent machine used for this build).
  • Share more log lines around this error to allow us sharing more ideas for troubleshooting this.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events