Automatic Updates #26
No reviewers
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
HugeSpaceship/patchwork!26
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "FeTetra/patchwork:updates"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR implements a simple automatic update system and some configuration changes to add options for changing the update server and enabling/disabling updates (as well as an option to enable/disable patching the XXTEA network key).
The client will send an HTTP header called X-Patchwork-Client-Version which is it's own version number, and expects the server to send an updated SPRX module and a hash of that file in a header called X-Patchwork-Sprx-Hash. It should receive a 200 if the server has an update to send, or a 204 if the client's version is great enough. Any other response is treated as an error.
auto-updateinto branchupdatesPipelines as Code CI is skipping this commit.
User FeTetra is not allowed to trigger CI via pull_request in this repo.
Pipelines as Code CI is skipping this commit.
User FeTetra is not allowed to trigger CI via pull_request in this repo.
/ok-to-test
Pipelines as Code CI is skipping this commit.
User zaprit is not allowed to trigger CI via pull_request in this repo.
/ok-to-test
/ok-to-test
Pipelines as Code CI is skipping this commit.
User zaprit is not allowed to trigger CI via pull_request_closed in this repo.
Pipelines as Code CI is skipping this commit.
User zaprit is not allowed to trigger CI via pull_request in this repo.
Pipelines as Code CI is skipping this commit.
User FeTetra is not allowed to trigger CI via pull_request in this repo.
/ok-to-test
Pipelines as Code CI/patchwork-pr-q9vmd is running.
Starting Pipelinerun patchwork-pr-q9vmd in namespace hugespaceship-ci
You can monitor the execution using the Not configured PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n hugespaceship-ci patchwork-pr-q9vmd -fPipelines as Code CI/patchwork-pr-q9vmd has successfully validated your commit.
Task Statuses:
fetch
build
go-build
patch-generate
upload-artifacts
cleanup