build directory - ui-bundle.zip - automation process in docs

[mmattel]

Currently the build directory is excluded by

cat .gitignore
/build/
/node_modules/
/public/

If we want to automate the inclusion of ui-bundle.zip in docs originated in this repro in directory build, we would need to include it.

If I get that right, it would then need on the docs side in site.yml the inclusion (just as an example):

ui:
  bundle:
    url: https://github.com/owncloud/docs-ui/build/ui-bundle.zip
    snapshot: true

Is that correct?

In docs
you have an empty build directory kept by .gitignore.
and in the root folder of docs you can find the current local (unautomated, out of sync) version of ui-bundle.zip

@tboerger @settermjd

[tboerger]

Best would be some drone process on every push to master branch. The built artifact will be uploaded to our Minio instance where antora can fetch the theme from.

[tboerger]

The process is automated now, the latest bundle can always be downloaded from https://minio.owncloud.com/documentation/ui-bundle.zip

[mmattel]

@tboerger questions:

• how is the process when there is a merge in docs-ui that the bundle is created and copied to minio?
• shouldn´t that be documented in readme.md?

[tboerger]

The UI bundle gets updated on every push to the master branch. If @settermjd tags a git version the bundle gets automatically assigned to a GitHub release.

Of course the process should be documented to make it clear to everybody, but I can't do everything at once ;)