Well I think I wrote down the entire workflow as well as the when's and why's
so many times that I'm not going to repeat them again.
You don't need the build at builds.a.o at all. I just set that up in the
beginning because in the beginning I thought I would have to trigger buildbot
from there and didn't delete it after finishing, because I simply forgot it's
What you get is:
- A website in git and not svn.
- The code is generally a lot cleaner.
- You don't have to commit changes to test them in the staging area.
- You don't have to use that stupid web interface to release staged stuff to
I currently don't have asciidoctor in there at all, so please stop describing
this approach as complicated and simply read my emails.
1. Do changes in the "maven-site" branch
2. Test them locally by running "mvn clean site"
3. Commit and push them
That's it. Nothing more to it.
Von meinem Samsung Galaxy Smartphone gesendet.
-------- Ursprüngliche Nachricht --------
Von: Alex Harui <aha...@adobe.com>
Datum: 12.10.16 20:20 (GMT+01:00)
Betreff: Re: AW: AW: [Website] Progress on the Website-Generation topic
Safari spit some warnings like that to the console but the menu and
carousel seems to be working.
I noticed in the emails from the buildbot that it seems to be copying html
files into the flex-site repo. The version of index.html in the repo
comes out differently.
I added an "Archive artifacts" option to the Maven site build and hit
"Build Now'. That might make a version of the files folks can access
without having to log in.
So, AIUI, using this workflow would make changing the website dependent on
both builds.a.o and buildbot, whereas svnpubsub and gitpubsub only require
buildbot? But what we get for this additional step is asciidoc support?
On 10/12/16, 10:56 AM, "Christofer Dutz" <christofer.d...@c-ware.de> wrote:
>Ok ... I just noticed that if you do it that way Chrome complained about
>"unsecure scripts" (I don't get that message when accessing the files
>otherwise. I had to enable those scripts to get the menus and carousel
>Von: Alex Harui <aha...@adobe.com>
>Gesendet: Mittwoch, 12. Oktober 2016 19:45:54
>Betreff: Re: AW: [Website] Progress on the Website-Generation topic
>I'm seeing emails titled "Automatic Site Publish by Buildbot". Are you
>sure we can't see the buildbot output? I think you'd get more feedback if
>folks don't have to bring down the repos and set it up.
>On 10/12/16, 10:39 AM, "Christofer Dutz" <christofer.d...@c-ware.de>
>>Currently there is no such place, where you can just go with the browser,
>>but just clone the flex-site repo and checkout the "asf-site" branch and
>>you should have the working version locally.
>>Just open index.html with your favorite browser :-)
>>At least I just checked exactly that path and it worked as expected.
>>Von: Alex Harui <aha...@adobe.com>
>>Gesendet: Mittwoch, 12. Oktober 2016 18:31:05
>>Betreff: Re: [Website] Progress on the Website-Generation topic
>>Is there a URL we can go to and see the results of this workflow?
>>On 10/12/16, 5:48 AM, "Christofer Dutz" <christofer.d...@c-ware.de>
>>>I just wanted to post, that I have finished setting up a new version of
>>>the Website. The source is located in the "maven-site" branch of the
>>>This is a Maven build which produces the Website using the
>>>maven-site-plugin and the reflow-site plugin to render a responsive
>>>version of the website using bootstrap (Seems that this is pretty
>>>to the original version).
>>>I migrated all the ".cmsPage" files I needed to Markdown format and
>>>removed unnecessary html code inside. I think the code is a lot cleaner
>>>and easier to maintain.
>>>Currently the site does look a little different than the original, but
>>>I'm no CSS guru. I invested about 5 full days in migrating things to the
>>>current point and think we should start discussing if fine-tuning makes
>>>sense (I don't see any sense in investing more time and then we decide
>>>not to use it)
>>>The current workflow is that you checkout the "maven-site" branch
>>>(eventually apply your changes) and do a "mvn clean site" build. This
>>>will produce the website content in the "target/site" directory. Here
>>>can have a look at the content which is produced. If you are satisfied
>>>with your changes, you commit and push them and a buildbot build-job I
>>>configured (what was quite a task) will run the same build and push the
>>>generated content to the "asf-site" branch in the same git repo
>>>(Currently you should be able to have a look at the generated content,
>>>checking out that branch).
>>>As soon as we are happy with the new version, all we have to do is to
>>>tell Infra to sync the "asf-site" branch with their website repo and the
>>>website is online.
>>>I also documented the procedure of auto-building the website on the
>>>website itself as an additional page under Documentation "Contributing
>>>the Flex Website".
>>>So I'm ready for some feedback ;-)