Page History

...

• Commands:
  • kubectl create configmap build-config --from-file=build-request.
    properties
  • kubectl describe configmaps build-config
  • kubectl create -f build-config.yml

todo:  Work on test project like test-ioc, with bom. claudio can use this to test

• we can make the lsit of components just have boost and epics for now
• Then we want to get to the point where a pod is executed and start_build.py can read the bom of the ioc

todo: Work on getting testing flow designed

• Unit tests firsts, the ones you can run right after the build
• may want a specific directory name that the container test script can run
• Come up with backend api for it, which just records to db i think, 
• We can assume basic/unit tests are automatically ran if a build is started

Flow:

1. User command CLI $ bs run build  which does the build flow.
   1. Pass to backend the component, branch, and user headers
   2. backend looks into component DB for the development image
   3. backend mounts /mnt  at /sdf/scratch/ad/ad-build/ for downloading src code
   4. backend mounts /build  at /sdf/groups/eed/ad/ad-build/ for the build scripts
   5. backend mounts configMap at /config/build_config.json for build request information
   6. starts the build container and calls start_build.py 
   7. start_build.py then performs a build and outputs its results at the top of repo directory
2. start_build.py  will then call start_test.py
3. start_test.py will then look into directories in the src code called /test/unit_tests/ and run those

Group meeting 6-6-24

Group Meeting 6-6-24 - LCLSControls - SLAC Confluence (stanford.edu)