saudet commented on issue #17783: URL: https://github.com/apache/incubator-mxnet/issues/17783#issuecomment-749934604
I've updated my fork with a workflow for Java build on GitHub Actions: https://github.com/saudet/incubator-mxnet/commit/2be05405090e388bdfcb52d40d9419ca7aa038c4 Please let me know what you think of this! It's currently building and testing for Linux (CentOS 7), Mac, and Windows on x86_64 with and without CUDA: https://github.com/saudet/incubator-mxnet/actions/runs/437312011 (It looks like the build doesn't work for CUDA 11.1 with Visual Studio 2019 yet, but that's unrelated to Java.) Since my account at Sonatype doesn't have deploy access to `org.apache`, the artifacts are getting deployed here for now: https://oss.sonatype.org/content/repositories/snapshots/org/bytedeco/mxnet/2.0-SNAPSHOT/ But this can be changed by updating only a single line here: https://github.com/saudet/incubator-mxnet/blob/add-javacpp/java/build.gradle#L8 In any case, the `javadoc` secondary artifact also gets deployed as part of the build there. Where does the publishing to the main site happen? Somewhere in here by the looks of it: https://github.com/apache/incubator-mxnet/tree/master/ci/publish/website We can fetch the latest `javadoc` archive this way, so I assume we could add that to the scripts? ``` $ mvn dependency:get -Dartifact=org.bytedeco:mxnet:2.0-SNAPSHOT:javadoc $ unzip ~/.m2/repository/org/bytedeco/mxnet/2.0-SNAPSHOT/mxnet-2.0-SNAPSHOT-javadoc.jar -d ... ``` > It's also fine to use Github Actions if that's easier for you. The main reason for using Jenkins is that the MXNet test suite is too large for a free service such as Github Actions and that there are also GPU tests involved. Java tests can initially run on Github Actions and be migrated later to Jenkins based on need. For that, GitHub Actions now support self-hosted runners, where we just need to provision some machines on the cloud somewhere, and install the equivalent of Jenkins Agent on them, and that's it. Much easier than maintaining Jenkins. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@mxnet.apache.org For additional commands, e-mail: issues-h...@mxnet.apache.org
