Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CI: test binder startup #159

Open
bsipocz opened this issue Dec 7, 2022 · 3 comments
Open

CI: test binder startup #159

bsipocz opened this issue Dec 7, 2022 · 3 comments
Labels
enhancement New feature or request infrastructure Issues relevant to infrasructure, rather than content

Comments

@bsipocz
Copy link
Member

bsipocz commented Dec 7, 2022

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),

@bsipocz bsipocz added enhancement New feature or request infrastructure Issues relevant to infrasructure, rather than content labels Dec 7, 2022
@soma2000-lang
Copy link

@bsipocz working on this one.

@bsipocz
Copy link
Member Author

bsipocz commented Jun 18, 2024

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
Copy link
Member Author

bsipocz commented Jun 18, 2024

(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
Labels
enhancement New feature or request infrastructure Issues relevant to infrasructure, rather than content
Projects
None yet
Development

No branches or pull requests

2 participants