Skip to content
  1. Feb 23, 2024
  2. Feb 15, 2024
  3. Feb 12, 2024
    • Serban Iorga's avatar
      Add bridge zombienet test back to the CI (#3264) · e661dc0b
      Serban Iorga authored
      Related to https://github.com/paritytech/polkadot-sdk/issues/3176
      
      This PR only adds the first bridge zombienet test back to the CI after
      fixing it, reverting
      https://github.com/paritytech/polkadot-sdk/pull/3071
      
      Credits to @svyatonik for building all the CI infrastructure around
      this.
      e661dc0b
  4. Jan 26, 2024
    • Svyatoslav Nikolsky's avatar
      Remove bridges zombienet tests from CI (#3071) · acd043bc
      Svyatoslav Nikolsky authored
      closes https://github.com/paritytech/parity-bridges-common/issues/2796
      
      This partially reverts the #2439 - there are some changes (unrelated to
      CI) that we still want to keep. The reason of that removal is that with
      async backing enabled for Rococo AH (and for other chains in the near
      future), we see a lot of issues there (because we run `14` nodes +
      additional standalone process within a same container and it causes a
      lot of timeouts). There's no way known to me to fix it right now, so
      we're removing those tests hopefully temporarily to keep CI green
      acd043bc
  5. Jan 12, 2024
    • Svyatoslav Nikolsky's avatar
      Run bridges zombienet tests on CI (#2439) · 5ed0a75f
      Svyatoslav Nikolsky authored
      Brridges zombienet tests are non-standard - zombienet currently missing
      multiple relay chains support (see e.g.
      https://github.com/paritytech/zombienet/pull/796), so we need to go live
      with two relay networks, their parachains + custom test runner (which
      e.g. doesn't shutdown net when its tests are finished and instead waits
      for both networks tests to complete). So we are stuck with native
      zombienet provider => this PR is an attempt to gather everything in a
      single docker container and run tests there ~Draft, because it is far
      from finishing - what I want now is to see how it works on CI~
      5ed0a75f
  6. Sep 29, 2023
  7. Sep 28, 2023
    • Michal Kucharczyk's avatar
      rococo-runtime: `RococoGenesisExt` removed (#1490) · 50242a61
      Michal Kucharczyk authored
      [`RococoGenesisExt`](https://github.com/paritytech/polkadot-sdk/blob/a414ea75
      
      /polkadot/node/service/src/chain_spec.rs#L152-L171)
      is removed. It was the hack to allow overwriting
      `EpochDurationInBlocks`. Removal of `RococGenesisExt` prevents from
      manipulating the state to change the runtime constants.
      
      Changes:
      - Environment variable which controls the `time::EpochDurationInBlocks`
      value was added: `ROCOCO_EPOCH_DURATION` (epoch duration will be set to
      the value of env),
      - `10,100,600` versions of rococo-runtime are built in CI and put into `polkadot-debug` docker image.
      
      `rococo-runtime` building examples:
      - to build runtime for `versi_staging_testnet` which had
      EpochDurationInBlocks set to 100:
        ```
      ROCOCO_EPOCH_DURATION=100 cargo build --features=fast-runtime -p
      rococo-runtime
        ```
      - to build runtime for `wococo_development`
        ```
      ROCOCO_EPOCH_DURATION=10 cargo build --features=fast-runtime -p
      rococo-runtime
        ```
      - to build `versi-staging` chain spec:
        ```
      ROCOCO_EPOCH_DURATION=100 cargo run -p polkadot --features=fast-runtime
      -- build-spec --chain versi-staging --raw
        ```
      - to build `wococo-dev` chain spec:
        ```
      ROCOCO_EPOCH_DURATION=10 cargo run -p polkadot --features=fast-runtime
      -- build-spec --chain wococo-dev --raw
        ```
      
      It is also possible to change the epoch duration by replacing the `code` field in the chain spec with the hex dump of pre-built runtime wasm blob (because the epoch duration is hard-coded into wasm blob).
      
      ---------
      
      Co-authored-by: default avatarBastian Köcher <[email protected]>
      50242a61
  8. Sep 13, 2023
  9. Sep 11, 2023
  10. Sep 06, 2023
    • ordian's avatar
      zombienet: use another collator image for the slashing test (#1386) · a4794398
      ordian authored
      * zombienet: use test-parachain image for the slashing test
      
      * use the right image
      
      * try polkadot-parachain image
      
      * try naming collator alice 🙈
      
      
      
      * add needed job for the pipeline
      
      * fix user id in polkadot-parachain-debug image
      
      * small tweaks to the test
      
      * another small tweak
      
      * yet another small tweak
      
      * bump zombienet version
      
      ---------
      
      Co-authored-by: default avatarJavier Viola <[email protected]>
      a4794398
    • Egor_P's avatar
      GHW for building and publishing docker images (#1391) · eeb368ed
      Egor_P authored
      * add ghw and scripts for docker image deployment
      
      * debug
      
      * add permissions for content
      
      * fix path to the bin folder
      
      * add tags
      
      * rename env
      
      * fix path to docker file
      
      * make polkadot-parachain executable
      
      * fix typo
      
      * fix more typos
      
      * test
      
      * revert back  use of  working directory
      
      * mke bin executable in the artifacts folder
      
      * use cd instead of working directory
      
      * change path to cash
      
      * fix path to cash
      
      * change cache key
      
      * delete old flows
      
      * addressed PR comments
      
      * fix path
      
      * reorg docker files
      eeb368ed