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

Feat/assertor release workflow #12662

Closed
wants to merge 14 commits into from

Conversation

tosettil-polimi
Copy link
Collaborator

@tosettil-polimi tosettil-polimi commented Nov 7, 2024

Assertor Release Workflow

Description

This pull request introduces several improvements to the CI/CD workflow for the Erigon project:

  1. Generalized CI/CD Workflow: The existing CI/CD workflow has been refactored to work with any branch, not just the main branch. This allows for more flexible release management, where new versions can be built and tested on different branches before being promoted to main.

  2. Pectra Assertor Tests: A new configuration file (config-pectra.properties) has been added to run the Pectra Assertor tests as part of the Kurtosis-based integration testing. These tests can be enabled for the release/2.61 branch.

Changes

The key changes in this pull request include:

  1. Modifying the ci-cd-main-branch-docker-images.yml workflow to work with any branch, not just main.
  2. Adding a new config-pectra.properties file for running Pectra Assertor tests.
  3. Updating the Dockerfile.release to use the new branch-agnostic Docker build targets.

These changes will improve the overall release management and testing processes for the Erigon project, making it more flexible and robust.

Copy link
Collaborator

@Perlets9 Perlets9 left a comment

Choose a reason for hiding this comment

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

@tosettil-polimi To avoid potential issues with the new releases of Erigon 3 and to ensure compatibility with future versions of Erigon 2, it would be better to create a new workflow instead of modifying the existing one.
The target branch should be release/2.61.

@tosettil-polimi tosettil-polimi deleted the feat/assertor-release-workflow branch November 7, 2024 16:46
@AskAlexSharov AskAlexSharov added this to the 3.0.0-alpha6 milestone Nov 8, 2024
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