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; } } }

Why can't I see the artifacts?

piotrpodyma

Hi,

I run e2e tests on CI environment, but I cannot see the artifacts.

bitbucket-pipelines.yml:

image: cypress/base:10
options: max-time: 20
pipelines:
default:
-step:
script:
- npm install
- npm run test
artifacts:
- /opt/atlassian/pipelines/agent/build/cypress/screenshots/*
- screenshots/*.png
- **/*.png

Maybe I typed the wrong path, but I am not sure. Does anyone have any ideas what I am doing wrong?

Accepted answers

All comments

Philip Hodder

Hi Piotr,

What do you see if you list the content of directories?

image: cypress/base:10
options: max-time: 20
pipelines: 
    default: 
        - step: 
            script: 
                - npm install 
                - npm run test
                - ls -R /opt/atlassian/pipelines/agent/build/cypress/screenshots
                - ls -R screenshots
                - ls -R 
            artifacts: 
                - /opt/atlassian/pipelines/agent/build/cypress/screenshots/* 
                - screenshots/*.png
                - **/*.png

What are in the logs listed in your 'Build Teardown'? Is there any reference to artifacts?

Thanks,

Phil

piotrpodyma

Hi Philip Hodder,

Thank you for the answer.
I tried very many different cases to get screenshots, but it still doesn't work, even with your suggestion, and I have not any idea why, what wrong could be with it?

Thanks,
Piotr

Philip Hodder

Can you post the log output for a build using the configuration I provided? We can use that to debug further.

piotrpodyma

I tried as you wrote. When every pipeline (tests) failed then I always got this message:

What I'd like to do is to see screenshots when something went wrong.
Artifacts tab is still blank

Sabin.Ranjit

Hi
I'm facing the similar issue, step 1 produces .tar , step 2 can find it and use it but step 3 does not find the artifact at all.
any solution yet?

thanks

tatenda_fhm912

Same issue here. Any solution yet @Philip Hodder

Annet Andrew

hi guys,
I have tried what @Philip Hodder mentioned above and it's working this is my solution
this is the custom pipeline in my bitbucket config file to run cypress.
please try cypress/screenshots/**/*.png in artifact section

"cypress:pipeline": "cypress run --env user=${E2E_USER_EMAIL},pass=${E2E_USER_PASSWORD} --browser chrome --spec cypress/integration/src/**/*.spec.ts"

pipelines:
custom:
healthCheck:
      - step:
name: Integration and E2E Test
script:
            - npm install
            - npm run cypress:pipeline
artifacts:
# store any generated images as artifacts
            - cypress/screenshots/**/*.png

Welcome!

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

Quick Links

Find more posts tagged with

bitbucket

bitbucket-pipelines