dosubot[bot] commented on issue #7563:
URL: 
https://github.com/apache/incubator-devlake/issues/7563#issuecomment-2146637555

   <!-- Answer -->
   The CircleCI regex configuration in DevLake might not be working correctly 
because the regular expressions provided in the `deploymentPattern` and 
`productionPattern` fields might not match any of the CircleCI workflow or job 
names.
   
   Ensure that the regular expressions you are using in the `deploymentPattern` 
and `productionPattern` fields accurately match the names of your CircleCI 
workflows or jobs. For example:
   
   ```tsx
   <Input
     style={{ width: 200, margin: '0 8px' }}
     placeholder="(deploy|push-image)"
     value={transformation.deploymentPattern ?? ''}
     onChange={(e) =>
       onChangeTransformation({
         ...transformation,
         deploymentPattern: e.target.value,
         productionPattern: !e.target.value ? '' : 
transformation.productionPattern,
       })
     }
   />
   ```
   
   If the names of your workflows or jobs do not match the regex 
`(deploy|push-image)`, then no data will be collected. Similarly, ensure that 
the `productionPattern` is also correctly set to match the intended production 
deployments:
   
   ```tsx
   <Input
     style={{ width: 200, margin: '0 8px' }}
     placeholder="prod(.*)"
     value={transformation.productionPattern ?? ''}
     onChange={(e) =>
       onChangeTransformation({
         ...transformation,
         productionPattern: e.target.value,
       })
     }
   />
   ```
   
   Double-check the actual names of your CircleCI workflows and jobs and adjust 
the regex patterns accordingly 
<sup>[[1]](https://github.com/apache/incubator-devlake/blob/main/config-ui/src/plugins/register/circleci/transformation.tsx)</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

Reply via email to