While trying to run a test automation suite in pipeline getting error, but the same command works locally:
+ umask 000
+ GIT_LFS_SKIP_SMUDGE=1 retry 6 git clone --branch="main" --depth 50 https://x-token-auth:$REPOSITORY_OAUTH_ACCESS_TOKEN@bitbucket.org/$BITBUCKET_REPO_FULL_NAME.git $BUILD_DIR
Cloning into '/opt/atlassian/pipelines/agent/build'...
+ git reset --hard 23070c5744edc443f3313c3b06698d526f53e002
HEAD is now at 23070c5 https://bitbucket.org/krishnatest1/nc-test-automation/src/23070c5744edc443f3313c3b06698d526f53e002/bitbucket-pipelines.yml edited online with Bitbucket
+ git config user.name bitbucket-pipelines
+ git config user.email commits-noreply@bitbucket.org
+ git config push.default current
+ git config http.${BITBUCKET_GIT_HTTP_ORIGIN}.proxy http://localhost:29418/
+ git remote set-url origin http://bitbucket.org/$BITBUCKET_REPO_FULL_NAME
+ git reflog expire --expire=all --all
+ echo ".bitbucket/pipelines/generated" >> .git/info/exclude
+ chmod 777 $BUILD_DIR
Images used:
build : docker.io/library/node@sha256:a5d9200d3b8c17f0f3d7717034a9c215015b7aae70cb2a9d5e5dae7ff8aa6ca8
+ npm test
> nc-testing@1.0.0 test
> jest webservices/specs/sanity/**/*.test.ts --group=$GROUP --maxWorkers=2 --forceExit
/tmp/test-bc16b754.sh: 1: /tmp/test-bc16b754.sh: jest: not found
Searching for test report files in directories named [test-results, failsafe-reports, test-reports, TestResults, 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.
Issue resolved, need to pass the node_modules as artifacts
Hi @Krishna Kumar Singhal how did you point your artifacts option to node_modules? tia!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.