Needs to fix "test-only" runs

According to a conda developer (https://github.com/conda/conda-build/issues/3172#event-1887558612), our current way to run test-only package builds is going to get deprecated soon. We need to port our CI to the new expected behaviour.

@andre.anjos you da one implemented this. It's used only in bob.nightlies and beat packages (which have docker step).

assigned to @andre.anjos and unassigned @amohammadi

This is implemented here https://gitlab.idiap.ch/bob/bob.admin/blob/master/gitlab/build.sh#L20, so generically for all packages. Furthermore, I'm not sure I understand the comment from Mike in that thread. This new behaviour is not documented.

assigned to @amohammadi and unassigned @andre.anjos

$ conda build --help

  -t, --test            Test package (assumes package is already built).
                        RECIPE_DIR argument can be either recipe directory, in
                        which case source download may be necessary to resolve
                        package version, or path to built package .tar.bz2
                        file, in which case no source is necessary.

He was talking about this: path to built package .tar.bz2 file

We currently upload the built package like this:

<cmd> ${CONDA_ROOT}/conda-bld/${os}/${CI_PROJECT_NAME}*.tar.bz2

I think we'd need to base a new test rule on this recipe, possibly limiting by python version (with some variant of ${PYTHON_VERSION}). Do I understand correctly that, since the package is built, its recipe is fully resolved and no need to further configuration is required?

I think we'd need to base a new test rule on this recipe, possibly limiting by python version (with some variant of ${PYTHON_VERSION}).

Why? It's fine to upload everything. We might build multiple versions in each build.

Do I understand correctly that, since the package is built, its recipe is fully resolved and no need to further configuration is required?

Yes most probably.

@andre.anjos as far as I understand you have to run something like this:

$ conda build -m ../bob.admin/gitlab/conda_build_config.yaml --output conda

which will output something like: .../bob.extension-0.0.1-py36hb288b9d_0.tar.bz2

then, you find this tarball (from artifacts folder or in our channel).

Then, you run conda build --test /path/to/bob.extension-0.0.1-py36hb288b9d_0.tar.bz2

mentioned in issue beat/beat.cmdline#48 (closed)

I guess we also need to check the channel to see if the package was already built/uploaded. In such case, it won't be present locally and needs to be downloaded for tests (this would be used in the nightlies). I wonder if conda build <tarball> would accept an URL instead of a local path.

closed via commit 6f7695b4

I pushed my take on this. Let's see if it works tonite.

mentioned in commit da984a1a

mentioned in issue #102 (moved)

mentioned in merge request beat/beat.cmdline!53 (merged)

mentioned in merge request beat/beat.core!37 (merged)

mentioned in merge request beat/beat.editor!25 (merged)

mentioned in issue bob.devtools#5 (closed)