Skip to content

Commit

Permalink
Merge pull request #109 from samansmink/add-new-templates-to-ci
Browse files Browse the repository at this point in the history
add new templates to CI
  • Loading branch information
samansmink authored Nov 15, 2024
2 parents 83c4013 + 902ed05 commit 512b17d
Show file tree
Hide file tree
Showing 2 changed files with 27 additions and 1 deletion.
26 changes: 26 additions & 0 deletions .github/workflows/TestCITools.yml
Original file line number Diff line number Diff line change
Expand Up @@ -24,6 +24,32 @@ jobs:
ci_tools_version: ${{ github.sha }}
extra_toolchains: 'parser_tools;fortran;omp;go;python3'

extension-template-capi:
name: Extension template (C API)
uses: ./.github/workflows/_extension_distribution.yml
with:
extension_name: capi_quack
override_repository: duckdb/extension-template-c
override_ref: main
duckdb_version: v1.1.3
override_ci_tools_repository: ${{ github.repository }}
ci_tools_version: ${{ github.sha }}
extra_toolchains: 'parser_tools;fortran;omp;go;python3'
exclude_archs: 'wasm_mvp;wasm_eh;wasm_threads' # TODO: remove once fixed upstream

extension-template-rust:
name: Extension template (Rust)
uses: ./.github/workflows/_extension_distribution.yml
with:
extension_name: rusty_quack
override_repository: duckdb/extension-template-rs
override_ref: main
duckdb_version: v1.1.3
override_ci_tools_repository: ${{ github.repository }}
ci_tools_version: ${{ github.sha }}
extra_toolchains: 'parser_tools;fortran;omp;go;rust;python3'
exclude_archs: 'windows_amd64_rtools;windows_amd64_mingw;wasm_threads' # TODO: remove once fixed upstream

delta-extension-main:
name: Rust builds (using Delta extension)
uses: ./.github/workflows/_extension_distribution.yml
Expand Down
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,4 +18,4 @@ DuckDB's [Extension Template](https://github.com/duckdb/extension-template/actio
| v0.10.0 | v0.10.0 | no |

Each branch in this repository targets a specific version of DuckDB. Note that these branches will be continually updated to ensure the build environment is functional for that version of DuckDB.
Also note that at some point, support for versions will be dropped. Currently, we aim to support the latest 2 DuckDB versions, to allow extensions devs to transition to a new DuckDB version.
Also note that at some point, support for versions will be dropped. Currently, we aim to support the latest 2 DuckDB versions, to allow extensions devs to transition to a new DuckDB version.

0 comments on commit 512b17d

Please sign in to comment.