-
Notifications
You must be signed in to change notification settings - Fork 94
Expand file tree
/
Copy pathclients-cpp-python-ubuntu2404.yml
More file actions
262 lines (221 loc) · 9.98 KB
/
clients-cpp-python-ubuntu2404.yml
File metadata and controls
262 lines (221 loc) · 9.98 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
name: "Build C++ and Python Clients on Ubuntu 24.04"
on:
pull_request:
branches: [ 'main', 'rc/v*' ]
push:
branches: [ 'main', 'check/**', 'release/v*' ]
permissions:
packages: write
#===============================================================================
# Background: in this workflow there are three different kinds of caching going
# on:
#
# 1. The outputs are Github Build artifacts, attached to every action run.
# These artifacts can be downloaded from e.g.
# https://github.com/deephaven/deephaven-core/actions/runs/17416308139
# but the specific URL depends on the build.
# We use this to upload:
# - The C++ install directory
# - The .whl file for the static Python client
# - The .whl file for the ticking Python client
#
# 2. The C++ install directory is cached via actions/cache, and keyed
# by the hash of the cpp-client and proto directories. This allows us
# to skip recompilation if these files don't change. This is an optional
# optimization that might not be very significant.
#
# 3. Github Packages, which is a NuGet-compatible repo accessible from
# https://github.com/orgs/deephaven/packages?repo_name=deephaven-core
# and controlled via the NuGet API. We use this package repository to hold
# the binaries for the C++ dependencies e build (grpc, arrow, etc.). It is
# managed automatically for us by cmake/vcpkg/nuget. This optimization is
# important because building the C++ dependencies takes significant time
# (45 minutes maybe).
#===============================================================================
env:
GH_PACKAGES_USERNAME: ${{ github.repository_owner }}
GH_PACKAGES_FEED: https://nuget.pkg.github.com/${{ github.repository_owner }}/index.json
DHINSTALL: ${{ github.workspace }}/dhinstall
jobs:
#=============================================================================
# Identify version of Deephaven Core
#=============================================================================
version_job:
uses: ./.github/workflows/dhc-version.yml
#=============================================================================
# Build the C++ Client
#=============================================================================
cpp_job:
name: Build C++ client on Ubuntu or fetch from cache
runs-on: ubuntu-24.04
defaults:
run:
shell: bash
steps:
- name: Check out this repo
uses: actions/checkout@v6
# Try to fetch the whole installation directory (the final product of the
# build) from the Github Cache. The key to this cache is derived
# from the hash of the contents of the files in the cpp-client and proto
# directories. If this fetch is successful, we skip over all the build
# work and just copy this cached install directory to the output artifact
# for this run.
- name: Restore the cached installation directory, or prepare a new one
id: cache-cpp-install
uses: actions/cache@v5
with:
path: ${{ env.DHINSTALL }}
key: ${{ runner.os }}-cpp-client-${{ hashFiles('cpp-client/**', 'proto/**') }}
# [Note: skip this step if cache-cpp-install was successful]
# Check out vcpkg
- name: Check out vcpkg
id: checkout-vcpkg
if: steps.cache-cpp-install.outputs.cache-hit != 'true'
uses: actions/checkout@v6
with:
repository: microsoft/vcpkg
path: vcpkg
# [Note: skip this step if cache-cpp-install was successful]
# Bootstrap vcpkg
- name: Bootstrap vcpkg
if: steps.cache-cpp-install.outputs.cache-hit != 'true'
run: ${{ github.workspace }}/vcpkg/bootstrap-vcpkg.sh
# [Note: skip this step if cache-cpp-install was successful]
# Get mono so that we can run nuget. This is because the nuget.exe that
# ships with vcpkg is an old .NET Framework binary (Windows format), and
# only mono knows how to run such a thing on Linux. Some day the maintainers
# will fix this so it runs with the cross-platform "dotnet".
- name: Get mono so that we can run nuget
if: steps.cache-cpp-install.outputs.cache-hit != 'true'
run: sudo apt install mono-complete
# [Note: skip this step if cache-cpp-install was successful]
# Adapted from
# https://learn.microsoft.com/en-us/vcpkg/consume/binary-caching-github-packages?pivots=linux-runner
# [Note: skip this step if cache-cpp-install was successful]
- name: "Configure nuget to know how to download (or upload) each cached package that we need (or create)"
if: steps.cache-cpp-install.outputs.cache-hit != 'true'
run: |
vcpkg_exe=${{ github.workspace }}/vcpkg/vcpkg
nuget_dotnet=$($vcpkg_exe fetch nuget | tail -n 1)
mono $nuget_dotnet \
sources add \
-Source "${{ env.GH_PACKAGES_FEED }}" \
-StorePasswordInClearText \
-Name GitHubPackages \
-UserName "${{ env.GH_PACKAGES_USERNAME }}" \
-Password "${{ secrets.GITHUB_TOKEN }}"
mono $nuget_dotnet \
setapikey "${{ secrets.GITHUB_TOKEN }}" \
-Source "${{ env.GH_PACKAGES_FEED }}"
# [Note: skip this step if cache-cpp-install was successful]
# 1. Invoke vcpkg to:
# a) Try to fetch each of the dependent libraries from the nuget cache
# b) If not found, build them and insert them in the nuget cache
# 2. Configure cmake to prepare for the build/install step, which comes next
- name: build packages and configure cmake. Cached packages will be found, or stored in github's nuget repo
if: steps.cache-cpp-install.outputs.cache-hit != 'true'
env:
VCPKG_BINARY_SOURCES: "clear;nuget,${{ env.GH_PACKAGES_FEED }},readwrite"
run: cmake -S cpp-client/deephaven -B cpp-client/deephaven/build --toolchain ${{ github.workspace }}/vcpkg/scripts/buildsystems/vcpkg.cmake -DCMAKE_INSTALL_PREFIX=${{ env.DHINSTALL }} -DVCPKG_TARGET_TRIPLET=x64-linux-dynamic-release -DVCPKG_OVERLAY_TRIPLETS=cpp-client/deephaven/custom-triplets
# [Note: skip this step if cache-cpp-install was successful]
# Build our executables and install them in the configured install directory {{ env.DHINSTALL }}
- name: Run cmake build and install
if: steps.cache-cpp-install.outputs.cache-hit != 'true'
run: cmake --build cpp-client/deephaven/build --config RelWithDebInfo --target install --parallel
# Upload results as build artifact. Note: if cache-cpp-install was
# then none of the intervening steps were executed. In that case,
# this effectively just copies the cache to the build artifact.
- name: Upload install directory as build artifact
id: upload-install-directory
uses: actions/upload-artifact@v7
with:
name: cpp-client-install
path: ${{ env.DHINSTALL }}
#=============================================================================
# Build the Python Static Client
#=============================================================================
python_static_job:
name: Build Python static client on Ubuntu
runs-on: ubuntu-24.04
needs: [version_job]
defaults:
run:
shell: bash
steps:
- name: Check out this repo
uses: actions/checkout@v6
- name: Install Python
uses: actions/setup-python@v6
with:
python-version: '3.10'
- name: Install the 'wheel' package
run: pip3 install wheel
- name: Install requirements-dev.txt
run: |
cd ./py/client
pip3 install -r requirements-dev.txt
- name: Run setup.py
env:
DEEPHAVEN_VERSION: ${{ needs.version_job.outputs.dhc_version }}
run: |
cd ./py/client
python setup.py bdist_wheel
- name: Upload static .whl file as build artifact, to be used directly or by dependent clients like Python ticking
uses: actions/upload-artifact@v7
with:
name: py-static-wheel
path: ./py/client/dist/*.whl
#=============================================================================
# Build the Python Ticking Client
#=============================================================================
python_ticking_job:
name: Build Python ticking client on Ubuntu
runs-on: ubuntu-24.04
needs: [cpp_job, python_static_job, version_job]
defaults:
run:
shell: bash
steps:
- name: Check out this repo
uses: actions/checkout@v6
- name: Get the C++ installation as a build artifact
uses: actions/download-artifact@v8
with:
name: cpp-client-install
path: ${{ env.DHINSTALL }}
- name: Get the Python static installation as a build artifact
uses: actions/download-artifact@v8
with:
name: py-static-wheel
path: ./py/client/dist/
- name: Install Python
uses: actions/setup-python@v6
with:
python-version: '3.10'
- name: Install the 'wheel' and 'cython' packages
run: pip3 install wheel cython
- name: Install requirements-dev.txt
run: |
cd ./py/client
pip3 install -r requirements-dev.txt
- name: Install the static client
run: pip3 install --force --no-deps ./py/client/dist/*.whl
- name: Build cython code
env:
DEEPHAVEN_VERSION: ${{ needs.version_job.outputs.dhc_version }}
CPPFLAGS: -I${{ env.DHINSTALL }}/include
LDFLAGS: -L${{ env.DHINSTALL }}/lib
run: |
cd ./py/client-ticking
python setup.py build_ext -i
- name: Run setup.py
env:
DEEPHAVEN_VERSION: ${{ needs.version_job.outputs.dhc_version }}
run: |
cd ./py/client-ticking
python setup.py bdist_wheel
- name: Upload ticking .whl file as build artifact
uses: actions/upload-artifact@v7
with:
name: py-ticking-wheel
path: ./py/client-ticking/dist/*.whl