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,459,771
Community Members
 
Community Events
176
Community Groups

Changing umask for Remote bamboo agents

My dev team would like to change the umask under which the bamboo agents run so that people building plans can access their files after they have finished. The default is 022 and we need 002. Simply setting the umask in the bamboo-agent.sh script does not work. 

1 answer

Simon says:

"

You can override the default system wide umask value in the profile of each user. For example you can add the line:

umask 002

at the bottom of the .profile configuration file that is located in the home of the user that runs the remote agent. (Don't forget to start a new session after making the change or source the file in a new shell). Depending on which shell the user is using you may have to set the value in a different file. (For bash you can set it either in ~/.profile or ~/.bashrc. Note that the tilde means the home of the user that runs the agent).

"

Simon out

I have already tried this. I attempted to modify /etc/bashrc and /etc/profile as well without any luck. 

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events