The after-script commands are not running at all on some pipelines

Konstantinos_a8l8y8

The after-script section in the following custom pipeline is never triggered:

pipelines:
  custom:
    test-job:
      - step:
          name: Run Postman
          image: alpine:3.15
          script:
            - apk add npm bash
            - npm install -g newman
            - echo "This runs"
          after-script:
            - echo "This doesn't run"

Although the following works:

pipelines:
  custom:
    test-job:
      - step:
          name: Run Postman
          image: alpine:3.15
          script:
            - echo "This runs"
          after-script:
            - echo "This also runs" 

This seems like a pipeline bug to me. Any ideas what might be causing this?

Mohammad Syahrul

Hey @Konstantinos 

Welcome to the community!

I tested and verified that this issue is only reproducible on the alpine image and other docker image works fine.

Further investigation, I found out that this was caused by the command

add npm bash  

The root cause it's a little complex, but the simplified version is before we start the build, we will try to check if `/bin/bash` existed or not. If yes, we add a special redirection command in "~/.bashrc" to make the output redirect correctly.

However, because alpine does not have a `/bin/bash` build-in, we don't put that file in the image, and when the user installs bash in the build script, our after build script would find "/bin/bash" and execute after build script in bash context. It would miss the log because it doesn't have `~/.bashrc` in place, so it doesn't redirect properly.

There are two suggestion to fix it, which is:

• Don't install bash
• Use an image that already has bash installed.

I hope this helps. 

Cheers,
Syahrul