chore: integrate allure ci

[utsabc]

What are the changes introduced in this PR?

This PR introduces CI for allure-reports with transformer tests. We are storing these runs in a separate gh-pages branch hence the primary branches main or develop are not getting bloated.

We are storing the last 20 run history. The workflow also comments the specific report associated with the current run by checking out to the specific branch and getting latest run number.

What is the related Linear task?

Resolves INT-3018

Put down any required details on the broader aspect of your changes. If there are any dependent changes, mandatorily mention them here

Any changes to existing capabilities/behaviour, mention the reason & what are the changes ?

N/A

Any new dependencies introduced with this change?

N/A

Any new generic utility introduced or modified. Please explain the changes.

N/A

Any technical or performance related pointers to consider with the change?

N/A

@coderabbitai review

---

Developer checklist

• My code follows the style guidelines of this project

• No breaking changes are being introduced.

• All related docs linked with the PR?

• All changes manually tested?

• Any documentation changes needed with this change?

• Is the PR limited to 10 file changes?

• Is the PR limited to one linear task?

• Are relevant unit and component test-cases added in new readability format?

Reviewer checklist

• Is the type of change in the PR title appropriate as per the changes?

• Verified that there are no credentials or confidential data exposed with the changes.

[devops-github-rudderstack]

Test report for this run is available at: https://test-integrations-dev.s3.amazonaws.com/integrations-test-reports/rudder-transformer/3959/test-report.html

[devops-github-rudderstack]

Allure Test reports for this run are available at:

• Allure Report: https://github.com/rudderlabs/rudder-transformer/pages/branch/gh-pages/index.html

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 90.75%. Comparing base (9d6a002) to head (e52e0dd).
Report is 15 commits behind head on develop.

Additional details and impacted files

@@             Coverage Diff             @@
##           develop    #3959      +/-   ##
===========================================
+ Coverage    90.50%   90.75%   +0.25%     
===========================================
  Files          620      622       +2     
  Lines        32518    32516       -2     
  Branches      7710     7715       +5     
===========================================
+ Hits         29429    29511      +82     
+ Misses        2865     2781      -84     
  Partials       224      224              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[devops-github-rudderstack]

Allure Test reports for this run are available at:

• Allure Report: https://rudderlabs.github.io/rudder-transformer

[devops-github-rudderstack]

Allure Test reports for this run are available at:

• Allure Report: https://rudderlabs.github.io/rudder-transformer

[devops-github-rudderstack]

Allure Test reports for this run are available at:

• Allure Report: https://rudderlabs.github.io/rudder-transformer//index.html

[devops-github-rudderstack]

Allure Test reports for this run are available at:

• Allure Report: https://rudderlabs.github.io/rudder-transformer/5/index.html

[devops-github-rudderstack]

Allure Test reports for this run are available at:

• Allure Report: https://rudderlabs.github.io/rudder-transformer/6/index.html

[devops-github-rudderstack]

Allure Test reports for this run are available at:

• Allure Report: https://rudderlabs.github.io/rudder-transformer/7/index.html

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud