Build Artefact Diet Plan?
We're experimenting with Docker and deploying in images build artefacts created from Visual COBOL 5.0 for Eclipse for Windows. We're using Git/Bitbucket for source code management and Nexus Pro to store build artefacts. We use Bamboo for build and deploy. I noticed some build outputs that we are including in Docker and storing in Nexus and wonder if they truly need to be deployed. I would appreciate reading your opinions regarding the following file types:
- .lst file - who looks at listing these days?
- .obj - if we always produce dlls/exes in our build, do we need to deploy obj files?
- .idy - nice to have, but with 2000+ COBOL programs, an expensive luxury? If we have all the branch source stored safely in Git, is it better to create debug files on demand as needed?
- obj.1.tlog - what is a tlog file and why do I care?
lst files: Personally I wouldn't have thought you would need these on a Docker image.
obj files: you would only need these if the Docker image ever needs to rebuild executables so probably not.
idy files: If you ever need to debug code running on the Docker image you would need these.
tlog files. These are used by the build system to track dependencies so unless the image ever builds a project they would not be required.
I hope that helps.