Skip to content

CI: test binder startup #159

@bsipocz

Description

@bsipocz
Member

At another, much smaller traffic, project I run into the issue that the binder deployment stopped working without CI noticing.
Would be nice to work out a CI job that checks on that all the deployment options (binder, colab, or anything else we enable) works as expected (that case it was due to version incompatibilities),

Activity

added
enhancementNew feature or request
infrastructureIssues relevant to infrasructure, rather than content
on Dec 7, 2022
soma2000-lang

soma2000-lang commented on Jan 20, 2023

@soma2000-lang

@bsipocz working on this one.

bsipocz

bsipocz commented on Jun 18, 2024

@bsipocz
MemberAuthor

I would advocate for dropping the env file in favour of reusing the requirements files for the deployments, after all we already test those and duplicating listing dependencies just creates more opportunities for failures.

bsipocz

bsipocz commented on Jun 18, 2024

@bsipocz
MemberAuthor

(that being said, environment.yml is being tested in a job, so it apparently not adequate for picking up issues with the deployment, see #216 )

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestinfrastructureIssues relevant to infrasructure, rather than content

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @bsipocz@soma2000-lang

        Issue actions

          CI: test binder startup · Issue #159 · numpy/numpy-tutorials