EPMDEDP-16625: docs: Update quick start guide with new pipeline

cspell.config.yaml

@@ -262,6 +262,7 @@ words:
   - SLSA
   - slsaprovenance
   - Snyk
+  - sonarcloud
   - sonarqube
   - sonarscanner
   - sonarsource

docs/quick-start/create-application.md

@@ -53,7 +53,7 @@ To create the first application, complete the instructions below:
 
     ![Application blank](../assets/quick-start/review-stage.png "Application blank")
 
-7. As soon as the codebase is created, navigate to it via the notification at the bottom left corner or click the **Components** section:
+7. As soon as the codebase is created, click the **Open Project** button:
 
     ![Marketplace notification](../assets/quick-start/success_notification.png "Marketplace notification")
 
@@ -96,38 +96,11 @@ Having created the Go application, proceed to build it by performing the followi
 
 6. Commit and push the `sonar-project.properties` changes to the main branch.
 
-7. Align the Tekton **Pipeline** with SonarCloud.
-
-    The `sonarqube-general` Task overwrites `sonar.projectKey` from the pipeline parameter `SONAR_PROJECT_KEY`. The build pipeline often sets `SONAR_PROJECT_KEY` to `$(params.CODEBASE_NAME)` only (for example `my-go-gin-app`). That value must match the **Project key** from SonarCloud **Project Information** (often `<organization-key>_my-go-gin-app`).
-
-    Navigate to **KubeRocketCI portal** -> **CI/CD Pipelines** -> **Pipelines**. Search the `github-go-gin-app-build-semver` Pipeline and click on its name. In the top-right corner of the screen, click **Actions** -> **Edit**. Find the task named `sonar` and set its parameters as follows.
-
-    Replace the `sonar` task parameter block (or the equivalent fragment) with:
-
-    ```yaml
-    - name: sonar
-      params:
-        - name: SONAR_PROJECT_KEY
-          value: "<organization-name>_my-go-gin-app"
-        - name: SONAR_PROJECT_NAME
-          value: $(params.CODEBASE_NAME)
-        - name: branch
-          value: $(params.git-source-revision)
-      runAfter:
-        - build
-      taskRef:
-        kind: Task
-        name: sonarqube-general
-      workspaces:
-        - name: source
-          subPath: source
-          workspace: shared-workspace
-    ```
-
-    Replace `"<organization-name>_my-go-gin-app"` with the **exact Project key** from SonarCloud (quotes keep YAML valid if the key contains characters such as `_`):
+7. (Optional) Select the SonarCloud-specific pipeline:
 
-        ![Sonar project properties](../assets/quick-start/edit-pipeline.png "Sonar project properties")
+  On the Project details page, select the **Branches tab**, click the actions button and select **Configure**:
 
+    ![Edit branch](../assets/quick-start/edit-main.png "Edit branch")
 
     :::note
       If this Pipeline is managed by Helm or Argo CD, apply the same change in the GitOps manifest or chart values so the cluster object is not reverted on sync.
@@ -137,39 +110,15 @@ Having created the Go application, proceed to build it by performing the followi
       If you use a self-hosted SonarQube instance instead of SonarCloud, follow [SonarQube integration](../operator-guide/code-quality/sonarqube.md); project key rules may differ.
     :::
 
-8. Update the `sonarqube-general` **Task** so the SonarCloud availability check does not treat HTTP **307** (redirect on the site root) as failure.
-
-    1. Navigate to **KubeRocketCI portal** -> **CI/CD Pipelines** -> **Tasks**. 
-    2. Search the `sonarqube-general` Task and click on its name. 
-    3. In the top-right corner of the screen, click **Actions** -> **Edit**. 
-    4. In the Tekton **Task** named `sonarqube-general`, open the step `prepare-project`.
-    5. Find the check that requests `${SONAR_HOST_URL}` with `curl` and **replace** the availability logic with a **GET** to `/api/system/status`, for example:
-
-    ```bash
-    SONAR_STATUS=$(curl -s -o /dev/null -w "%{http_code}" "${SONAR_HOST_URL}/api/system/status") || SONAR_STATUS="503"
-
-    if [[ "$SONAR_STATUS" != "200" ]]; then
-      echo -e "SonarQube is not available\nPlease check the connection to SonarQube"
-      exit 1
-    fi
-    ```
-
-    Remove or do not use a bare `HEAD`/`GET` against `${SONAR_HOST_URL}` alone without following redirects, as SonarCloud can respond with **307** and the step would exit incorrectly.
+  In the **Edit** window, select the **github-build-edp-sonarcloud** build Pipeline and click **Apply**:
 
-    ![Successful pipelinerun](../assets/quick-start/sonarqube_general_task.png "Successful pipelinerun")
+    ![Change build pipeline](../assets/quick-start/change-build-pipeline.png "Change build pipeline")
 
-
-    :::note
-      Cluster administrators usually patch this Task once per environment. If your platform already ships the `/api/system/status` check, you can skip this step.
-    :::
-
-9. Ensure **Automatic Analysis** is disabled for this project in SonarCloud when using CI scans (see [Integrate SonarQube](./integrate-sonarcloud.md)).
-
-10. In the Project details page, click **Build**:
+8. In the Project details page, click **Build**:
 
     ![Triggering pipeline run](../assets/quick-start/trigger_pipeline_run.png "Triggering pipeline run")
 
-11. Open the PipelineRun and wait until it finishes. Many small starter projects pass on the first run:
+9. Open the PipelineRun and wait until it finishes. Many small starter projects pass on the first run:
 
     ![Pipelinerun logs](../assets/quick-start/pipelinerun_status.png "Pipelinerun logs")
 
@@ -179,6 +128,10 @@ Having created the Go application, proceed to build it by performing the followi
       After the first analysis, SonarCloud may adjust Quality Gate behavior for the project. If the `sonar` task fails with **Quality Gate failed** even though the scan completed, address the reported issues or review the Quality Gate, then **re-run** the build pipeline. A second run is not always required.
     :::
 
+    If the pipeline failed, ensure **Automatic Analysis** is disabled for this project in SonarCloud when using CI scans (see [Integrate SonarQube](./integrate-sonarcloud.md)):
+
+      ![Analysis error](../assets/quick-start/analysis-error.png "Analysis error")
+
 Build pipelines in KubeRocketCI are specifically designed to generate an executable image of an application. Once the build process is complete, the resulting image can be deployed and run in a target environment.
 
 Now that you have successfully built an application, the next step is to create an environment for deployment. In order to deploy the application, you will need to install and integrate Argo CD. To learn how to install and integrate Argo CD, please refer to the [Integrate Argo CD](./integrate-argocd.md) page.

docs/quick-start/integrate-sonarcloud.md

@@ -67,7 +67,7 @@ To integrate SonarCloud with the platform, follow the steps below:
 
     Set the **Previous** version option and click **Create project**:
 
-    ![Add new project](../assets/quick-start/add_sonar_project2.png "Add new project")
+    ![Add new project](../assets/quick-start/previous-version.png "Add new project")
 
 6. On the project menu, navigate to **Branches** menu, select `master` branch and rename it to `main`. You can skip this step if the default branch is already `main`:
 

versioned_docs/version-3.13/quick-start/create-application.md

@@ -53,7 +53,7 @@ To create the first application, complete the instructions below:
 
     ![Application blank](../assets/quick-start/review-stage.png "Application blank")
 
-7. As soon as the codebase is created, navigate to it via the notification at the bottom left corner or click the **Components** section:
+7. As soon as the codebase is created, click the **Open Project** button:
 
     ![Marketplace notification](../assets/quick-start/success_notification.png "Marketplace notification")
 
@@ -96,38 +96,11 @@ Having created the Go application, proceed to build it by performing the followi
 
 6. Commit and push the `sonar-project.properties` changes to the main branch.
 
-7. Align the Tekton **Pipeline** with SonarCloud.
-
-    The `sonarqube-general` Task overwrites `sonar.projectKey` from the pipeline parameter `SONAR_PROJECT_KEY`. The build pipeline often sets `SONAR_PROJECT_KEY` to `$(params.CODEBASE_NAME)` only (for example `my-go-gin-app`). That value must match the **Project key** from SonarCloud **Project Information** (often `<organization-key>_my-go-gin-app`).
-
-    Navigate to **KubeRocketCI portal** -> **CI/CD Pipelines** -> **Pipelines**. Search the `github-go-gin-app-build-semver` Pipeline and click on its name. In the top-right corner of the screen, click **Actions** -> **Edit**. Find the task named `sonar` and set its parameters as follows.
-
-    Replace the `sonar` task parameter block (or the equivalent fragment) with:
-
-    ```yaml
-    - name: sonar
-      params:
-        - name: SONAR_PROJECT_KEY
-          value: "<organization-name>_my-go-gin-app"
-        - name: SONAR_PROJECT_NAME
-          value: $(params.CODEBASE_NAME)
-        - name: branch
-          value: $(params.git-source-revision)
-      runAfter:
-        - build
-      taskRef:
-        kind: Task
-        name: sonarqube-general
-      workspaces:
-        - name: source
-          subPath: source
-          workspace: shared-workspace
-    ```
-
-    Replace `"<organization-name>_my-go-gin-app"` with the **exact Project key** from SonarCloud (quotes keep YAML valid if the key contains characters such as `_`):
+7. (Optional) Select the SonarCloud-specific pipeline:
 
-        ![Sonar project properties](../assets/quick-start/edit-pipeline.png "Sonar project properties")
+  On the Project details page, select the **Branches tab**, click the actions button and select **Configure**:
 
+    ![Edit branch](../assets/quick-start/edit-main.png "Edit branch")
 
     :::note
       If this Pipeline is managed by Helm or Argo CD, apply the same change in the GitOps manifest or chart values so the cluster object is not reverted on sync.
@@ -137,39 +110,15 @@ Having created the Go application, proceed to build it by performing the followi
       If you use a self-hosted SonarQube instance instead of SonarCloud, follow [SonarQube integration](../operator-guide/code-quality/sonarqube.md); project key rules may differ.
     :::
 
-8. Update the `sonarqube-general` **Task** so the SonarCloud availability check does not treat HTTP **307** (redirect on the site root) as failure.
-
-    1. Navigate to **KubeRocketCI portal** -> **CI/CD Pipelines** -> **Tasks**. 
-    2. Search the `sonarqube-general` Task and click on its name. 
-    3. In the top-right corner of the screen, click **Actions** -> **Edit**. 
-    4. In the Tekton **Task** named `sonarqube-general`, open the step `prepare-project`.
-    5. Find the check that requests `${SONAR_HOST_URL}` with `curl` and **replace** the availability logic with a **GET** to `/api/system/status`, for example:
-
-    ```bash
-    SONAR_STATUS=$(curl -s -o /dev/null -w "%{http_code}" "${SONAR_HOST_URL}/api/system/status") || SONAR_STATUS="503"
-
-    if [[ "$SONAR_STATUS" != "200" ]]; then
-      echo -e "SonarQube is not available\nPlease check the connection to SonarQube"
-      exit 1
-    fi
-    ```
-
-    Remove or do not use a bare `HEAD`/`GET` against `${SONAR_HOST_URL}` alone without following redirects, as SonarCloud can respond with **307** and the step would exit incorrectly.
+  In the **Edit** window, select the **github-build-edp-sonarcloud** build Pipeline and click **Apply**:
 
-    ![Successful pipelinerun](../assets/quick-start/sonarqube_general_task.png "Successful pipelinerun")
+    ![Change build pipeline](../assets/quick-start/change-build-pipeline.png "Change build pipeline")
 
-
-    :::note
-      Cluster administrators usually patch this Task once per environment. If your platform already ships the `/api/system/status` check, you can skip this step.
-    :::
-
-9. Ensure **Automatic Analysis** is disabled for this project in SonarCloud when using CI scans (see [Integrate SonarQube](./integrate-sonarcloud.md)).
-
-10. In the Project details page, click **Build**:
+8. In the Project details page, click **Build**:
 
     ![Triggering pipeline run](../assets/quick-start/trigger_pipeline_run.png "Triggering pipeline run")
 
-11. Open the PipelineRun and wait until it finishes. Many small starter projects pass on the first run:
+9. Open the PipelineRun and wait until it finishes. Many small starter projects pass on the first run:
 
     ![Pipelinerun logs](../assets/quick-start/pipelinerun_status.png "Pipelinerun logs")
 
@@ -179,6 +128,10 @@ Having created the Go application, proceed to build it by performing the followi
       After the first analysis, SonarCloud may adjust Quality Gate behavior for the project. If the `sonar` task fails with **Quality Gate failed** even though the scan completed, address the reported issues or review the Quality Gate, then **re-run** the build pipeline. A second run is not always required.
     :::
 
+    If the pipeline failed, ensure **Automatic Analysis** is disabled for this project in SonarCloud when using CI scans (see [Integrate SonarQube](./integrate-sonarcloud.md)):
+
+      ![Analysis error](../assets/quick-start/analysis-error.png "Analysis error")
+
 Build pipelines in KubeRocketCI are specifically designed to generate an executable image of an application. Once the build process is complete, the resulting image can be deployed and run in a target environment.
 
 Now that you have successfully built an application, the next step is to create an environment for deployment. In order to deploy the application, you will need to install and integrate Argo CD. To learn how to install and integrate Argo CD, please refer to the [Integrate Argo CD](./integrate-argocd.md) page.

versioned_docs/version-3.13/quick-start/integrate-sonarcloud.md

@@ -67,7 +67,7 @@ To integrate SonarCloud with the platform, follow the steps below:
 
     Set the **Previous** version option and click **Create project**:
 
-    ![Add new project](../assets/quick-start/add_sonar_project2.png "Add new project")
+    ![Add new project](../assets/quick-start/previous-version.png "Add new project")
 
 6. On the project menu, navigate to **Branches** menu, select `master` branch and rename it to `main`. You can skip this step if the default branch is already `main`: