have a per PR and online access to the generated documentation (this was my initial goal in fact) using the build artifacts feature provided by circleci.

we could also save murdock's output.

we could also save murdock's output

I thought of it but the effort was not the same, at least for me.

Is there still interest in this PR?

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you want me to ignore this issue, please mark it with the "State: don't stale" label. Thank you for your contributions.

I've updated the initial goal of this PR to only build the documentation and use Circle CI Artifacts to get a preview of the generated documentation.
The last run result (on my fork) is available here: https://1526-44016379-gh.circle-artifacts.com/0/tmp/doc/html/index.html

The bad news is that now it take more than 25 minutes to upload the artifacts to S3 (the storage backend on CircleCI). This is because the doxygen documentation generates a lot of single file and they are copied one by one.
The advantage is that it requires no setup to get the preview (except the circleci config file, which is rather simple).

The bad news is that now it take more than 25 minutes to upload the artifacts to S3 (the storage backend on CircleCI).

Are there other backend options?

Are there other backend options?

I don't think so: https://circleci.com/docs/2.0/artifacts/

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you want me to ignore this issue, please mark it with the "State: don't stale" label. Thank you for your contributions.

still useful, although slow.

Can we revive this one? As long as circle-ci does not block a PR getting merged I find this quite useful (even if slow), I have had many times issues or question about whether my locally generated doc would match what would be displayed on riot.org.

What needs to be configured to add the status of circle-ci to the PR?

What needs to be configured to add the status of circle-ci to the PR?

I think integration of external applications, similar to Travis I guess.

If 25 minutes is acceptable before the documentation preview is available, using circleci is useful. Unfortunately, because of the huge amount of single files to upload (+19k), 99% of the time is spent in uploading the artifacts.
To speed-up things there are alternatives:

• retrieve the documentation in an archive, still using circleci : this is way faster (a couple of minutes) but no online preview.
• use github actions: there's one for uploading artifacts. I just tested in ci: setup github actions #14308 and it works, just takes 15 minutes to complete but has the same limitation: the documentation is available in an archive, so no online preview.

We could (and probably should), like with Travis make the results non-binding. If for any reason the artefacts are of any interest, the wait time is not much longer as with current Murdock ;-).

I think integration of external applications, similar to Travis I guess.

You have some doc on that?

You have some doc on that?

Could this one help: https://circleci.com/docs/2.0/gh-bb-integration/#section=projects ?

Can you do a force push to see if it worked?

https://app.circleci.com/pipelines/github/RIOT-OS/RIOT

Integration seems to work, I see a new circleci item.

Integration seems to work, I see a new circleci item.

You seem to need to log in (via GitHub) to be able to see the progress.

So after 27 minutes of copy... the documentation artifacts are available here. And the generated documentation is available at https://2803-44016379-gh.circle-artifacts.com/0/doc/index.html