[CI] Unify all buidl.yml

[Devjiu]

We have 3 build.yml files:

• build.yml
• windows-build.yml
• build-docker.yml

Naming is inconsistent and any changes in common build pipeline requires changes in 3 files, what complicates maintenance.

Also it uses different scripts:

• omniscidb\scripts\conda\build.bat
• omniscidb/scripts/conda/build.sh

That simply wraps common: cmake -B build -S . $@ && cmake --build build --parallel $(nproc)

[alexbaden]

I don't think the build scripts will change that much, so unifying the shell and batch scripts seems more trouble than it's worth (unless there's something easy I am missing).

As far as separate build files, I recognize there is duplication, but there are also benefits to keeping the number of steps in the build clean. It can be confusing when you see steps about tests which are skipped because they are not relevant to the current job.

[Devjiu]

I don't think the build scripts will change that much, so unifying the shell and batch scripts seems more trouble than it's worth (unless there's something easy I am missing).

As far as separate build files, I recognize there is duplication, but there are also benefits to keeping the number of steps in the build clean. It can be confusing when you see steps about tests which are skipped because they are not relevant to the current job.

Main issue here is that build.sh/build.bat not used by developers, so it increases probability of works on my machine, fails in CI. I mean that cmake -B build -S . $@ && cmake --build build --parallel $(nproc) can be called directly in yml files.

There are 2 possible ways:

1. add compile defs inside of common build.py to unify dev workflow with CI workflow
2. use cmake build explicitly in CI workflow.

Currently we are using some mix of it and build.sh/build.bat are useless for developers and to reproduce you have to unwrap all those wrappers.

[Devjiu]

Also we already have steps, that are skipped during build.
For example:

[alexbaden]

Works on my machine fails in CI is very unlikely with simple cmake commands. I don't think the benefit is worth the tradeoff. The script does other things too -- sets up environment variables, etc.

As far as steps that are skipped during build, that is my point. They can be confusing, I don't want to add more :)