feat: add sonarqube bitbucket (#43)

* feat: add sonarqube bitbucket

* chore: change sonar projectKey

.gitignore

@@ -7,3 +7,5 @@ node_modules
 .step-functions-local
 .bak
 .idea
+.nyc_output
+/coverage

README.md

@@ -73,6 +73,12 @@ We support ASL for Step Functions. Make sure to install AWS Toolkit so you can r
 
 ##
 
+### SonarQube configuration
+
+Before deployment make sure to create a new SonarQube project. After that set proper repository variables (`SONAR_TOKEN` and `SONAR_HOST_URL`) and properties in `sonar-project.properties` file. 
+
+##
+
 ### Deploy
 
 The best choice for deployment is the bitbucket pipeline.

bitbucket-pipelines.yml

@@ -1,5 +1,7 @@
 image: node:20-alpine
 definitions:
+  caches:
+    sonar: /opt/sonar-scanner/.sonar
   steps:
     - step: &compile
         name: Compile
@@ -8,7 +10,9 @@ definitions:
         script:
           - npm ci
           - npm run lint
-          # - npm run test
+          - npm run test-coverage
+        artifacts:
+          - coverage/**
     - step: &deploy
         name: Deploy
         trigger: manual
@@ -18,10 +22,18 @@ definitions:
           - npm install
           - ./node_modules/.bin/serverless config credentials --provider aws --key ${AWS_LAMBDA_KEY} --secret ${AWS_LAMBDA_SECRET}
           - ./node_modules/.bin/serverless deploy --stage ${STAGE}
+    - step: &sonarqube-analysis
+        name: SonarQube analysis
+        image: sonarsource/sonar-scanner-cli:latest
+        caches:
+          - sonar
+        script:
+          - sonar-scanner
 
 pipelines:
   default:
     - step: *compile
+    - step: *sonarqube-analysis
   custom:
     deploy-to-dev:
       - step: *compile