Anniina - draft a CI/CD workflow for POET

[katilp]

(POET : PhysObjectExtractorTool 😉 )

Design a CI/CD workflow for https://github.com/cms-legacydata-analyses/PhysObjectExtractorTool

As a first step, just implement something similar to https://github.com/cms-opendata-analyses/AOD2NanoAODOutreachTool/blob/master/.github/workflows/main.yml but following the steps in https://github.com/cms-legacydata-analyses/PhysObjectExtractorTool

There are some changes needed compared to AOD2NanoAODOutreachTool workflow example :

1. It should use the image from gitlab-registry.cern.ch/cms-cloud/cmssw-docker/cmssw_5_3_32-slc6_amd64_gcc472:2020-07-30-b26f0eeb instead of cmsopendata/cmssw_5_3_32 (although they are the same so it does not change the functionality)

2. To have a proper CI/CD workflow testing the actual code that has been pushed to the repository, it needs to be done differently from what is done in the AOD2NanoAOD example

   • There the commands are passed to the container with a script commands.sh and the area is cloned in the container: https://github.com/cms-opendata-analyses/AOD2NanoAODOutreachTool/blob/master/commands.sh#L10. That clone takes the version of the repository without the updates in the push.
   • Instead of doing the clone in the container, use the code which is available through the GihHub action in the mounted area /mnt/vol of the container. Create a PhysObjectExtractorTooldirectory and copy the code from /mnt/vol to there. Note that the CMSSW is already available in the container so step 2 in https://github.com/cms-legacydata-analyses/PhysObjectExtractorTool is not necessary in the workflow.

3. We will use the condition data server that is available without the special settings in step 6 in the instructions and this line in the code. To comment that line in the code, you can use something similar to https://github.com/cms-opendata-analyses/HiForestProducerTool/blob/2011/commands.sh#L20