Hi everyone,
I got a strange issue on a new repo i've create.
when i try to run a bitbucket-pipeline, i got this error :
+ umask 000
+ GIT_LFS_SKIP_SMUDGE=1 git clone --branch="master" --depth 50 https://x-token-auth:$REPOSITORY_OAUTH_ACCESS_TOKEN@bitbucket.org/Julien-Amblard/brush-photoshop-admin.git $BUILD_DIR ; git reset --hard d442d1602b62461b01d001bd88ae6c3043c3348f ; git remote set-url origin git@bitbucket.org:Julien-Amblard/brush-photoshop-admin.git
Cloning into '/opt/atlassian/pipelines/agent/build'...
HEAD is now at d442d16 test
+ chmod 777 $BUILD_DIR
+ apt-get update
bash: apt-get: command not found
Searching for test report files in directories named [test-results, failsafe-reports, test-reports, surefire-reports] down to a depth of 4
Finished scanning for test reports. Found 0 test report files.
Merged test suites, total number tests is 0, with 0 failures and 0 errors.
here is my pipeline script :
image: samueldebruyn/debian-git pipelines: default: - step: script: - apt-get update - apt-get -qq install git-ftp - git ftp init --user $FTP_USERNAME --passwd $FTP_PASSWORD $FTP_HOST
note that i have the same script runing on another repos and everythings run just fine !
i searching on the web but i juste don't find anyone having the same issue than me
What i didn't see ? am i a complete idiot ?
Thanks for the help
ok i finally fix it !!
you want to know how ? me too..
In the settings, i rename an environement variable : $PATH -> $ANOTHER_RANDOM_STRING
and it work.... why ? who know ! i think "PATH" is a reserve keyword that we should not use.
i'm not sure this is a valid answer, but, meh..
$PATH contains the list of directories a unix-like system will look in for stuff to run when you do not specify one
For example, on this laptop,
$ echo $PATH
/usr/lib/jvm/java-8-oracle/bin:/home/nic/bin:/home/nic/bin:/usr/local/git/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.