search

guibranco / VTEX-SDK-dotnet

🛒 ⚙️ VTEX platform .NET SDK
https://guibranco.github.io/VTEX-SDK-dotnet/
MIT License
12 stars 7 forks source link

Update appveyor.yml #373

Closed guibranco closed 1 week ago

guibranco commented 1 week ago

Closes #

📑 Description

✅ Checks

☢️ Does this introduce a breaking change?

ℹ Additional Information

Summary by CodeRabbit

coderabbitai[bot] commented 1 week ago

Walkthrough

The changes in this pull request focus on restructuring the appveyor.yml file to enhance clarity and organization of the build configuration. Key modifications include the adoption of list formats for various sections, updates to paths and commands for coverage reporting, and the addition of commands for generating and uploading artifacts. The build section is disabled, and the deploy section has been reformatted while maintaining the existing deployment logic.

Changes

File Change Summary
appveyor.yml - Restructured init, before_build, and deploy sections to list format for clarity.
- Disabled build section with build: off.
- Updated build_script with new parameters for SonarScanner and modified coverage report paths.
- Added logger for JUnit output in test execution command and included upload of test results to AppVeyor.
- Expanded after_build section for generating and pushing artifacts, including nupkg and snupkg files.
- Enhanced coverage artifact generation with commands for zipping and pushing results.

Possibly related PRs

Suggested labels

enhancement, size/M, Review effort [1-5]: 2

Suggested reviewers

🐰 In the meadow, changes bloom,
A YAML file finds more room.
With lists and paths, it’s clear and bright,
Artifacts ready, all in sight!
A hop, a skip, let’s build with glee,
For every change, there’s joy, you see! 🌼

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share - [X](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai) - [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai) - [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai) - [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code)
🪧 Tips ### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit , please review it.` - `Generate unit testing code for this file.` - `Open a follow-up GitHub issue for this discussion.` - Files and specific lines of code (under the "Files changed" tab): Tag `@coderabbitai` in a new review comment at the desired location with your query. Examples: - `@coderabbitai generate unit testing code for this file.` - `@coderabbitai modularize this function.` - PR comments: Tag `@coderabbitai` in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples: - `@coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.` - `@coderabbitai read src/utils.ts and generate unit testing code.` - `@coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.` - `@coderabbitai help me debug CodeRabbit configuration file.` Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. ### CodeRabbit Commands (Invoked using PR comments) - `@coderabbitai pause` to pause the reviews on a PR. - `@coderabbitai resume` to resume the paused reviews. - `@coderabbitai review` to trigger an incremental review. This is useful when automatic reviews are disabled for the repository. - `@coderabbitai full review` to do a full review from scratch and review all the files again. - `@coderabbitai summary` to regenerate the summary of the PR. - `@coderabbitai resolve` resolve all the CodeRabbit review comments. - `@coderabbitai configuration` to show the current CodeRabbit configuration for the repository. - `@coderabbitai help` to get help. ### Other keywords and placeholders - Add `@coderabbitai ignore` anywhere in the PR description to prevent this PR from being reviewed. - Add `@coderabbitai summary` to generate the high-level summary at a specific location in the PR description. - Add `@coderabbitai` anywhere in the PR title to generate the title automatically. ### CodeRabbit Configuration File (`.coderabbit.yaml`) - You can programmatically configure CodeRabbit by adding a `.coderabbit.yaml` file to the root of your repository. - Please see the [configuration documentation](https://docs.coderabbit.ai/guides/configure-coderabbit) for more information. - If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: `# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json` ### Documentation and Community - Visit our [Documentation](https://coderabbit.ai/docs) for detailed information on how to use CodeRabbit. - Join our [Discord Community](http://discord.gg/coderabbit) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.
AppVeyorBot commented 1 week ago

:x: Build VTEX-SDK-dotnet 2.3.1687 failed (commit https://github.com/guibranco/VTEX-SDK-dotnet/commit/e9205e43d3 by @gstraccini[bot])

guibranco commented 1 week ago

@gstraccini appveyor build pr

guibranco commented 1 week ago

@gstraccini appveyor build commit

gstraccini[bot] commented 1 week ago

I'm sorry @guibranco, I can't do that. Invalid parameter. :pleading_face:

guibranco commented 1 week ago

@gstraccini appveyor build pull request

gstraccini[bot] commented 1 week ago

AppVeyor build (commit) started! :rocket:

Build ID: 50978504 Version: 2.4.0

gstraccini[bot] commented 1 week ago

AppVeyor build (pull request) started! :rocket:

Build ID: 50978506 Version: 2.4.1

codacy-production[bot] commented 1 week ago

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation Diff coverage
Report missing for 699ae9f31029ed28305871a1b76ba416962bae6c[^1] :white_check_mark: ∅
Coverage variation details | | Coverable lines | Covered lines | Coverage | | ------------- | ------------- | ------------- | ------------- | | Common ancestor commit (699ae9f31029ed28305871a1b76ba416962bae6c) | Report Missing | Report Missing | Report Missing | | | Head commit (b86e5e64df27d8a89fb899e9188770e40ee24bd4) | 1777 | 4 | 0.23% | **Coverage variation** is the difference between the coverage for the head and common ancestor commits of the pull request branch: ` - `
Diff coverage details | | Coverable lines | Covered lines | Diff coverage | | ------------- | ------------- | ------------- | ------------- | | Pull request (#373) | 0 | 0 | **∅ (not applicable)** | **Diff coverage** is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: `/ * 100%`

See your quality gate settings    Change summary preferences

Codacy stopped sending the deprecated coverage status on June 5th, 2024. Learn more [^1]: Codacy didn't receive coverage data for the commit, or there was an error processing the received data. Check your integration for errors and validate that your coverage setup is correct.

AppVeyorBot commented 1 week ago

:x: Build VTEX-SDK-dotnet 2.4.1 failed (commit https://github.com/guibranco/VTEX-SDK-dotnet/commit/f39cd63186 by @guibranco)

github-actions[bot] commented 1 week ago

Infisical secrets check: ✅ No secrets leaked!

💻 Scan logs ```txt 2:27PM INF scanning for exposed secrets... 2:27PM INF 576 commits scanned. 2:27PM INF scan completed in 302ms 2:27PM INF no leaks found ```
sonarcloud[bot] commented 1 week ago

Quality Gate Passed 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

AppVeyorBot commented 1 week ago

:white_check_mark: Build VTEX-SDK-dotnet 2.4.3 completed (commit https://github.com/guibranco/VTEX-SDK-dotnet/commit/ca7c55d08d by @guibranco)

codecov[bot] commented 1 week ago

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 0.22%. Comparing base (1f2e144) to head (b86e5e6). Report is 13 commits behind head on main.

Additional details and impacted files ```diff @@ Coverage Diff @@ ## main #373 +/- ## ======================================== - Coverage 0.22% 0.22% -0.01% ======================================== Files 117 117 Lines 1774 1777 +3 Branches 75 75 ======================================== Hits 4 4 - Misses 1770 1771 +1 - Partials 0 2 +2 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.