Skip to content
This repository has been archived by the owner on Nov 15, 2023. It is now read-only.

Move polkadot build check to polkadot and check status in substrate #6706

Closed
wants to merge 37 commits into from

Conversation

cecton
Copy link
Contributor

@cecton cecton commented Jul 22, 2020

More details in paritytech/polkadot#1426

polkadot companion: paritytech/polkadot#1426

cecton and others added 30 commits July 14, 2020 13:50
Forked at: 60e3a69
Parent branch: origin/master
Co-authored-by: Benjamin Kampmann <ben@gnunicorn.org>
This reverts commit 4e15214.
Parent branch: origin/master
Forked at: 4da2926
Parent branch: origin/master
Forked at: 4da2926
Parent branch: origin/master
Forked at: 4da2926
Parent branch: origin/master
Forked at: 4da2926
cecton and others added 3 commits July 21, 2020 18:48
Parent branch: origin/master
Forked at: 4da2926
Co-authored-by: Bastian Köcher <bkchr@users.noreply.github.com>
Parent branch: origin/master
Forked at: 4da2926
@cecton cecton force-pushed the cecton-ignore-test-for-companion branch from a66a759 to 5f07368 Compare July 22, 2020 06:24
Parent branch: origin/master
Forked at: 4da2926
@cecton cecton added B0-silent Changes should not be mentioned in any release notes C1-low PR touches the given topic and has a low impact on builders. labels Jul 22, 2020
@cecton cecton requested a review from TriplEight July 22, 2020 07:23
Parent branch: origin/master
Forked at: 4da2926
@cecton
Copy link
Contributor Author

cecton commented Jul 22, 2020

@TriplEight as you can see now the polkadot-companion-status step fails because the polkadot companion PR has not been approved yet.

(I still need to finish some things in polkadot .gitlab-ci.yml)

Copy link
Contributor

@TriplEight TriplEight left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

CI and bash parts look good!

@cecton
Copy link
Contributor Author

cecton commented Jul 22, 2020

@TriplEight It is almost ready to merge but I won't be able to do it alone:

  1. The build in polkadot must pass. It started failing but I couldn't reproduce it locally. Logs here.
  2. The requirement for continuous-integration/gitlab-check-polkadot-companion-build on GitHub must be removed (as this step has been removed)
  3. I updated the doc but I think it would be best to make an announcement on the channel because with this change, the companion PR must be in the description of the polkadot pr too (both links must be present)

(The reason for 3. is because on substrate it checks the status of the polkadot PR while on Polkadot it needs to know which branch of substrate needs to be used for the build)

@s3krit
Copy link
Contributor

s3krit commented Jul 22, 2020

We should probably also remove or edit .github/workflows/polkadot-companion-labels.yml also - Its current purpose is to monitor the status of the companion-build job and apply a label to the PR if it fails. I get the suspicion it's not actually been that useful an action anyway.

  1. The requirement for continuous-integration/gitlab-check-polkadot-companion-build on GitHub must be removed (as this step has been removed)

We'll need to get someone in the dev-admin team to do this.

@cecton
Copy link
Contributor Author

cecton commented Jul 22, 2020

(Wait before doing so because there is still this problem of Cargo.lock to update in polkadot)

@cecton
Copy link
Contributor Author

cecton commented Jul 22, 2020

I'm closing this PR because after discussion (and checking history) I realized that this solution won't solve the issue I currently have with the companion pr process.

@cecton cecton closed this Jul 22, 2020
@cecton cecton deleted the cecton-ignore-test-for-companion branch July 22, 2020 14:11
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
A0-please_review Pull request needs code review. B0-silent Changes should not be mentioned in any release notes C1-low PR touches the given topic and has a low impact on builders.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants