dosubot[bot] commented on issue #7601: URL: https://github.com/apache/incubator-devlake/issues/7601#issuecomment-2158633678
<!-- Answer --> To ensure that the Bitbucket Server data collection task in DevLake continues even if one pull request is corrupted, you can configure the Sync Policy to "Skip Failed Tasks." This setting allows the data collection process to skip over any failed tasks, preventing the entire pipeline from failing and ensuring that you do not lose all Bitbucket metrics for the repository. Here is the relevant section from the document: ```md ### Step 2.3 - Set the Sync Policy There are three settings for Sync Policy: - Data Time Range: You can select the time range of the data you wish to collect. The default is set to the past six months. - Sync Frequency: You can choose how often you would like to sync your data in this step by selecting a sync frequency option or enter a cron code to specify your preferred schedule. - Skip Failed Tasks: sometime a few tasks may fail in a long pipeline; you can choose to skip them to avoid spending more time in running the pipeline all over again. ``` Additionally, the `ConvertPullRequests` function in the `pr_convertor.go` file is designed to handle errors gracefully. The `api.NewDataConverter` method in the `ConvertPullRequests` function is set up to manage errors effectively, allowing the data collection process to continue even if some pull requests are not found or are corrupted. By enabling the "Skip Failed Tasks" option and leveraging the error handling in the `ConvertPullRequests` function, you can ensure that the data collection process continues even if some tasks fail <sup>[[1]](https://github.com/apache/incubator-devlake-website/blob/main/docs/Configuration/BitBucketServer.md)</sup><sup>[[2]](https://github.com/apache/incubator-devlake/blob/main/backend/plugins/bitbucket_server/tasks/pr_convertor.go)</sup>. <!-- 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-unsubscr...@devlake.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org