difftreelog
Merge pull request #461 from lzadjsf/ci-build-workflow-v3
in: master
CI, step 1
12 files changed
.docker/Dockerfile-chain-devdiffbeforeafterbothno changes
.docker/Dockerfile-parachaindiffbeforeafterbothno changes
.docker/docker-compose-dev.yamldiffbeforeafterbothno changes
.docker/docker-compose.tmp.j2diffbeforeafterbothno changes
.dockerignorediffbeforeafterboth1.git/1.git/2.github/2.github/3.docker/3doc/4doc/4target/5target/5tests/6tests/.github/workflows/codestyle.ymldiffbeforeafterboth1name: Code style1name: Code style223on: [push]3on:4 pull_request:5 branches:6 - develop7 types:8 - opened9 - reopened10 - synchronize4115jobs:12jobs:6 rustfmt:13 rustfmt:7 runs-on: ubuntu-20.0414 runs-on: self-hosted-ci8159 steps:16 steps:17 - name: Skip if pull request is in Draft18 # `if: github.event.pull_request.draft == true` should be kept here, at19 # the step level, rather than at the job level. The latter is not20 # recommended because when the PR is moved from "Draft" to "Ready to21 # review" the workflow will immediately be passing (since it was skipped),22 # even though it hasn't actually ran, since it takes a few seconds for23 # the workflow to start. This is also disclosed in:24 # https://github.community/t/dont-run-actions-on-draft-pull-requests/16817/1725 # That scenario would open an opportunity for the check to be bypassed:26 # 1. Get your PR approved27 # 2. Move it to Draft28 # 3. Push whatever commits you want29 # 4. Move it to "Ready for review"; now the workflow is passing (it was30 # skipped) and "Check reviews" is also passing (it won't be updated31 # until the workflow is finished)32 if: github.event.pull_request.draft == true33 run: exit 13410 - uses: actions/checkout@v135 - uses: actions/checkout@v111 - name: Install latest nightly36 - name: Install latest nightly204521 clippy:46 clippy:22 if: ${{ false }}47 if: ${{ false }}23 runs-on: ubuntu-20.0448 runs-on: self-hosted-ci244925 steps:50 steps:51 - name: Skip if pull request is in Draft52 # `if: github.event.pull_request.draft == true` should be kept here, at53 # the step level, rather than at the job level. The latter is not54 # recommended because when the PR is moved from "Draft" to "Ready to55 # review" the workflow will immediately be passing (since it was skipped),56 # even though it hasn't actually ran, since it takes a few seconds for57 # the workflow to start. This is also disclosed in:58 # https://github.community/t/dont-run-actions-on-draft-pull-requests/16817/1759 # That scenario would open an opportunity for the check to be bypassed:60 # 1. Get your PR approved61 # 2. Move it to Draft62 # 3. Push whatever commits you want63 # 4. Move it to "Ready for review"; now the workflow is passing (it was64 # skipped) and "Check reviews" is also passing (it won't be updated65 # until the workflow is finished)66 if: github.event.pull_request.draft == true67 run: exit 168 26 - uses: actions/checkout@v169 - uses: actions/checkout@v327 - name: Install substrate dependencies70 - name: Install substrate dependencies28 run: sudo apt-get install libssl-dev pkg-config libclang-dev clang71 run: sudo apt-get install libssl-dev pkg-config libclang-dev clang29 - name: Install latest nightly72 - name: Install latest nightly.github/workflows/node_build_test.ymldiffbeforeafterboth1name: Build & test1name: Develop - Build & test223# Controls when the action will run. 3# Controls when the action will run.4on:4on:5 # Triggers the workflow on push or pull request events but only for the master branch5 # Triggers the workflow on push or pull request events but only for the master branch6 push:6 pull_request:7 branches: [ develop ]7 branches:8 # pull_request:8 - develop9 # branches: [ develop ]9 types:10 - opened11 - reopened12 - synchronize #commit(s) pushed to the pull request1310 # Allows you to run this workflow manually from the Actions tab14 # Allows you to run this workflow manually from the Actions tab11 workflow_dispatch:15 workflow_dispatch:121613# A workflow run is made up of one or more jobs that can run sequentially or in parallel17#Define Workflow variables18env:19 RUST_TOOLCHAIN: nightly-2022-05-1120 REPO_URL: ${{ github.server_url }}/${{ github.repository }}21 POLKA_VERSION: release-v0.9.242223# A workflow run is made up of one or more jobs that can run sequentially or in parallel14jobs:24jobs:15 build:25 build:16 # The type of runner that the job will run on26 # The type of runner that the job will run on17 runs-on: ubuntu-20.0427 runs-on: self-hosted-ci182819 # if: github.event_name == 'pull_request' && github.event.action == 'closed' && github.event.pull_request.merged == true29 name: Build Container, Spin it Up an test203021 # Steps represent a sequence of tasks that will be executed as part of the job31 continue-on-error: false #Do not stop testing of matrix runs failed. As it decided during PR review - it required 50/50& Let's check it with false.3233 strategy:34 matrix:35 include:36 - network: "Opal"37 features: "--features=opal-runtime"38 - network: "Quartz"39 features: "--features=quartz-runtime"40 - network: "Unique"41 features: "--features=unique-runtime"4222 steps:43 steps:44 - name: Skip if pull request is in Draft45 # `if: github.event.pull_request.draft == true` should be kept here, at46 # the step level, rather than at the job level. The latter is not47 # recommended because when the PR is moved from "Draft" to "Ready to48 # review" the workflow will immediately be passing (since it was skipped),49 # even though it hasn't actually ran, since it takes a few seconds for50 # the workflow to start. This is also disclosed in:51 # https://github.community/t/dont-run-actions-on-draft-pull-requests/16817/1752 # That scenario would open an opportunity for the check to be bypassed:53 # 1. Get your PR approved54 # 2. Move it to Draft55 # 3. Push whatever commits you want56 # 4. Move it to "Ready for review"; now the workflow is passing (it was57 # skipped) and "Check reviews" is also passing (it won't be updated58 # until the workflow is finished)59 if: github.event.pull_request.draft == true60 run: exit 16123 # Checks-out your repository under $GITHUB_WORKSPACE, so your job can access it62 # Checks-out your repository under $GITHUB_WORKSPACE, so your job can access it24 - uses: actions/checkout@v263 - uses: actions/checkout@v325 64 with:26 #runs ssh connection65 ref: ${{ github.head_ref }} #Checking out head commit6667 - name: Generate ENV related extend file for docker-compose68 uses: cuchi/jinja2-action@v1.2.069 with:70 template: .docker/docker-compose.tmp.j271 output_file: .docker/docker-compose.${{ matrix.network }}.yml72 variables: |73 REPO_URL=${{ github.server_url }}/${{ github.repository }}.git74 RUST_TOOLCHAIN=${{ env.RUST_TOOLCHAIN }}75 POLKA_VERSION=${{ env.POLKA_VERSION }}76 FEATURE='${{ matrix.features }}'77 BRANCH=${{ github.head_ref }}7879 - name: Show build configuration80 run: cat .docker/docker-compose.${{ matrix.network }}.yml8182 - name: Build the stack83 run: docker-compose -f ".docker/docker-compose-dev.yaml" -f ".docker/docker-compose.${{ matrix.network }}.yml" up -d --build8485 - uses: actions/setup-node@v386 with:87 node-version: 168889 - name: Run tests90 run: |91 cd tests92 yarn install93 yarn add mochawesome94 echo "Ready to start tests"95 node scripts/readyness.js96 NOW=$(date +%s) && yarn test --reporter mochawesome --reporter-options reportFilename=test-${NOW}97 env:98 RPC_URL: http://127.0.0.1:9933/9927 - name: Go to server100 - name: Test Report28 uses: appleboy/ssh-action@master101 uses: phoenix-actions/test-reporting@v8102 if: success() || failure() # run this step even if previous step failed29 with:103 with:30 host: ${{ secrets.SERVER_IP }}31 username: ${{ secrets.SERVER_USERNAME }}104 name: Tests ${{ matrix.network }} # Name of the check run which will be created32 key: ${{ secrets.KEY }}105 path: tests/mochawesome-report/test-*.json # Path to test results33 port: ${{ secrets.SERVER_PORT }}106 reporter: mochawesome-json34 command_timeout: 300m35 script: |107 fail-on-error: 'false'36 eval $(ssh-agent -s)10837 ssh-add /home/devops/.ssh/git_hub109 - name: Read output variables38 git clone git@github.com:UniqueNetwork/unique-chain.git110 run: |39 cd unique-chain111 echo "url is ${{ steps.test-report.outputs.runHtmlUrl }}"40 git checkout develop11241 # git pull --all113 - name: Stop running containers42 chmod +x ci_node.sh114 if: always() # run this step always43 ./ci_node.sh115 run: docker-compose -f ".docker/docker-compose-dev.yaml" -f ".docker/docker-compose.${{ matrix.network }}.yml" down44 rm -rf /home/polkadot/unique-chain45116.github/workflows/notify.ymldiffbeforeafterbothno changes
.github/workflows/tests_codestyle.ymldiffbeforeafterboth1name: Tests code style1name: Tests code style223on: [push]3on:44 pull_request:5 branches:6 - develop7 types:8 - opened9 - reopened10 - synchronize5jobs:11jobs:6 build:12 build:7 runs-on: ubuntu-20.0413 runs-on: self-hosted-ci8149 steps:15 steps:16 - name: Skip if pull request is in Draft17 # `if: github.event.pull_request.draft == true` should be kept here, at18 # the step level, rather than at the job level. The latter is not19 # recommended because when the PR is moved from "Draft" to "Ready to20 # review" the workflow will immediately be passing (since it was skipped),21 # even though it hasn't actually ran, since it takes a few seconds for22 # the workflow to start. This is also disclosed in:23 # https://github.community/t/dont-run-actions-on-draft-pull-requests/16817/1724 # That scenario would open an opportunity for the check to be bypassed:25 # 1. Get your PR approved26 # 2. Move it to Draft27 # 3. Push whatever commits you want28 # 4. Move it to "Ready for review"; now the workflow is passing (it was29 # skipped) and "Check reviews" is also passing (it won't be updated30 # until the workflow is finished)31 if: github.event.pull_request.draft == true32 run: exit 13310 - uses: actions/checkout@v234 - uses: actions/checkout@v33536 - uses: actions/setup-node@v337 with:38 node-version: 163911 - name: Install modules40 - name: Install modules12 run: cd tests && yarn41 run: cd tests && yarnDockerfile-parachaindiffbeforeafterbothno changes
docker-compose-tests-parachain.ymldiffbeforeafterbothno changes
tests/scripts/readyness.jsdiffbeforeafterbothno changes