Community Announcements have moved! To stay up to date, please join the new Community Announcements group today. Learn more
×
From time to time (I can't catch the rule), it happens timeout for the emial-notify pipe. The email is sent weather the step if successful or failed. The timeout is stochastic and it happens not matter of the step result. Attacment is less than 1MB. Please find the log bellow:
-------------------------------------------------------------------------------------------
pipe: atlassian/email-notify:0.13.213s
+ docker container run \
--volume=/opt/atlassian/pipelines/agent/build:/opt/atlassian/pipelines/agent/build \
--volume=/usr/local/bin/docker:/usr/local/bin/docker:ro \
--volume=/opt/atlassian/pipelines/agent/ssh:/opt/atlassian/pipelines/agent/ssh:ro \
--volume=/opt/atlassian/pipelines/agent/build/.bitbucket/pipelines/generated/pipeline/pipes:/opt/atlassian/pipelines/agent/build/.bitbucket/pipelines/generated/pipeline/pipes \
--volume=/opt/atlassian/pipelines/agent/build/.bitbucket/pipelines/generated/pipeline/pipes/atlassian/email-notify:/opt/atlassian/pipelines/agent/build/.bitbucket/pipelines/generated/pipeline/pipes/atlassian/email-notify \
--workdir=$(pwd) \
--label=org.bitbucket.pipelines.system=true \
--env=BITBUCKET_STEP_TRIGGERER_UUID="$BITBUCKET_STEP_TRIGGERER_UUID" \
--env=BITBUCKET_REPO_FULL_NAME="$BITBUCKET_REPO_FULL_NAME" \
--env=BITBUCKET_GIT_HTTP_ORIGIN="$BITBUCKET_GIT_HTTP_ORIGIN" \
--env=BITBUCKET_PROJECT_UUID="$BITBUCKET_PROJECT_UUID" \
--env=BITBUCKET_REPO_IS_PRIVATE="$BITBUCKET_REPO_IS_PRIVATE" \
--env=BITBUCKET_WORKSPACE="$BITBUCKET_WORKSPACE" \
--env=BITBUCKET_SSH_KEY_FILE="$BITBUCKET_SSH_KEY_FILE" \
--env=BITBUCKET_REPO_OWNER_UUID="$BITBUCKET_REPO_OWNER_UUID" \
--env=BITBUCKET_BRANCH="$BITBUCKET_BRANCH" \
--env=BITBUCKET_REPO_UUID="$BITBUCKET_REPO_UUID" \
--env=BITBUCKET_PROJECT_KEY="$BITBUCKET_PROJECT_KEY" \
--env=BITBUCKET_REPO_SLUG="$BITBUCKET_REPO_SLUG" \
--env=CI="$CI" \
--env=BITBUCKET_REPO_OWNER="$BITBUCKET_REPO_OWNER" \
--env=BITBUCKET_STEP_RUN_NUMBER="$BITBUCKET_STEP_RUN_NUMBER" \
--env=BITBUCKET_BUILD_NUMBER="$BITBUCKET_BUILD_NUMBER" \
--env=BITBUCKET_GIT_SSH_ORIGIN="$BITBUCKET_GIT_SSH_ORIGIN" \
--env=BITBUCKET_PIPELINE_UUID="$BITBUCKET_PIPELINE_UUID" \
--env=BITBUCKET_PIPELINES_VARIABLES_PATH="$BITBUCKET_PIPELINES_VARIABLES_PATH" \
--env=BITBUCKET_COMMIT="$BITBUCKET_COMMIT" \
--env=BITBUCKET_CLONE_DIR="$BITBUCKET_CLONE_DIR" \
--env=PIPELINES_JWT_TOKEN="$PIPELINES_JWT_TOKEN" \
--env=BITBUCKET_STEP_UUID="$BITBUCKET_STEP_UUID" \
--env=BITBUCKET_DOCKER_HOST_INTERNAL="$BITBUCKET_DOCKER_HOST_INTERNAL" \
--env=DOCKER_HOST="tcp://host.docker.internal:2375" \
--env=BITBUCKET_PIPE_SHARED_STORAGE_DIR="/opt/atlassian/pipelines/agent/build/.bitbucket/pipelines/generated/pipeline/pipes" \
--env=BITBUCKET_PIPE_STORAGE_DIR="/opt/atlassian/pipelines/agent/build/.bitbucket/pipelines/generated/pipeline/pipes/atlassian/email-notify" \
--env=ATTACHMENTS="$ATTACHMENTS" \
--env=BODY_PLAIN="Go to link and see build result <a href='https://bitbucket.org/${BITBUCKET_WORKSPACE}/${BITBUCKET_REPO_SLUG}/addon/pipelines/home#!/results/${BITBUCKET_BUILD_NUMBER}'>build#${BITBUCKET_BUILD_NUMBER}</a>" \
--env=DEBUG="true" \
--env=FROM="$EMAIL_USERNAME" \
--env=HOST="$EMAIL_HOST" \
--env=PASSWORD="$EMAIL_PASSWORD" \
--env=PORT="$EMAIL_PORT" \
--env=SUBJECT="Report for the build ${BITBUCKET_BRANCH}" \
--env=TO="$EMAIL" \
--env=USERNAME="$EMAIL_USERNAME" \
--env=BITBUCKET_EXIT_CODE="$BITBUCKET_EXIT_CODE" \
--add-host="host.docker.internal:$BITBUCKET_DOCKER_HOST_INTERNAL" \
bitbucketpipelines/email-notify:0.13.2
Unable to find image 'bitbucketpipelines/email-notify:0.13.2' locally
0.13.2: Pulling from bitbucketpipelines/email-notify
efc2b5ad9eec: Pulling fs layer
5b36cea6ecc3: Pulling fs layer
20dccfbf27d1: Pulling fs layer
5378e3337df7: Pulling fs layer
420671bdeb40: Pulling fs layer
425bc5d13e79: Pulling fs layer
b2ffe598748d: Pulling fs layer
27a5115e1fc9: Pulling fs layer
aa382114b57e: Pulling fs layer
5378e3337df7: Waiting
420671bdeb40: Waiting
425bc5d13e79: Waiting
b2ffe598748d: Waiting
27a5115e1fc9: Waiting
aa382114b57e: Waiting
5b36cea6ecc3: Verifying Checksum
5b36cea6ecc3: Download complete
20dccfbf27d1: Verifying Checksum
20dccfbf27d1: Download complete
5378e3337df7: Verifying Checksum
5378e3337df7: Download complete
420671bdeb40: Download complete
efc2b5ad9eec: Download complete
27a5115e1fc9: Download complete
425bc5d13e79: Download complete
b2ffe598748d: Verifying Checksum
b2ffe598748d: Download complete
aa382114b57e: Verifying Checksum
aa382114b57e: Download complete
efc2b5ad9eec: Pull complete
5b36cea6ecc3: Pull complete
20dccfbf27d1: Pull complete
5378e3337df7: Pull complete
420671bdeb40: Pull complete
425bc5d13e79: Pull complete
b2ffe598748d: Pull complete
27a5115e1fc9: Pull complete
aa382114b57e: Pull complete
Digest: sha256:b64fb56d37ab9df6f9a8ef595cf9a3130fa40f79e6cb60c608e0ef9eb1650ff0
Status: Downloaded newer image for bitbucketpipelines/email-notify:0.13.2
DEBUG: Starting new HTTPS connection (1): bitbucket.org:443
DEBUG: https://bitbucket.org:443 "GET /bitbucketpipelines/official-pipes/raw/master/pipes.prod.json HTTP/11" 200 None
INFO: Sending email...
✖ Failed to send email to $CONFLUENCE_USER. Check your configuration settings: timed out