You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Stamatis Zampetakis (Jira)" <ji...@apache.org> on 2025/01/28 10:07:00 UTC

[jira] [Commented] (CALCITE-6806) Add CI action to test site remains buildable after changes

    [ https://issues.apache.org/jira/browse/CALCITE-6806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17921667#comment-17921667 ] 

Stamatis Zampetakis commented on CALCITE-6806:
----------------------------------------------

This check will be helpful to avoid breaking the build as it happened in CALCITE-6803.

> Add CI action to test site remains buildable after changes
> ----------------------------------------------------------
>
>                 Key: CALCITE-6806
>                 URL: https://issues.apache.org/jira/browse/CALCITE-6806
>             Project: Calcite
>          Issue Type: Task
>            Reporter: Stamatis Zampetakis
>            Priority: Major
>
> Currently, we have CI automation to build and publish the website when:
> * [a release tag is created|https://github.com/apache/calcite/blob/main/.github/workflows/publish-website-on-release.yml]
> * [a commit is merged to main branch |https://github.com/apache/calcite/blob/main/.github/workflows/publish-non-release-website-updates.yml]
> but there are no checks to ensure that the site can be built and before merging a PR.
> We should add a CI check to build the website if a PR changes anything under the site directory.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)