search

xapi-project / xapi-storage

Experimental new storage interface for xapi
https://xapi-project.github.io/xapi-storage/
9 stars 19 forks source link

ci: switch to github workflow #112

Closed psafont closed 2 years ago

psafont commented 2 years ago

The whole deployment to github pages is untested.

The doc generator generator should work by creating 4 files in .gh-pages:

datapath.html.md
plugin.html.md
task.html.md
volume.html.md

Then wipe the directory source/includes in the branch slate: https://github.com/xapi-project/xapi-storage/tree/slate/source/includes (hence the keep_files: false, publish_branch: slate and destination_dir: source/includes )

and commiting the newly created files in that branch and directory.

If it goes wrong, I'll just have to manually intervene

The tests are happy: https://github.com/psafont/xapi-storage/runs/6778115598?check_suite_focus=true

undu commented 2 years ago

xapi-storage is a part of xen-api now, a different approach for generating docs should be taken: https://github.com/xapi-project/xen-api/commits/master/ocaml/xapi-storage

MarkSymsCtx commented 2 years ago

xapi-storage is a part of xen-api now, a different approach for generating docs should be taken: https://github.com/xapi-project/xen-api/commits/master/ocaml/xapi-storage

This repository should be retired then otherwise it will cause confusion

psafont commented 2 years ago

Cleanup actions need to be decided, these repositories might still be required for LCM fixes. Replacing the content of the master branch to point out the current situation is the option I'm leaning towards the most. This should allow to keep publishing docs from the other repository while having the LCM branch available if needed

psafont commented 2 years ago

Work is done in https://github.com/xapi-project/xen-api/pull/4729