Closed jburel closed 3 months ago
Conflicting PR. Removed from build OMERO-insight-push#299. See the console output for more details. Possible conflicts:
--conflicts
Conflicting PR. Removed from build OMERO-insight-push#300. See the console output for more details. Possible conflicts:
--conflicts Conflict resolved in build OMERO-insight-push#301. See the console output for more details.
Looks good to me. Any idea why the build is failing? Also a bit worried that the merge-ci build doesn't work (strangely local gradle build does).
the build was failing because artifacts.openmicroscopy.org was down due to the power outage
Looks good to me. Any idea why the build is failing? Also a bit worried that the merge-ci build doesn't work (strangely local gradle build does).
@dominikl I have tested locally the following:
gradle build
unzip build/distributions/OMERO.insight-5.8.4-SNAPSHOT.zip
Everything works as expected.
Then tested the latest release downloaded from GitHub and unzipped i.e.
bash ~/Desktop/OMERO.insight-5.8.3/bin/omero-insight
It works too
Everything works as expected. Then tested the latest release downloaded from GitHub and unzipped i.e.
bash ~/Desktop/OMERO.insight-5.8.3/bin/omero-insight
It works too
What @dominikl is meaning is (i.e. grab the build from jenkins, which has to be started using bash as well, but fails as below)
(cli) pwalczysko@Petrs-MBP ~ % bash ~/Downloads/OMERO.insight-5.8.4-SNAPSHOT/bin/omero-insight
Error: LinkageError occurred while loading main class org.openmicroscopy.shoola.Main
java.lang.ExceptionInInitializerError: null
@jburel I have successfully repeated your workflow with release artifacts from GitHub - it very much resembles my workflow ^^^ except that the zip is from Jenkins in my case. The only difference thereafter is the result - the Github release artifact just works, the CI artifact from jenkins does not.
It does not work from merge-ci sorry I forgot to mention it in my testing report
👍 Any idea how we could fix the msi installer issue? https://github.com/ome/omero-insight/issues/400 . I guess that will be bigger effort to find out what's going wrong there, right?
Looks good. Just release date 'January' should be updated to 'May' :-)