Open dgault opened 4 years ago
homebrew formula: https://downloads.openmicroscopy.org/bio-formats/6.4.0/artifacts/bioformats-6.4.0.zip This is not currently uploaded via actions
Tested GitHub actions to generate and upload artifacts see https://github.com/jburel/bioformats/releases/tag/v6.6.0-m1
https://github.com/jburel/bioformats/releases/tag/v6.6.0-m2 now have the various zip/jars and also the sha256 so it can be used in the homebrew formula: ignore the version mismatch, this is b/c I have tagged without changing to trigger the GH action
new tag created with shasum and md5 to match what is available under download I have opted not to have a sha1 or md5 per file to reduce the number of attachments
I now build on windows and ubuntu via GH actions. so we can get rid of appveyor and travis files
@dgault https://github.com/jburel/bioformats/releases/tag/v6.6.0-m3 should have what is currently under download.o.org Could you double check? See comment above about sha1 and md5 https://github.com/ome/bioformats/issues/3621#issuecomment-708626796
Now I have example using github actions pushing artifacts to Maven central, for both gradle and maven project
https://ci.openmicroscopy.org/job/BIOFORMATS-DEV-latest-version-bump/ only bumps the version in the pom and sets the value in all the pom.xml by running a python scripts
STABLE_VERSION
in UpgradeChecker.java
could be removed.mvn versions:set -DnewVersion=XXXX
The workflow could become:
Remaining open question: docs are combined i.e. not one per component so using javadoc.io is not going to work nicely
Dependency Repos
Downstream Repos
Links to downloads
Misc Updates
management tools /playbooks
Potential Issues which need investigating