Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Creates another project to build wheel packages. Apache-beam created a beam-wheels repository for the sole purpose of building wheel packages.
  2. Introduces github actions to build wheel packages.
  3. Adds building wheel packages logic to current Azure CI of Flink

Props

Cons

Solution 1

We can learn from beam-wheels

1. Beam have already discussed about to change this solution to github actions as solution 2 

2. Need to create another repository

Solution 2

1.

Github

 Github actions comes with a strong level of integration with GitHub

2. We can build our wheel packages very simply by using many action tools,such as 

(actions/setup-java,

 actions/setup-python,

 actions/upload-artifact)

1. It introduces another build CI system of github actions which increases the burden of maintaining

2. Github action is still very young

Solution 3

The logic of building wheel package could be integrated into the current Azure CI directly

N/A

Solution 3 is preferred now as we already have built stable Azure CI in Flink and it is convenient to add the logic of building wheel packages to Azure CI.

...