-
-
Notifications
You must be signed in to change notification settings - Fork 480
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
Automatically build binder configuration #24842
Comments
screenshot |
comment:1
Attachment: binder.png |
Branch: u/saraedum/binder |
Commit: |
comment:4
I could definitely add support for this in the Trac plugin as well, easy peasy. |
Branch pushed to git repo; I updated commit sha1. Last 10 new commits:
|
comment:6
For this to really make sense we would have to synchronize trac's Git repository to gitlab, say to something like a |
Work Issues: use ssh keys through https://circleci.com/docs/2.0/configuration-reference/#add_ssh_keys |
Changed commit from |
Changed branch from u/saraedum/binder to none |
Branch: u/saraedum/24842 |
Commit: |
Last 10 new commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
Changed work issues from use ssh keys through https://circleci.com/docs/2.0/configuration-reference/#add_ssh_keys to encode keys base64, support gitlab |
Branch pushed to git repo; I updated commit sha1. Last 10 new commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:18
For some reason I thought this was already done but apparently not. Are there any remaining challenges to this? Currently it lists #24854 as a dependency, but I don't know if that's strictly needed. The pipelines are already working for building; being able to launch the built containers in binder is immediately useful, because it also will allow us to run specific tests against each build manually. |
comment:19
Another idea I had is that if the build was for a merge request on gitlab, we can easily post a comment to the merge request with the link to run the built image on binder. |
comment:20
The branch for this currently has some merge conflict artifacts. |
Branch pushed to git repo; I updated commit sha1. Last 10 new commits:
|
Last 10 new commits:
|
Changed work issues from encode keys base64, support gitlab to encode keys base64, support gitlab, squash history once #24854 has ben merged |
comment:24
I am trying a simpler approach in #28457. |
This ticket proposes to add an automatic build for binder to the CI infrastructure from #24655.
Even though there is no support for this in trac yet, people could manually link to the generated binder configuration in their trac tickets. This would make it possible to try the proposed changes out without having to checkout and build the ticket.
If you want to try this out, you can go to the (automatically generated) commit in this github repository.
From personal experience, I see a number of reasons why this could be useful:
Depends on #24854
CC: @roed314 @embray @nthiery @xcaruso
Component: build
Keywords: CI, binder
Work Issues: encode keys base64, support gitlab, squash history once #24854 has ben merged
Author: Julian Rüth
Branch/Commit: u/saraedum/24842 @
9f84f0a
Issue created by migration from https://trac.sagemath.org/ticket/24842
The text was updated successfully, but these errors were encountered: