CRAB CI/CD flow with Jenkins
- Each release created in CRABServer repository triggers Jenkins job that builds RPMs for crabserver and crabtaskworker.
- In
masterbranch agreed naming convention for tagging new releases should follow this logic:v3.YYMMDD. Note: dash is not allowed in branch or tag name as RPM build will fail. - Built RPMs are stored in
comp.crab_[branch]repository every time overwriting old RPMs files.[branch]stands for the branch name which was used to create new release, e.g.comp.crab_master.
- If RPMs build job was successful, Jenkins job that builds Docker images is triggered.
- Built images are stored in
cmssw/[crabserver|crabtaskworker]Docker Hub repository while crabserver is also stored in CERN Registry. - After build is done, email notification is sent confirming that overall build process is done with indication whether build failed or succeeded. Log file is attached to the email for investigation.
- crabserver can be deployed to given environment by entering needed parameters in this Jenkins job.
- Two parameters should be provided before starting the build job:
CRABServer_imageandREST_Instance. CRABServer_imagerequires to enter image tag that should be deployed.REST_Instancerequires to enterk8shost name where provided tag should be deployed. Default value points tocmsweb-test2.cern.ch.- After deployment of crabserver is done, email notification is sent confirming that deployment process is done with indication whether it failed or succeeded. Log file is attached to the email for investigation.
- TaskWorker/Publisher can be deployed to given environment by entering needed parameters in this Jenkins job.
- Three parameters should be provided before starting the build job:
Service,ImageandEnvironment. Servicerequires to select which service should be deployed: TaskWorker or Publisher.Imagerequires to enter image tag that should be deployed.Environmentrequires to enter host name where provided tag should be deployed. Default value points tocrab-dev-tw01.- After deployment of TaskWorker/Publisher is done, email notification is sent confirming that deployment process is done with indication whether it failed or succeeded. Log file is attached to the email for investigation.
- One can start running testing suits in this Jenkins job.
- 3 kinds of testings can be started:
Client_Validation_Suite,Task_Submission_Status_TrackingandClient_Configuration_Validation. - Different kinds of testings and needed to provide parameters are explained in Jenkins jobs description.
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent