Skip to content

Build multiple Python versions of all feedstocks in nightly CI conda builds

Description

This MR fixes #681 (closed) by modifying the conda builds in CI (.conda-build job template) to automagically replace a reference to a Python-version-specific CONDA_CONFIG with references to all of the Python-version-specific configurations matching the same prefix and suffix for nightly builds.

This means that for LALSimulation and LALApps, where the entire conda feedstock build runs over a single Python version, the lalxxx:conda CI job in a nightly build pipeline will actually run the whole conda build process N times, one for each Python version in the feedstock configuration.

The other subpackages build multiple versions of Python in a single conda build run, so their logic remains sort of the logical inverse: if not 'nightly' then specify --python to build just a single version, otherwise just build the thing.

API Changes and Justification

Backwards Compatible Changes

  • This change does not modify any class/function/struct/type definitions in a public C header file or any Python class/function definitions
  • This change adds new classes/functions/structs/types to a public C header file or Python module

Backwards Incompatible Changes

  • This change modifies an existing class/function/struct/type definition in a public C header file or Python module
  • This change removes an existing class/function/struct/type from a public C header file or Python module

If any of the Backwards Incompatible check boxes are ticked please provide a justification why this change is necessary and why it needs to be done in a backwards incompatible way.

Review Status

Please provide details on any reviews related to this change and and the associated reviewers.

Merge request reports

Loading