atlassian

I started a bbrun without parameters and the fist default step was successful.
But then also another default step wich has deployment: staging & trigger: manual set.
This should be prevented!

attached you will find a test bitbucket-pipline.yml:

pipelines:
  default:
    - step:
        name: Build & Test
        script:
          - /bin/echo "Build & Test"
    - step:
        nam

Would be nice to add the get avatar API call to this project.

Instead of forcing auth via API in the configure script (https://github.com/opendevstack/ods-core/blob/master/sonarqube/configure.sh#L199-L205) we can do this in the container startup script: https://github.com/opendevstack/ods-core/blob/master/sonarqube/docker/run.sh.

FYI @felipecruz91

I have a weird issue with the crowd chart where setting the nfsPermissionFixer value to true (thus enabling the k8s job object) errors on the helm build as the job runs before the PVC is created. This keeps the job container in a pending state.

The event on the pending job pod is:

Warning FailedScheduling 9m13s default-scheduler persistentvolumeclaim "crowd-shared-home" not found