warren830 commented on code in PR #421: URL: https://github.com/apache/incubator-devlake-website/pull/421#discussion_r1096533020
########## docs/UserManuals/ConfigUI/Jenkins.md: ########## @@ -59,6 +59,14 @@ If you're using Jenkins builds to conduct `deployments`, please select "Detect D - Deployment: A Jenkins build with a name that matches the given regEx will be considered as a deployment. - Production: A Jenkins build with a name that matches the given regEx will be considered a build in the production environment. +There're two cases. If a Jenkins build has no stage, it's converted to both a cicd_task and a cicd_pipeline, +both have the same name as the Jenkins job's name. +If a Jenkins build has stages, it's converted to a cicd_pipeline and its +stages are converted to cicd_tasks in the domain layer. + + +The deployment and production regex is always applied to the records in the cicd_tasks table. + By the above two fields, DevLake can identify a production deployment among massive CI jobs. Review Comment: fixed ########## docs/UserManuals/ConfigUI/Jenkins.md: ########## @@ -59,6 +59,14 @@ If you're using Jenkins builds to conduct `deployments`, please select "Detect D - Deployment: A Jenkins build with a name that matches the given regEx will be considered as a deployment. - Production: A Jenkins build with a name that matches the given regEx will be considered a build in the production environment. +There're two cases. If a Jenkins build has no stage, it's converted to both a cicd_task and a cicd_pipeline, Review Comment: fixed -- 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]
