You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@devlake.apache.org by "The0Danktor (via GitHub)" <gi...@apache.org> on 2024/12/04 09:47:31 UTC
[I] [Bug][Jira] Can't link issues to commits [incubator-devlake]
The0Danktor opened a new issue, #8231:
URL: https://github.com/apache/incubator-devlake/issues/8231
### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/incubator-devlake/issues?q=is%3Aissue) and found no similar issues.
### What happened
i cant get any data on Failed deployment recovery time
im using a jira and bitbucket connection
in the jira cross-domain config im using the development panel configuration
but the links its fetching are as followed
https://bitbucket.org/{}/{657afclb-c407-4753-b02c-669584d660da}/commits/a9dc0392610064565a9155f3e0364f666eb8990f
### What do you expect to happen
i would except it to find a connection between issue and commit for recovery
### How to reproduce
jira and bitbucket connection
cross-domain with development panel configuration to bitbucket
the fetched links look like this
https://bitbucket.org/{}/{657afclb-c407-4753-b02c-669584d660da}/commits/a9dc0392610064565a9155f3e0364f666eb8990f
and the pattern that i use is
https://bitbucket.org/{namespace}/{repo_name}/commits/{commit_sha}
### Anything else
_No response_
### Version
v1.0.1
### Are you willing to submit PR?
- [ ] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@devlake.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Bug][Jira] Can't link issues to commits [incubator-devlake]
Posted by "The0Danktor (via GitHub)" <gi...@apache.org>.
The0Danktor commented on issue #8231:
URL: https://github.com/apache/incubator-devlake/issues/8231#issuecomment-2517819720
was not the origin of the problem for not getting metrics for recovery time
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@devlake.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Bug][Jira] Can't link issues to commits [incubator-devlake]
Posted by "The0Danktor (via GitHub)" <gi...@apache.org>.
The0Danktor commented on issue #8231:
URL: https://github.com/apache/incubator-devlake/issues/8231#issuecomment-2516832748
@dosu but its needs the repo_name and im not even sure if it uses the repo_uuid i dont see that anywhere in the documantation
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@devlake.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Bug][Jira] Can't link issues to commits [incubator-devlake]
Posted by "The0Danktor (via GitHub)" <gi...@apache.org>.
The0Danktor closed issue #8231: [Bug][Jira] Can't link issues to commits
URL: https://github.com/apache/incubator-devlake/issues/8231
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@devlake.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Bug][Jira] Can't link issues to commits [incubator-devlake]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
dosubot[bot] commented on issue #8231:
URL: https://github.com/apache/incubator-devlake/issues/8231#issuecomment-2516727072
<!-- Answer -->
The issue you're experiencing with linking Jira issues to Bitbucket commits might be due to the pattern mismatch in the URLs being fetched. The pattern you are using:
```
https://bitbucket.org/{namespace}/{repo_name}/commits/{commit_sha}
```
does not match the format of the links you provided:
```
https://bitbucket.org/{}/{657afclb-c407-4753-b02c-669584d660da}/commits/a9dc0392610064565a9155f3e0364f666eb8990f
```
It seems like the `{namespace}` and `{repo_name}` placeholders in your pattern do not align with the actual structure of the URLs being fetched. The URL you provided has a UUID-like structure in place of `{repo_name}`.
To resolve this, you may need to adjust your pattern to match the actual structure of the URLs. For example, if the UUID is consistent, you might need to modify your pattern to accommodate this format. Here's a potential adjustment:
```regexp
https://bitbucket.org/{namespace}/{repo_uuid}/commits/{commit_sha}
```
Ensure that your pattern correctly captures the components of the URL as they appear in the fetched links. This should help DevLake correctly parse and link the Jira issues with the Bitbucket commits.
<!-- Dosu Comment Footer -->
*To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@devlake.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Bug][Jira] Can't link issues to commits [incubator-devlake]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
dosubot[bot] commented on issue #8231:
URL: https://github.com/apache/incubator-devlake/issues/8231#issuecomment-2516839697
<!-- Answer -->
The documentation for DevLake does not explicitly mention using `repo_uuid` in place of `repo_name` for Bitbucket URLs. If the URLs being fetched contain a UUID-like structure, it might be specific to your Bitbucket setup or configuration.
To address this, you could try verifying if your Bitbucket instance uses UUIDs for repository identification. If it does, you might need to adjust your pattern accordingly. However, if `repo_name` is required, you may need to investigate further why the URLs are being fetched with UUIDs instead of names.
Unfortunately, without specific documentation on this, it might require some trial and error or checking with your Bitbucket configuration to ensure the correct pattern is used.
<!-- Dosu Comment Footer -->
*To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@devlake.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org