* Changes to release workflow
- Workflow environment variable changed to RELEASE_VERSION instead of RELEASE_NAME to make it more meaningful
- Workflows draft-release and docker-promote previously trigger workflow container-verify. This can result in trigger is successful but actual verification workflow fails. This will not be reflected in the draft-release and docker-promote workflows. Container verify code is embedded in the draft-release and docker-promote workflows to avoid this confusion
Signed-off-by: Chaminda Divitotawela <cdivitotawela@gmail.com>
* PR comment improvements
Signed-off-by: Chaminda Divitotawela <cdivitotawela@gmail.com>
* Match the only tags starting with word latest for latest check
Signed-off-by: Chaminda Divitotawela <cdivitotawela@gmail.com>
---------
Signed-off-by: Chaminda Divitotawela <cdivitotawela@gmail.com>
Co-authored-by: Simon Dudley <simon.dudley@consensys.net>
Previously GitHub release will be created which triggers building and publishing the artifacts. Release engineers found workflow could fail after the GitHub release created. Community may subscribed to GitHub releases but if the workflow failed, artifacts for the release would not available.
Proposed solution requires release engineer to run a GitHub workflow manually by providing the Git tag which creates a draft GitHub release. During this workflow, release artifacts binary distribution, docker images (not latest), Artifactory jars created and published. Release engineer can update the release notes in draft release and publish the release. At the time when the release is published, release engineer is confident all the artifacts are ready. Upon publishing the release, another workflow is triggered to promote the release version of docker images to latest
Signed-off-by: Chaminda Divitotawela <cdivitotawela@gmail.com>
Co-authored-by: Simon Dudley <simon.dudley@consensys.net>
Implemented support for emptyBlockPeriodSeconds in QBFT (Issue #3810)
Introduces experimental xemptyblockperiodseconds genesis config option for producing empty blocks at a specific interval independently of the value of the existing blockperiodseconds setting.
https://github.com/hyperledger/besu/issues/3810
---------
Signed-off-by: Antonio Mota <antonio.mota@citi.com>
Signed-off-by: amsmota <amsmota@gmail.com>
* Update entrypoint script for Dockerfile to only switch user if its running as root
Signed-off-by: Rafael Matias <rafael@skyle.net>
* make root user check at the beginning
Signed-off-by: Rafael Matias <rafael@skyle.net>
---------
Signed-off-by: Rafael Matias <rafael@skyle.net>
* Dev mode for short BFT block periods
Signed-off-by: Matthew Whitehead <matthew1001@gmail.com>
* Refactoring
Signed-off-by: Matthew Whitehead <matthew1001@gmail.com>
* Fix comment
Signed-off-by: Matthew Whitehead <matthew1001@gmail.com>
* Refactor to make BFT block milliseconds an experimental QBFT config option
Signed-off-by: Matthew Whitehead <matthew1001@gmail.com>
* Update Json BFT config options
Signed-off-by: Matthew Whitehead <matthew1001@gmail.com>
---------
Signed-off-by: Matthew Whitehead <matthew1001@gmail.com>
* Don't persist IBFT2 proposal blocks, just validate them
Signed-off-by: Matthew Whitehead <matthew1001@gmail.com>
* Tidy up changelog
Signed-off-by: Matthew Whitehead <matthew1001@gmail.com>
---------
Signed-off-by: Matthew Whitehead <matthew1001@gmail.com>
Signed-off-by: Matt Whitehead <matthew.whitehead@kaleido.io>
* create separate signature class for code delegations as they have different bound checks
Signed-off-by: Daniel Lehrner <daniel.lehrner@consensys.net>
* test if increasing xmx let's failing acceptance test pass
Signed-off-by: Daniel Lehrner <daniel.lehrner@consensys.net>
* javadoc
Signed-off-by: Sally MacFarlane <macfarla.github@gmail.com>
---------
Signed-off-by: Daniel Lehrner <daniel.lehrner@consensys.net>
Signed-off-by: Sally MacFarlane <macfarla.github@gmail.com>
Co-authored-by: Sally MacFarlane <macfarla.github@gmail.com>
I am no longer aligned with the Governance policies and practices of
LFDT and resign my position as maintainer.
Signed-off-by: Danno Ferrin <danno@numisight.com>
* shift creation of plugin context to BesuCommand for now
* mock component will provide a no-op metrics sys
---------
Signed-off-by: Justin Florentine <justin+github@florentine.us>
* Fix mounted data path directory permissions for besu user
Signed-off-by: Bhanu Pulluri <bhanu.pulluri@kaleido.io>
* Add besu CLI option to output dirs needing permission update
Signed-off-by: Bhanu Pulluri <bhanu.pulluri@kaleido.io>
* run spotless apply to handle PR test failure
Signed-off-by: Bhanu Pulluri <bhanu.pulluri@kaleido.io>
* Remove newly added --print-paths-and-exit option from config file test
This option doesn't have a corresponding config file entry as it's a
standalone option to be used with docker containers
Signed-off-by: Bhanu Pulluri <bhanu.pulluri@kaleido.io>
* Add optional user argument to --print-paths-and-exit and fix directory permissions
Signed-off-by: Bhanu Pulluri <bhanu.pulluri@kaleido.io>
* Correct build.gradle changes, remove a duplicate line and extra whitespaces
Signed-off-by: Bhanu Pulluri <bhanu.pulluri@kaleido.io>
* Fix checking for user in path's group membership
Signed-off-by: Bhanu Pulluri <bhanu.pulluri@kaleido.io>
* Add platform check to restrict --print-paths-and-exit option usage to Linux and Mac
Signed-off-by: Bhanu Pulluri <bhanu.pulluri@kaleido.io>
* Apply suggestions from code review
Co-authored-by: Fabio Di Fabio <fabio.difabio@consensys.net>
Signed-off-by: Bhanu Pulluri <59369753+pullurib@users.noreply.github.com>
---------
Signed-off-by: Bhanu Pulluri <bhanu.pulluri@kaleido.io>
Signed-off-by: Bhanu Pulluri <59369753+pullurib@users.noreply.github.com>
Co-authored-by: Bhanu Pulluri <bhanu.pulluri@kaleido.io>
Co-authored-by: Fabio Di Fabio <fabio.difabio@consensys.net>