Skip to content

Conversation

@ggera
Copy link
Member

@ggera ggera commented Jun 9, 2022

NO TICKET

Checklist:

  • I have verified that the code works
    • No panics! (checked arithmetic ops, no indexing array[3] use get(3), ...)
  • I have verified that the code is easy to understand
    • If not, I have left a well-balanced amount of inline comments
  • I have left the code in a better state
  • I have documented the changes (where applicable)

@ggera ggera requested a review from wischli June 9, 2022 15:54
@ggera
Copy link
Member Author

ggera commented Jun 9, 2022

Dockerfile Outdated

# c4f0daf3-20220110 -> rust version rustc 1.58.0-nightly (46b8e7488 2021-11-07)
FROM paritytech/ci-linux:f203f298-20220421 as builder
FROM docker.io/paritytech/ci-linux:production as builder
Copy link
Contributor

@wischli wischli Jun 9, 2022

Choose a reason for hiding this comment

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

I fear that the production image will be bumped up by Parity while we want to have full control over bumping the image to reduce error likelihood when building.

I suggest to stay with a distinct hash. The one suggested has the same digest as the current production one, e.g., they are the same.

Suggested change
FROM docker.io/paritytech/ci-linux:production as builder
FROM paritytech/ci-linux:eb1f6a26-20220518

Copy link
Member Author

@ggera ggera Jun 10, 2022

Choose a reason for hiding this comment

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

Yup, I was kinda puzzled. Since the toolchain file has precedence over the docker image, we kinda have no control.

Copy link
Contributor

@wischli wischli left a comment

Choose a reason for hiding this comment

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

LGTM

@wischli wischli enabled auto-merge (squash) June 13, 2022 11:54
@wischli wischli merged commit 4834987 into develop Jun 13, 2022
@wischli wischli deleted the ci-linux branch June 13, 2022 12:44
ntn-x2 pushed a commit that referenced this pull request Jun 23, 2022
* use ci-linx:production base image

* Use hash tag on ci-linux to have more control than latest production

Co-authored-by: William Freudenberger <[email protected]>
(cherry picked from commit 4834987)
ntn-x2 added a commit that referenced this pull request Jun 24, 2022
* Adds two more relaychain bootnodes for staging environment  (#334)

* chore: reset peregrine stg (#335)

* ci: use custom ci image (#336)

* Optimizes docker layer (#337)

* fix: add did lookup pallet to DID authorization logic + reverse lookup index (#343)

* chore: update toolchain version to nightly 1.59 (#339)

* feat: proxy type for disableling deposit claiming (#341)

* fix: rococo protocol id (#369)

* feat: generic access control (#316)

* Updates toolchain version (#345)

* refactor: enforce no runtime in pallet (#349)

* fix: features (#353)

* feat: add tips pallet (#352)

* feat: upgrade to Polkadot v0.9.19 (#357)

* chore: upgrade and clean up (#360)

* Adds the new rococo chainspec (#363)

* feat: add launch pallet removal migration (#359)

* refactor: update rilt para id from 2015 to 2108 (#364)

* fix: rilt para id (#365)

* feat: upgrade to Polkadot v0.9.23 (#366)

* use ci-linx:production base image (#368)

* feat: upgrade to Polkadot v0.9.24 (#370)

* fix: fix CI builders compilation errors and pin to a specific hash (#372)
@ntn-x2 ntn-x2 changed the title use ci-linx:production base image use ci-linux:production base image Jun 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants