Pipelines – script is not generating dist folder or it's not visible

IgorPodlawski

Hello!

I'm trying to use Bitbucket Pipelines to deploy my Nuxt.js based web app. Below there is my bitbucket pipelines config:

image: node

pipelines: 
  custom: 
    init:
      - step:
        caches:
          - node
        script:
          - yarn install
          - yarn build --spa
          - echo "$(ls -la dist/)" 
          - ls
      - step: 
        script:
          - ls

And It is simplest as possible. It's installing all dependencies (yarn install) and using nuxt command yarn build --spa.

Yarn build --spa command is creating new dist folder and putting there build files. If dist folder were already existing script removes that folder and creates new dist folder. If I run this commands on my local machine I'm getting new dist folder filled with build files.

Whole steps are working fine, build step also, but finally there isn't any dist folder.

Most related topic on the internet that I've found is that: https://github.com/nuxt/nuxt.js/issues/5344 – but is more about docker image than bitbucket pipeline. Is there anything that I can fix in my config without creating new docker image?

Oleksandr Kyrdan

Hi @IgorPodlawski ,

Thank you for your feedback!

All should work well with the next Bitbucket pipelines config.

image: node

pipelines:
  custom: # Pipelines that can only be triggered manually
    init:
      - step:
          script:
            - yarn install
            - yarn build --spa
            - echo "$(ls -la dist/)" 
            - ls
          artifacts: # defining the artifacts to be passed to each future step.
            - dist/**
      - step:
          script:
            - ls

You can validate your bitbucket-pipelines.yml with the online validator.
Also to use `dist` directory in the next steps you should define artifacts.

Cheers, 
Alex