On Wednesday, June 3, 2020 at 12:48:56 PM UTC+2, Karl Heinz Marbaise wrote: > > On Wednesday, June 3, 2020 at 12:34:34 PM UTC+2, Anders Hammar wrote: >> >> How's the release site part supposed to work? Won't releases still be >> done manually outside of Github Actions? >> >> Also, every build on master cannot (must not) overwrite the site for the >> current (latest) release. But maybe to some kind of "staging" space? >> > > The current state is based on the idea to keep the release process on your > local machine (technically it can be changed to put on GitHub actions with > the problem gpg signing artifacts and putting your key on a remote > machine?; That a complete different story). > > The release will be made as usual from your local machine. No change. > After made a release you have to close the appropriate milestone (which > will trigger the change log generation). >
The link to the release notes generator missed: https://github.com/mojohaus/mojo-parent/blob/9fe14ae54e37647380c73cdb63836315deb1313e/.github/workflows/release-notes.yml > > So the release build will create the artifacts as well as deploy the > generated site via maven-scm-publish-plugin to github pages like before > https://www.mojohaus.org/mojo-parent/ and furthermore opens the option > to run master (site generation which is deployed to > https://www.mojohaus.org/mojo-parent/snapshot/). This will be done by the > https://github.com/mojohaus/mojo-parent/blob/9fe14ae54e37647380c73cdb63836315deb1313e/.github/workflows/deploy.yml > Github action. So having simple solution to have snapshot state as well as > release state on github pages... > > Kind regards > Karl Heinz Marbaise > >> >> /Anders >> >> On Tue, Jun 2, 2020 at 6:43 PM Karl Heinz Marbaise <[email protected]> >> wrote: >> >>> Hi, >>> >>> >>> currently I'm working the subject to replace the travis build with >>> GitHub actions: >>> >>> >>> https://github.com/mojohaus/mojo-parent/issues/114 >>> >>> >>> Replace the CI tooling with GitHub actions >>> >>> * Building with different JDK's (8,11,13,14) >>> >>> * Building on different platforms Linux, Windows, MacOS >>> >>> * Add site generation which supports release sites ( >>> https://www.mojohaus.org/mojo-parent/) as well as snapshot state ( >>> https://www.mojohaus.org/mojo-parent/snapshot/) >>> >>> * By each build on master the site will be generated. That means also >>> the site generation is tested (like javadoc etc.). >>> >>> * Add generation of release notes which is triggered by closing >>> milestone on GitHub. >>> >>> >>> >>> After I have done that for mojo-parent I would like to go plugin after >>> plugin to change the builds for each plugins as well... >>> >>> >>> WDYT? >>> >>> I would like to make it lazy consensus VOTE within 72 h >>> >>> >>> Kind regards >>> Karl Heinz Marbaise >>> >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "mojohaus-dev" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/mojohaus-dev/45b4fccb-b83e-42e3-b95c-8b498fb03cb8%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/mojohaus-dev/45b4fccb-b83e-42e3-b95c-8b498fb03cb8%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >> -- You received this message because you are subscribed to the Google Groups "mojohaus-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/mojohaus-dev/24f21aac-8aa2-4b91-8c58-468357668315%40googlegroups.com.
