Skip to content

HBASE-29878 Add GitHub Action workflow for building and publishing HBase website#7933

Draft
PDavid wants to merge 16 commits intoapache:masterfrom
PDavid:HBASE-29878-website-gh-actions
Draft

HBASE-29878 Add GitHub Action workflow for building and publishing HBase website#7933
PDavid wants to merge 16 commits intoapache:masterfrom
PDavid:HBASE-29878-website-gh-actions

Conversation

@PDavid
Copy link
Contributor

@PDavid PDavid commented Mar 13, 2026

No description provided.

@PDavid PDavid self-assigned this Mar 13, 2026
@Apache9
Copy link
Contributor

Apache9 commented Mar 14, 2026

Do we have enough permission to push the repo in github actions?

pull_request:
types: [opened, synchronize, reopened]
schedule:
- cron: '0 14 * * *'
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can github actions support something like pollSCM in jenkins? Where we will not run the pipeline if there is no change in git.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Very good question. I'm not sure, maybe it can be done somehow. I'd have to check. But makes perfect sense. 👍

@Apache9
Copy link
Contributor

Apache9 commented Mar 17, 2026

@PDavid I think we can implement a new jenkins job to publish the website, where we build the website content on hbase node, stash it, and then unstash it on website node, update the website repo and push it.

I could file an issue and try to implement it.

Thanks.

@PDavid
Copy link
Contributor Author

PDavid commented Mar 17, 2026

Do we have enough permission to push the repo in github actions?

No, unfortunately we don't have enough permissions. Usually the workflow only have permission to push to the same repo it "runs in".

To push to a different repository, the standard GITHUB_TOKEN usually won't cut it because its permissions are scoped only to the current repo. You’ll need a Personal Access Token (PAT) or a GitHub App token with "Contents: Write" permissions for the target repository.

@PDavid
Copy link
Contributor Author

PDavid commented Mar 17, 2026

@PDavid I think we can implement a new jenkins job to publish the website, where we build the website content on hbase node, stash it, and then unstash it on website node, update the website repo and push it.

I could file an issue and try to implement it.

Thanks.

Thanks @Apache9, to be completely honest I don't have too much experience with Jenkins but what you suggest makes perfect sense to me. Just wanted to check if I can quickly use GitHub Actions instead of Jenkins.

@apache apache deleted a comment from juniorcastro0152-hub Mar 17, 2026
@apache apache deleted a comment from juniorcastro0152-hub Mar 17, 2026
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