nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Wrong file permissions when bamboo job checkout

avner_xvtec

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

Accepted answers

Foong

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.

All comments

jredmond

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.

avner_xvtec

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

Foong

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.

avner_xvtec

Thanks!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

bitbucket

bitbucket-server

bamboo