You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's more of a question rather than issue, but I wasn't able to find the answer anywhere, so I thought I might try here.
We have a couple of repositories which are a shared responsibility of many teams (Jira projects). For example, almost all teams contribute to our GraphQL repo. Now If I'd go and configure the circleci.yaml in a way that it reports the deployments I'd have to provide the service_id which, in our case, would be associated only with a single project (Team). I'm wondering if that means only this project will get the deployments, or will it actually map the Jira ticket ID from the PR/branch/commit and report to other projects as well?
Another case are the deployments of multiple features at once. Let's say a GitHub release contains multiple PRs coming from multiple teams. What would happen in that case? Deployment would be registered only in the configured Jira team, or in all team, or nowhere, because the prefix wasn't matching the configured team?
If that's not possible, could we potentially use multiple steps for each projects and somehow filter which one will be triggered?
The text was updated successfully, but these errors were encountered:
It's more of a question rather than issue, but I wasn't able to find the answer anywhere, so I thought I might try here.
We have a couple of repositories which are a shared responsibility of many teams (Jira projects). For example, almost all teams contribute to our GraphQL repo. Now If I'd go and configure the
circleci.yaml
in a way that it reports the deployments I'd have to provide theservice_id
which, in our case, would be associated only with a single project (Team). I'm wondering if that means only this project will get the deployments, or will it actually map the Jira ticket ID from the PR/branch/commit and report to other projects as well?Another case are the deployments of multiple features at once. Let's say a GitHub release contains multiple PRs coming from multiple teams. What would happen in that case? Deployment would be registered only in the configured Jira team, or in all team, or nowhere, because the prefix wasn't matching the configured team?
If that's not possible, could we potentially use multiple steps for each projects and somehow filter which one will be triggered?
The text was updated successfully, but these errors were encountered: