Skip to content

chore(pipeline): persist dist for all cc folders #360

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

Merged
merged 1 commit into from
Jan 17, 2025

Conversation

mkesavan13
Copy link
Contributor

@mkesavan13 mkesavan13 commented Jan 17, 2025

Closes Adhoc

This PR addresses

  • The new and upcoming widgets not being published issue

by making the following changes

  • Updating the pipeline with appropriate persistence path

Summary by CodeRabbit

  • Chores
    • Updated CircleCI configuration to use a more flexible wildcard pattern for persisting workspace artifacts in the contact center packages.

Copy link

coderabbitai bot commented Jan 17, 2025

Walkthrough

The pull request modifies the CircleCI configuration file to use a wildcard pattern for persisting build artifacts from the contact-center packages. Instead of explicitly listing individual package distribution directories, the configuration now uses a more flexible approach that automatically captures all dist directories under the contact-center package, simplifying future package additions and reducing configuration maintenance.

Changes

File Change Summary
.circleci/config.yml Replaced specific dist directory paths with wildcard pattern packages/contact-center/*/dist

Poem

🐰 In CircleCI's realm of build and test,
A wildcard path now does its best
To catch each dist with gentle care
No more manual paths to declare
Flexibility hops with rabbit's zest! 🚀


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
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, 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 generate docstrings to generate docstrings for this PR. (Beta)
  • @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 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 for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@mkesavan13
Copy link
Contributor Author

@coderabbitai review

Copy link

coderabbitai bot commented Jan 17, 2025

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (1)
.circleci/config.yml (1)

68-69: LGTM! The change improves maintainability.

The modification to use a wildcard pattern packages/contact-center/*/dist is a good improvement because:

  1. It automatically includes all contact-center package dist folders
  2. Reduces configuration maintenance when adding new packages
  3. Keeps the configuration DRY

Consider documenting this pattern in the repository's README or contributing guidelines to ensure future contributors understand the automatic inclusion of new contact-center packages.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1f67485 and ce4af83.

📒 Files selected for processing (1)
  • .circleci/config.yml (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: setup_test_release
🔇 Additional comments (1)
.circleci/config.yml (1)

68-69: Verify CircleCI wildcard pattern support.

The wildcard pattern packages/contact-center/*/dist is more maintainable than listing individual paths. However, let's verify that CircleCI supports this pattern for workspace persistence.

✅ Verification successful

CircleCI wildcard patterns are correct and supported ✓

The patterns correctly match all buildable packages:

  • packages/contact-center/*/dist covers all 5 contact-center subpackages
  • packages/@webex/widgets/dist correctly targets the webex widgets package
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the existence of contact-center packages with dist folders
# and ensure we're not missing any in the new pattern

# Find all contact-center packages with dist folders
echo "Contact center packages with dist folders:"
fd --type d --glob 'packages/contact-center/*/dist'

# List package.json files to verify build configurations
echo -e "\nVerifying build configurations in package.json files:"
fd --type f --glob 'packages/contact-center/*/package.json' --exec cat {} \; | grep -A 5 '"build":'

Length of output: 376


Script:

#!/bin/bash
# Check the actual directory structure
echo "Directory structure under packages:"
fd --max-depth 2 . packages/

echo -e "\nAll package.json files under packages:"
fd package.json packages/

echo -e "\nAll dist directories under packages:"
fd --type d dist packages/

Length of output: 895

@mkesavan13 mkesavan13 merged commit 6d61796 into webex:ccwidgets Jan 17, 2025
2 checks passed
@sreenara
Copy link
Contributor

🎉 This PR is included in version 1.28.0-ccwidgets.10 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

@sreenara
Copy link
Contributor

sreenara commented Feb 5, 2025

🎉 This PR is included in version 1.28.0-ccconnectors.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

@mkesavan13 mkesavan13 deleted the publish-issue branch February 5, 2025 12:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants