on the main site, now that publication is easy, you can test new source formats different than apt I'll also provide soon a PR to improve breadcrumbs
later, we can work on adding edit button on each page, but that will require updating your specific skin, which is currently in svn only: is a migration to Git feasible? Regards, Hervé Le dimanche 15 novembre 2020, 19:17:09 CET Michael Osipov a écrit : > That was it. Gavin added the permission and it works now. > What's is next from your POV? > > Am 2020-11-15 um 00:11 schrieb Hervé BOUTEMY: > > I think that credentials are there, but write authorization to > > https://svn.apache.org/viewvc/httpcomponents/site/ > > for svn-site-role is missing > > > > Regards, > > > > Hervé > > > > Le vendredi 13 novembre 2020, 13:52:24 CET Michael Osipov a écrit : > >> Am 2020-11-13 um 12:57 schrieb Michael Osipov: > >>> Am 2020-10-27 um 14:04 schrieb Herve Boutemy: > >>>> Hi, > >>>> > >>>> As asked by Michael, I had a quick look at your current setup, your > >>>> pain points and what can be done to improve your experience. > >>>> I just proposed one little PR to go step by step: > >>>> https://github.com/apache/httpcomponents-website/pull/4 > >>>> > >>>> With that setup, building and deploying the main site is just "mvn > >>>> site-deploy". > >>>> As explain in the PR comment: "Once this step is ok from a developer > >>>> point of view, run on his local machine, next step will be to > >>>> configure a Jenkins job to do mvn site-deploy automatically when > >>>> updating source content: from there, many little improvements can be > >>>> done (testing Markdown and/or Asciidoc source instead of apt, > >>>> improving site.xml, reworking the skin to add the "edit" icon in > >>>> breadcrumb, ...)" > >>>> > >>>> On the question of "piecing together content of multiple releases into > >>>> a single web site", this is the next step that will improve > >>>> performance but requires some structure change (and 1 infra task done > >>>> by infra): IMHO, we should discuss that once the previous non-invasive > >>>> steps are working, then you start having a better confidence based on > >>>> better experience. > >>>> > >>>> once 1 dev is able to rebuild and publish from his computer with "mvn > >>>> site-deploy", I can provide you a few light improvements to see the > >>>> site evolve with the new setup: just tell me once it works and you are > >>>> ready to try next steps > >>> > >>> Hervé, > >>> > >>> I have merged your PR. It does run for me locally as well as with "mvn > >>> site-deploy". Set up the Jenkins job just like maven-site, but it still > >>> fails for me [1]: > >>> ERROR: Could not find the JDK installation: JDK 1.8 (latest). Make sure > >>> it is configured on the Global Tool Configuration page > >> > >> Screw that, it is almost working. It was purely my bad: > >> https://ci-builds.apache.org/job/HttpComponents/job/HttpComponents%20Webs > >> ite /job/master/2/ > >> > >> Just credentials are missing. How do I supply credentials? Gavin > >> McDonald said on Slack that the node is entitled to. > >> > >> What is the next step for automation? > >> > >> Michael > >> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [email protected] > >> For additional commands, e-mail: [email protected] > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
