You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi,
I have a plan in bamboo - and the first task is to check out a repository.
(the git server is bitbucket server)
When I checkout manually, and when the bamboo does the checkout I get different file permissions:
Manual:
drwxrwxr-x 8 bamboo bamboo 4096 Feb 6 14:57 rootfs
Bamboo:
drwxr-x--- 8 bamboo bamboo 4096 Feb 6 15:01 rootfs
What is going on there? I need the bamboo to checkout with the same permissions
Thanks
Avner
The latest Bamboo have a setting that affect the file permission.
Edit the file <bamboo-install>/bin/catalina.sh for the following line to change the permission:
# Set UMASK unless it has been overridden
if [ -z "$UMASK" ]; then
UMASK="0027"
fi
umask $UMASK
Bamboo have to be restarted after the modification.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Git only tracks the executable bit and the file type in a file mode - it doesn't track ownership or the read or write bits, so those parts are left to the client to determine. You'll need to ask this in the Bamboo section.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks
1. There are differences also in executable attributes
2. So if so, why is the differences between the bamboo does the cloning and when I am doing it (in the same path)
Avner
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.