matrixji commented on PR #7249:
URL:
https://github.com/apache/incubator-devlake/pull/7249#issuecomment-2029146478
I have the same requirement with #6000.
In our use of Jenkins, we use the parameter to specify which env to deploy,
e.g. devploy_env="prod" as Production deployment, while deploy_env="test" as
the QA deployment.
Currently in the DORA metrics process, while doing data transformation from
_ to _, it just uses Jenkins Jobs' name to decide which environment is used. So
my plan to support this requirement may be split into below steps:
- Collect the `parameters` into raw data
- Add parameters as string field into `JenkinsBuild`, this may rebuild kv
pairs as a string: k1=v1;k2=v2;k3=v3
- In the transformation step, besides deciding if this job is a production
env, also check the parameters(maybe matched with {name}~{parameters}):
- Right now, the job name needs to be set as Deploy_Foo_Service_Prod, we
use the pattern `.*_Prod` to match a production deployment.
- After this is done, we could use the job name Deploy_Foo_Service with
the parameter deploy_env=prod, we could set the pattern as `deploy_env=prod` to
match a production deployment.
I turned this PR as a draft, I'll try to provide the above 3 commits as a
whole PR to close #6000
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
