Skip to content
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

Adding in Mumbai/Mainnet precursor deb packaging for tests to use dur… #590

Merged
merged 6 commits into from
Nov 23, 2022

Conversation

djpolygon
Copy link
Contributor

@djpolygon djpolygon commented Nov 22, 2022

…ing upgrade(iterations to come)

Description

Please provide a detailed description of what was done in this PR

Changes

  • Bugfix (non-breaking change that solves an issue)
  • Hotfix (change that solves an urgent issue, and requires immediate attention)
  • [ d] New feature (non-breaking change that adds functionality)
  • Breaking change (change that is not backwards-compatible and/or changes current functionality)

Breaking changes

This change implements packaging for .deb and introduces profile concepts for installing for auto creating sentry nodes/validators. These packages rely on new hosts to be used on peers.

Checklist

  • I have added at least 2 reviewer or the whole pos-v1 team
  • I have added sufficient documentation in code
  • I will be resolving comments - if any - by pushing each fix in a separate commit and linking the commit hash in the comment reply

Cross repository changes

  • [ x] This PR requires changes to heimdall
  • This PR requires changes to matic-cli
    • In case link the PR here:

Testing

  • I have added unit tests
  • I have added tests to CI
  • I have tested this code manually on local environment
  • I have tested this code manually on remote devnet using express-cli
  • [x ] I have tested this code manually on mumbai
  • I have created new e2e tests into express-cli

Manual tests

Please complete this section with the steps you performed if you ran manual tests for this functionality, otherwise delete it

Additional comments

These tooling changes are per posv1 changes for the migration to more standardized debian packages. Other tooling changes will be in subsequent changes for clean up, rpm addition, and other packaging.

@codecov-commenter
Copy link

codecov-commenter commented Nov 22, 2022

Codecov Report

Base: 56.84% // Head: 56.84% // No change to project coverage 👍

Coverage data is based on head (e468e96) compared to base (e468e96).
Patch has no changes to coverable lines.

❗ Current head e468e96 differs from pull request most recent head 3b6c9b0. Consider uploading reports for the commit 3b6c9b0 to get more accurate results

Additional details and impacted files
@@           Coverage Diff           @@
##               qa     #590   +/-   ##
=======================================
  Coverage   56.84%   56.84%           
=======================================
  Files         598      598           
  Lines       69210    69210           
=======================================
  Hits        39341    39341           
  Misses      26514    26514           
  Partials     3355     3355           

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

Comment on lines 5 to 8
branches:
- 'main'
paths:
- '**'
Copy link
Contributor

Choose a reason for hiding this comment

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

These two are unnecessary I guess? We only need it the packager to run when new tags are created.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Removed

run: rm -rf lib/systemd/system/bor.service

- name: Creating package for binary only bor
run: cp -rp packaging/deb/bor packaging/deb/bor-v0.3.0-beta-amd64
Copy link
Contributor

Choose a reason for hiding this comment

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

It would be better to parameterize the version (v0.3.0) accordingly to the tag here, so we don't need to change it in multiple places when a new version is released in the future. I am okay with changing this in the future.

@@ -0,0 +1,36 @@
[Unit]
Copy link
Contributor

Choose a reason for hiding this comment

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

This file doesn't seem to be used anywhere else. Let's remove it if not used.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Updated and removed

- name: Confirming package built
run: ls -ltr packaging/deb/ | grep bor

- name: Release bor Packages
Copy link
Contributor

Choose a reason for hiding this comment

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

Can we make it a pre-release? A manual review is needed before actually releasing it.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

added


- name: Confirming package built
run: ls -ltr packaging/deb/ | grep bor

Copy link
Contributor

Choose a reason for hiding this comment

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

Do we plan to release rpm packages using alien?

@@ -0,0 +1,318 @@
name: packager
Copy link
Contributor

Choose a reason for hiding this comment

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

With packager.yml being added, we need to disable the release of gorelease in this line here. Otherwise, both workflows will try to create the same release.

go-version: 1.19
- name: Generate release tag
id: tag
run: echo "::set-output name=release_tag::bor_$(date +"%Y.%m.%d_%H-%M")"
Copy link
Contributor

Choose a reason for hiding this comment

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

The release name should match the release tag exactly (no date/time info should be included), as what we've been doing in the past: https://github.com/maticnetwork/bor/releases/

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Updated and now using tag

@gonVR gonVR requested a review from ssandeep November 23, 2022 09:51
@djpolygon djpolygon changed the base branch from develop to qa November 23, 2022 15:31
@djpolygon djpolygon merged commit 01e05cd into qa Nov 23, 2022
@djpolygon djpolygon deleted the djpolygon/v0.3.0packaging branch November 23, 2022 19:36
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.

4 participants