-
Notifications
You must be signed in to change notification settings - Fork 504
Merge SonarQube v2 module into the existing scaffolder plugin with a new config-driven action, deprecate the legacy action, and add docs + tests for local SonarQube setups #6066
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
…creation and token generation capabilities - Introduced a new module for integrating SonarQube with Backstage scaffolder. - Added functionality to create SonarQube projects and generate tokens. - Included example configurations and templates for usage. - Implemented TypeScript support and Jest testing for the module. This commit establishes the foundation for SonarQube integration, enhancing the Backstage scaffolder's capabilities for DevOps workflows. Signed-off-by: Mirac Can Yilmaz <[email protected]>
…space support and configuration files - Added workspace configuration for the SonarQube module in package.json. - Introduced ESLint configuration files for code quality enforcement. - Created Docker Compose setup for local SonarQube instance. - Added catalog info and README documentation for module usage. - Implemented TypeScript configuration and example templates for project creation and CI/CD integration. This commit builds upon the initial SonarQube integration, providing a more comprehensive setup for developers using Backstage scaffolder. Signed-off-by: Mirac Can Yilmaz <[email protected]>
- Introduced changeset configuration file for versioning and changelog management. - Added README documentation for the changesets folder to assist developers in using the tool. - Created a changeset for fixing ESLint and TypeScript configurations, enhancing module resolution and ESM compatibility. These updates streamline the development process and improve code quality for the SonarQube module. Signed-off-by: Mirac Can Yilmaz <[email protected]>
- Deleted the ESLint configuration file from the SonarQube module as part of the cleanup process. - This change simplifies the module's setup and aligns with recent updates to the development workflow. No functional changes were made to the codebase. Signed-off-by: Mirac Can Yilmaz <[email protected]>
- Removed legacy SonarQube project creation action and replaced it with a new action that uses shared configuration. - Introduced `createConfiguredSonarQubeProjectAction` to streamline project creation without passing credentials in templates. - Updated README to reflect new action usage and configuration. - Added Docker Compose file for local SonarQube testing. - Implemented unit and live tests for the new action. - Enhanced SonarQube client with improved error handling and authorization. - Updated TypeScript definitions and configuration files to support changes.
Missing ChangesetsThe following package(s) are changed by this PR but do not have a changeset:
See CONTRIBUTING.md for more information about how to add changesets. Changed Packages
|
|
Thanks for the contribution! |
|
This issue was originally developed here , and after receiving some feedback, I made additional changes to the PR and pushed again. This PR is related to this issue: #2795 I struggled a bit while pushing code to my branch because ESLint threw an error that I couldn’t understand at first. If you notice anything, I can try to fix it. I appreciate your review and look forward to your feedback. Thank you. |
…r schema validation and adjust context handling
…ation capabilities
|
When I try to run this locally: I get the same error that also appears in one of the pipelines. Is there anything I should look into to fix this?” |
@miraccan00 - Open the API report locally and search for the warnings. It's usually a lot clearer on what to do than the feedback in CI. API reports usually fail due to missing or incorrect jsdocs for public facing exports. |
Is there anything I need to do? Thanks for the reply, I really appreciate you taking the time :) |
|
@AndrienkoAleksandr , could you please review my PR when you have a moment? |
Hey, I just made a Pull Request!
✔️ Checklist
Signed-off-byline in the message. (more info)