goutamadwant opened a new pull request, #12614: URL: https://github.com/apache/seatunnel/pull/12614
### Purpose of this pull request Fixes #12613. The `Build website` check rebuilds every released docs snapshot in both locales. Since apache/seatunnel-website#546 added the 3.0.0 snapshot, the docusaurus build runs into the job's 90-minute timeout on most PRs. A PR's docs changes only reach the current docs and the shared images, so this keeps only the newest released snapshot in the website's `versions.json` before building. The website config needs that one entry (`versions[0]`). **Before:** current docs + 22 released snapshots, en + zh-CN. 63–90+ minutes on GitHub runners, cancelled at 90 on most PRs (see #12613). **After:** current docs + the 3.0.0 snapshot, en + zh-CN. | Local build, same machine, `dev` docs synced | Docusaurus build | |---|---| | Before (all 22 versions) | 155.6 min | | After (current + 3.0.0) | 12.9 min | Both builds succeed and generate the current docs in both locales (534 en, 534 zh-CN pages). Trade-off: the check no longer covers old snapshots. The only files they take from this repo are three images in `docs/images` (`azkaban.png`, `kafka.png`, `workflow.png`, embedded by the 2.1.0 and 2.1.1 snapshots); nothing under `docs/images` was deleted in the last year. The website repo's own `Build and Deploy` workflow still builds every version daily from `dev`. ### Does this PR introduce _any_ user-facing change? No. CI only; the website is still built and published by apache/seatunnel-website. ### How was this patch tested? Reproduced the job's steps locally with `dev` docs: ```shell git clone --depth 1 https://github.com/apache/seatunnel-website.git bash seatunnel/tools/documents/sync.sh seatunnel seatunnel-website cd seatunnel-website node -e "const fs = require('fs'); const v = JSON.parse(fs.readFileSync('versions.json')); fs.writeFileSync('versions.json', JSON.stringify(v.slice(0, 1), null, 2) + '\n');" npm install && npm run build ``` - With the trim: build passes in 12.9 min; `build/docs` and `build/zh-CN/docs` contain the current docs and `3.0.0`. - Without the trim (same machine): build passes in 155.6 min. - `backend.yml` parses as valid YAML. ### Check list * [ ] If any new Jar binary package adding in your PR, please add License Notice according [New License Guide](https://github.com/apache/seatunnel/blob/dev/docs/en/developer/new-license.md) * [ ] If necessary, please update the documentation to describe the new feature. https://github.com/apache/seatunnel/tree/dev/docs * [ ] If necessary, please update `incompatible-changes.md` to describe the incompatibility caused by this PR. * [ ] If you are contributing the connector code, please check that the following files are updated: 1. Update [plugin-mapping.properties](https://github.com/apache/seatunnel/blob/dev/plugin-mapping.properties) and add new connector information in it 2. Update the pom file of [seatunnel-dist](https://github.com/apache/seatunnel/blob/dev/seatunnel-dist/pom.xml) 3. Add ci label in [label-scope-conf](https://github.com/apache/seatunnel/blob/dev/.github/workflows/labeler/label-scope-conf.yml) 4. Add e2e testcase in [seatunnel-e2e](https://github.com/apache/seatunnel/tree/dev/seatunnel-e2e/seatunnel-connector-v2-e2e/) 5. Update connector [plugin_config](https://github.com/apache/seatunnel/blob/dev/config/plugin_config) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
