ci: check remote repos for updates #4

Open
opened 2025-03-14 16:47:14 +03:00 by DarkCat09 · 3 comments
Owner

Periodically check for new OpenJ9 releases and new commits in Piped-Backend master branch (skip if their GitHub CI failed for >50% actions), then trigger our CI by creating a release in this repo.

Periodically check for new [OpenJ9 releases](https://github.com/ibmruntimes/openj9-openjdk-jdk21/releases) and new commits in [Piped-Backend](https://github.com/TeamPiped/Piped-Backend) master branch (skip if their GitHub CI failed for >50% actions), then trigger our CI by creating a release in this repo.
Author
Owner

Or maybe not by creating a release...

Is there a convenient mechanism to trigger CI? Can an update-checker-bot create empty commits?

Or maybe not by creating a release... Is there a convenient mechanism to trigger CI? Can an update-checker-bot create empty commits?
Author
Owner

OK, let it be releases

OK, let it be releases
Contributor

@DarkCat09 wrote in #4 (comment):

Or maybe not by creating a release...

Is there a convenient mechanism to trigger CI? Can an update-checker-bot create empty commits?

Releases are the most commonly used method for this kind of thing.

@DarkCat09 wrote in https://git.dc09.ru/DarkCat09/docker-openj9-piped/issues/4#issuecomment-480: > Or maybe not by creating a release... > > Is there a convenient mechanism to trigger CI? Can an update-checker-bot create empty commits? Releases are the most commonly used method for this kind of thing.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: DarkCat09/docker-openj9-piped#4
No description provided.