Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sort out triggering of docs build #4859

Open
phil-davis opened this issue Jul 6, 2023 · 3 comments
Open

Sort out triggering of docs build #4859

phil-davis opened this issue Jul 6, 2023 · 3 comments

Comments

@phil-davis
Copy link
Contributor

When one of the docs repos (docs-client-desktop, docs-ocis, docs-server, docs-webui or whatever) changes, the drone merge CI triggers a rebuild of the docs repo. That docs build job does whatever is needed to grab the latest content of all the docs and publish it all.

With recent changes to the drone secrets, the drone_token is no longer available to the various jobs. And so the attempt to trigger a docs build fails.

We need to sort out how this process will be re-engineered.

Note: the trigger code is still in the drone CI code in each repo - that will need to be either changed to "something" or deleted, depending on how the solution to this issue is engineered.

@phil-davis
Copy link
Contributor Author

@mmattel FYI - need to discuss this all with anyone who might have good ideas about how this can best be engineered now.

@mmattel
Copy link
Contributor

mmattel commented Jul 6, 2023

There is an idea from @dragonchaser and @fschade that looks imho promising, but they can explain better than me 😅 Maybe to join in the mornig our ocis zoom so we can discuss.

@dragotin
Copy link

dragotin commented Apr 2, 2024

is this still hot?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants