Skip to content

Sync from snapshot, Mainnet, ParityDB pruned #58

Sync from snapshot, Mainnet, ParityDB pruned

Sync from snapshot, Mainnet, ParityDB pruned #58

---
# This workflow performs sync to Mainnet from a pruned ParityDB snapshot using the latest
# main version.
#
# For now, this test not quite correctly tests sync Mainnet from latest aleph-node binary,
# for which we don't guarantee it will always happen to work.
name: Sync from snapshot, Mainnet, ParityDB pruned
on:
# At 20:00 on Wednesday and Saturday
# Time corresponds with a snapshot creation time
schedule:
- cron: '0 20 * * 3,6'
workflow_dispatch:
concurrency:
group: ${{ github.ref }}-${{ github.workflow }}
cancel-in-progress: false
jobs:
check-vars-and-secrets:
name: Check vars and secrets
uses: ./.github/workflows/_check-vars-and-secrets.yml
secrets: inherit
build-production-aleph-node:
needs: [check-vars-and-secrets]
name: Build production aleph-node
uses: ./.github/workflows/_build-aleph-node.yml
with:
ref: ${{ github.ref }}
production: true
test-sync:
needs: [build-production-aleph-node]
name: Download snapshot and run
runs-on: [self-hosted, Linux, X64, medium-1000GB]
timeout-minutes: 90
steps:
- name: Checkout source code
uses: actions/checkout@v4
- name: Test sync
uses: ./.github/actions/sync-from-snapshot
with:
# yamllint disable-line rule:line-length
aleph-node-artifact-name: ${{ needs.build-production-aleph-node.outputs.artifact-name-binary }}
args: --mainnet --parity-db --pruned
aws-access-key-id: ${{ secrets.AWS_MAINNET_S3_ACCESS_KEY_ID }}
aws-secret-access-key: ${{ secrets.AWS_MAINNET_S3_SECRET_ACCESS_KEY }}
slack-notification:
name: Slack notification
runs-on: ubuntu-20.04
needs: [test-sync]
if: >
!cancelled() &&
github.event_name != 'workflow_dispatch'
steps:
- name: Send Slack message
uses: Cardinal-Cryptography/github-actions/slack-notification@v7
with:
notify-on: "failure"
env:
SLACK_WEBHOOK: ${{ secrets.SLACK_WEBHOOK_DEV_ONDUTY }}