-
Notifications
You must be signed in to change notification settings - Fork 9
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
Running Variant Analysis Across Multiple Organizations with a Single Controller Repository #1055
Comments
Hi @BullHacks3.
Can you please elaborate on this? What issues are you seeing? Are there any error logs that you can share? |
Let's take an example: There are two different orgs: org 1 --> staging controller repository is present in org1 --> staging/controller I'm trying to run the variant analysis on a repo available in production org (i.e production/sample-mp).
ERROR: Repository not found for variant analysis Issue:
|
Thanks @BullHacks3 for the additional information. I've tried this locally and I can confirm I'm able to run a variant analysis that covers repos against different orgs. Both my repos were private. Can you confirm whether you're able to run variant analysis against those repos individually? I wonder if there is something special around your access to those repos. Also can you tell us about how you're logged in to the VS Code extension? |
👋 Folks,
Scenario:
We have several internal organizations (e.g., org1, org2, org3), and we want to run variant analysis across all different repositories within these organizations. However, we only want to maintain a single controller repository in org1. Currently, when attempting to do this, we are facing issues.
Request:
Is there a way to run variant analysis across different organizations (where the repositories are private) while having only one controller repository in org1?
The text was updated successfully, but these errors were encountered: