-
Notifications
You must be signed in to change notification settings - Fork 3
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
Take care of C# node dockerfiles #175
Comments
We need to digest 3.7.4 first, it already changes a lot. |
I'm in progress, this issue is for future development. |
AnnaShaleva
added a commit
that referenced
this issue
Apr 4, 2025
1. Remove Dockerfile.sharp.sources.from_binaries, this way of build is not relevant after all C# modules are moved to a single repo. 2. Rename Dockerfile.sharp.sources.from_local_dependencies to Dockerfile.sharp.sources, it's the only way to build C# node from sources. 3. Adjust sources build algorithm. 4. Adjust the related documentation. Close #148. A part of #175. Signed-off-by: Anna Shaleva <[email protected]>
AnnaShaleva
added a commit
that referenced
this issue
Apr 4, 2025
v3.8 of C# node is the first version that is going to have every module in a single release build. Right now the format of release assets is not known, hence Dockerfile.sharp is still out-of-date and will be updated as soon as we have v3.8.0 published. Ref. #175. Signed-off-by: Anna Shaleva <[email protected]>
AnnaShaleva
added a commit
that referenced
this issue
Apr 4, 2025
1. Remove Dockerfile.sharp.sources.from_binaries, this way of build is not relevant after all C# modules are moved to a single repo. 2. Rename Dockerfile.sharp.sources.from_local_dependencies to Dockerfile.sharp.sources, it's the only way to build C# node from sources. 3. Adjust sources build algorithm. 4. Adjust the related documentation. Close #148. A part of #175. Signed-off-by: Anna Shaleva <[email protected]>
AnnaShaleva
added a commit
that referenced
this issue
Apr 4, 2025
v3.8 of C# node is the first version that is going to have every module in a single release build. Right now the format of release assets is not known, hence Dockerfile.sharp is still out-of-date and will be updated as soon as we have v3.8.0 published. Ref. #175. Signed-off-by: Anna Shaleva <[email protected]>
AnnaShaleva
added a commit
that referenced
this issue
Apr 4, 2025
1. Remove Dockerfile.sharp.sources.from_binaries, this way of build is not relevant after all C# modules are moved to a single repo. 2. Rename Dockerfile.sharp.sources.from_local_dependencies to Dockerfile.sharp.sources, it's the only way to build C# node from sources. 3. Adjust sources build algorithm. 4. Adjust the related documentation. Close #148. A part of #175. Signed-off-by: Anna Shaleva <[email protected]>
AnnaShaleva
added a commit
that referenced
this issue
Apr 4, 2025
v3.8 of C# node is the first version that is going to have every module in a single release build. Right now the format of release assets is not known, hence Dockerfile.sharp is still out-of-date and will be updated as soon as we have v3.8.0 published. Ref. #175. Signed-off-by: Anna Shaleva <[email protected]>
AnnaShaleva
added a commit
that referenced
this issue
Apr 4, 2025
1. Remove Dockerfile.sharp.sources.from_binaries, this way of build is not relevant after all C# modules are moved to a single repo. 2. Rename Dockerfile.sharp.sources.from_local_dependencies to Dockerfile.sharp.sources, it's the only way to build C# node from sources. 3. Adjust sources build algorithm. 4. Adjust the related documentation. Close #148. A part of #175. Signed-off-by: Anna Shaleva <[email protected]>
AnnaShaleva
added a commit
that referenced
this issue
Apr 4, 2025
v3.8 of C# node is the first version that is going to have every module in a single release build. Right now the format of release assets is not known, hence Dockerfile.sharp is still out-of-date and will be updated as soon as we have v3.8.0 published. Ref. #175. Signed-off-by: Anna Shaleva <[email protected]>
AnnaShaleva
added a commit
that referenced
this issue
Apr 7, 2025
1. Remove Dockerfile.sharp.sources.from_binaries, this way of build is not relevant after all C# modules are moved to a single repo. 2. Rename Dockerfile.sharp.sources.from_local_dependencies to Dockerfile.sharp.sources, it's the only way to build C# node from sources. 3. Adjust sources build algorithm. 4. Adjust the related documentation. Close #148. A part of #175. Signed-off-by: Anna Shaleva <[email protected]>
AnnaShaleva
added a commit
that referenced
this issue
Apr 7, 2025
v3.8 of C# node is the first version that is going to have every module in a single release build. Right now the format of release assets is not known, hence Dockerfile.sharp is still out-of-date and will be updated as soon as we have v3.8.0 published. Ref. #175. Signed-off-by: Anna Shaleva <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
neo-project/neo-modules#912 is finally merged which means that https://github.com/neo-project/neo is a monorepo. We need to migrate from
Dockerfile.sharp.sources.from_binaries
andDockerfile.sharp.sources.from_local_dependencies
to a single Dockerfile that allows to build node from the specific revision from sources.We also need to update
Dockerfile.sharp
to be able to build released monorepo version.This issue is relevant for post-3.7.4 versions of Neo node. Depends on neo-project/neo#3232 and neo-project/neo#3244.
The text was updated successfully, but these errors were encountered: