[Bug][CircleCI] CircleCI regex is not working to collect data
Search before asking
- [X] I had searched in the issues and found no similar issues.
What happened
When configuring the scope config the regex is not working
What do you expect to happen
It should collect data and show in DORA metrics.
How to reproduce
Go to - project - connections - scope config - transformations
No data collected when run.
Anything else
This is present since the installation.
Version
v0.21.0@ac4f7fe
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
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:
<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:
<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 [1].
To continue talking to Dosu, mention @dosu.
Hi, can you check if there is any records in the cicd_pipelines and cicd_deployments tables?
It seems to working fine on my local machine:
This issue has been automatically marked as stale because it has been inactive for 60 days. It will be closed in next 7 days if no further activity occurs.
This issue has been closed because it has been inactive for a long time. You can reopen it if you encounter the similar problem in the future.