-
Notifications
You must be signed in to change notification settings - Fork 279
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[suggestion] [ci] improve iroha2 build #2461
Comments
A few corrections, we should never push a non-iroha image into a separate tag, instead we fought hard and won an image called |
Also we have to decide what to do with |
There are a two ways to avoid it:
iroha2-dev-pr.yaml
iroha2-dev.yaml
|
This is weird. I suppose that there is not a problem in secrets due iroha1 uses the same credentials for dockerhub account, and there are no an errors from iroha1 pushing images. May be try to come back to |
It seems like |
Closed as main topics were resolved by #2576. |
Signed-off-by: BAStos525 jungle.vas@yandex.ru Co-authored-by: Ekaterina Mekhnetsova <mekkatya@gmail.com> Co-authored-by: 6r1d <vic.6r1d@gmail.com>
Signed-off-by: BAStos525 jungle.vas@yandex.ru Co-authored-by: Ekaterina Mekhnetsova <mekkatya@gmail.com> Co-authored-by: 6r1d <vic.6r1d@gmail.com>
Signed-off-by: BAStos525 jungle.vas@yandex.ru Co-authored-by: Ekaterina Mekhnetsova <mekkatya@gmail.com> Co-authored-by: 6r1d <vic.6r1d@gmail.com>
Signed-off-by: BAStos525 jungle.vas@yandex.ru Co-authored-by: Ekaterina Mekhnetsova <mekkatya@gmail.com> Co-authored-by: 6r1d <vic.6r1d@gmail.com>
Signed-off-by: BAStos525 jungle.vas@yandex.ru Co-authored-by: Ekaterina Mekhnetsova <mekkatya@gmail.com> Co-authored-by: 6r1d <vic.6r1d@gmail.com> Signed-off-by: BAStos525 <jungle.vas@yandex.ru>
Signed-off-by: BAStos525 jungle.vas@yandex.ru Co-authored-by: Ekaterina Mekhnetsova <mekkatya@gmail.com> Co-authored-by: 6r1d <vic.6r1d@gmail.com>
Signed-off-by: BAStos525 jungle.vas@yandex.ru Co-authored-by: Ekaterina Mekhnetsova <mekkatya@gmail.com> Co-authored-by: 6r1d <vic.6r1d@gmail.com>
Signed-off-by: BAStos525 jungle.vas@yandex.ru Co-authored-by: Ekaterina Mekhnetsova <mekkatya@gmail.com> Co-authored-by: 6r1d <vic.6r1d@gmail.com>
Signed-off-by: BAStos525 jungle.vas@yandex.ru Co-authored-by: Ekaterina Mekhnetsova <mekkatya@gmail.com> Co-authored-by: 6r1d <vic.6r1d@gmail.com> Signed-off-by: BAStos525 <jungle.vas@yandex.ru>
Signed-off-by: BAStos525 jungle.vas@yandex.ru Co-authored-by: Ekaterina Mekhnetsova <mekkatya@gmail.com> Co-authored-by: 6r1d <vic.6r1d@gmail.com>
Signed-off-by: BAStos525 jungle.vas@yandex.ru Co-authored-by: Ekaterina Mekhnetsova <mekkatya@gmail.com> Co-authored-by: 6r1d <vic.6r1d@gmail.com> Signed-off-by: BAStos525 <jungle.vas@yandex.ru>
Feature request
After merging this PR, Soramitsu DevOps team has to improve a couple of things in the iroha2 CI:
iroha2:base
docker image into a dedicated workflow which runs onDockerfile.ci
change, and replace 7272721/i2-ci:latest in .container.image with hyperledger/iroha2:envBuild and push iroha2:dev docker image
foriroha2:dev, iroha2:stable, iroha2:release
images works only asbash
command to build and push the corresponding docker image. For some reason, GH Actiondocker/build-push-action@v3
fails with following error:buildx failed with: error: failed to solve: failed to compute cache key: failed to calculate checksum of ref x8jvn8e81it8h6cbjf205gxgt::u6fgfckzgk3t5lxzms465fgd1: failed to walk /tmp/buildkit-mount878509508/release: lstat /tmp/buildkit-mount878509508/release: no such file or directory
DevOps team could try to resolve this issue if it is possible.
Motivation
To make iroha2 CI faster, more effective and reliable.
Who can help?
@appetrosyan @s8sato
The text was updated successfully, but these errors were encountered: