Skip to content

Add deploy-site.yaml workflow#465

Draft
ppkarwasz wants to merge 1 commit into
feat/logging-parent-migrationfrom
feat/generate-staging-site
Draft

Add deploy-site.yaml workflow#465
ppkarwasz wants to merge 1 commit into
feat/logging-parent-migrationfrom
feat/generate-staging-site

Conversation

@ppkarwasz

@ppkarwasz ppkarwasz commented Jul 22, 2026

Copy link
Copy Markdown
Member

Publishes the Antora site to logging.apache.org/flume/2.x via the logging-parent reusable workflow. The old 1.x site stays in logging-flume-site (content/flume).

Note

Stacked on #464, which should be merged before this one.

Publishes the Antora site to `logging.apache.org/flume/2.x` via the `logging-parent` reusable workflow. The old 1.x site stays in `logging-flume-site` (`content/flume`).

Since the reusable workflow builds the site with `./mvnw site`, the Antora setup is aligned with the `logging-parent` machinery: `antora.yml` is generated from `antora.tmpl.yml` (kept in sync for local builds, as in Log4j) and the useless per-module Maven Site Plugin runs are skipped in both POM hierarchies.

Assisted-By: Claude Fable 5 <noreply@anthropic.com>
@ppkarwasz
ppkarwasz force-pushed the feat/generate-staging-site branch from 7597b4f to 913182f Compare July 22, 2026 12:19
@ppkarwasz

Copy link
Copy Markdown
Member Author

This PR does not regenerate the staging website until we merge it, but I tested the commands in the reusable workflow and published a first version manually:

https://logging.staged.apache.org/flume/2.x/flume/index.html

@ppkarwasz
ppkarwasz marked this pull request as draft July 22, 2026 17:20
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

Successfully merging this pull request may close these issues.

2 participants