-
Notifications
You must be signed in to change notification settings - Fork 529
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
Use new version of deb-s3 for validating job publishing #16305
Conversation
!ci-build-me |
!ci-build-me |
Archive unit tests are failing all the time after updating toolchain: https://buildkite.com/o-1-labs-2/mina-o-1-labs/builds/35968#0192d971-40d3-42ad-8114-4307f749752a due to yet again using different port. I need to fix it in this PR not to introduce regression |
Small update. I created official release for deb-s3 in version 0.11.7 . I will now update PR. CI will use official version |
!ci-build-me |
!ci-build-me |
!approved-for-mainnet |
Used new deb-s3 version with new command (deb-s3 exist) which is capable of verifying existence of more than one packages in Packages file for given codename and component.
@mrmr1993 rightly pointed out that majority of publish packages verification job duration is spent on downloading Packages file (which can take ~ 45 seconds, since file can be up to 60 Mb) for each package. New deb-s3 version is capable to run validation for multiple debs in one go. We are utilizing this new command in publish.sh script.
Output of deb-s3 exist command is multiline tabular string in below format:
We are parsing such output and learning what packages are still missing. Then rerun command for only remaining ones.
We can now observe that publish job duration decreased from ~10+ minutes to only 2 minutes.
Note for reviewers:
I'm using 0.11.7 alpha version for deb-s3, since i didn't want to merge code to master of minaprotocol/deb-s3 repo . Therefore i'm asking to first review this PR along with: MinaProtocol/deb-s3#1
Then I will update this PR to use 0.11.7 version