-
Notifications
You must be signed in to change notification settings - Fork 2
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
Release automation #1
Comments
I would not overstretch this whole automation process to compiling + compressing.
Releases are more-or-less stable, and all the compiled executables, source codes, .dll/.so files, VS projects, etc. will be provided in the main branch.
Creating RWTH releases would just waste our time.
Also, CI for VS projects might not be as straightforward and I have done it only on University Azure.
…________________________________________
From: Jan C. Brammer ***@***.***
Sent: Tuesday, December 12, 2023 15:24
To: IUPAC-InChI/InChI_Dev
Cc: Baljozovic, Dorde; Mention
Subject: [IUPAC-InChI/InChI_Dev] Release automation (Issue IUPAC-InChI/InChI#1)
We've started to configure our release automation: https://github.com/IUPAC-InChI/InChI_Dev/blob/main/.github/workflows/release.yml.
In short, every time we tag and publish a new release, a GitHub action uploads zip archives according to the convention on https://www.inchi-trust.org/all-downloadable%20versions/.
We could expand this by automatically building / compiling our release artifacts, i.e., the contents of INCHI-1-BIN<https://github.com/IUPAC-InChI/InChI_Dev/tree/main/INCHI-1-BIN> such as libinchi.so<https://github.com/IUPAC-InChI/InChI_Dev/blob/main/INCHI-1-BIN/linux/64bit/so/libinchi.so.1.07.gz>. In order to do that we could write compilation scripts (essentially just calling make like so<https://github.com/IUPAC-InChI/InChI_Dev/blob/main/INCHI-1-TEST/compile_inchi_lib.sh>) which we then run as part of the release automation. By scripting the compilation, we can run it locally as well as during the automation.
@djb-rwth<https://github.com/djb-rwth>, we'd need to figure out which version of which compiler to run on which OS. That would pretty much be what you documented in the README<https://github.com/IUPAC-InChI/InChI_Dev/blob/main/README.md>, right?
—
Reply to this email directly, view it on GitHub<#1>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/A5BLV6N346PRSUT7OWQINKTYJBSJBAVCNFSM6AAAAABARR5PSSVHI2DSMVQWIX3LMV43ASLTON2WKOZSGAZTOOBWGQ2DSMI>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We've started to configure our release automation: https://github.com/IUPAC-InChI/InChI_Dev/blob/main/.github/workflows/release.yml.
In short, every time we tag and publish a new release, a GitHub action uploads zip archives according to the convention on https://www.inchi-trust.org/all-downloadable%20versions/.
We could expand this by automatically building / compiling our release artifacts, i.e., the contents of INCHI-1-BIN such as libinchi.so. In order to do that we could write compilation scripts (essentially just calling
make
like so) which we then run as part of the release automation. By scripting the compilation, we can run it locally as well as during the automation.@djb-rwth, we'd need to figure out which version of which compiler to run on which OS. That would pretty much be what you documented in the README, right?
See for example https://github.com/igraph/igraph/blob/master/.github/workflows/build-cmake.yml (thanks @flange-ipb).
TODO:
release
workflow only ifci
workflow passes for the tagged commit that triggeredrelease
ci
)The text was updated successfully, but these errors were encountered: