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

fix: gradle tasks from different subproject are not isolated #337

Open
wants to merge 15 commits into
base: main
Choose a base branch
from

Conversation

ata-nas
Copy link
Contributor

@ata-nas ata-nas commented Nov 12, 2024

Description:

Isolate gradle tasks to not go outside of the respective project's build root.

Related issue(s):

Fixes #299

Notes for reviewer:

  • am I missing something?

Checklist

  • Documented (Code comments, README, etc.)
  • Tested (unit, integration, etc.)

@ata-nas ata-nas added Bug A error that causes the feature to behave differently than what was expected based on design docs Block Node Issues/PR related to the Block Node. labels Nov 12, 2024
@ata-nas ata-nas added this to the 0.3.0 milestone Nov 12, 2024
@ata-nas ata-nas self-assigned this Nov 12, 2024
@ata-nas ata-nas linked an issue Nov 12, 2024 that may be closed by this pull request
@ata-nas ata-nas changed the title bug: gradle tasks from different subproject are not isolated fix: gradle tasks from different subproject are not isolated Nov 12, 2024
@ata-nas ata-nas marked this pull request as ready for review November 12, 2024 12:38
@ata-nas ata-nas requested review from a team as code owners November 12, 2024 12:38
@ata-nas ata-nas force-pushed the 299-bug-gradle-tasks-from-different-subproject-are-not-isolated branch from e3e75cc to 66d7417 Compare November 13, 2024 07:53
@ata-nas ata-nas requested a review from a team as a code owner November 13, 2024 12:12
@ata-nas ata-nas marked this pull request as draft November 13, 2024 12:25
@ata-nas ata-nas marked this pull request as ready for review November 13, 2024 14:39
mishomihov00
mishomihov00 previously approved these changes Nov 14, 2024
Copy link
Contributor

@mishomihov00 mishomihov00 left a comment

Choose a reason for hiding this comment

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

Reviewed and approved only these files:
.github/workflows/e2e-tests.yaml
.github/workflows/smoke-test.yaml
server/docker/docker-build.sh
server/docker/docker-compose.yml
server/docker/update-env.sh

mishomihov00
mishomihov00 previously approved these changes Nov 14, 2024
Copy link
Contributor

@mishomihov00 mishomihov00 left a comment

Choose a reason for hiding this comment

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

Reviewed and approved only these files:
.github/workflows/e2e-tests.yaml
.github/workflows/smoke-test.yaml
server/docker/docker-build.sh
server/docker/docker-compose.yml
server/docker/update-env.sh

georgi-l95
georgi-l95 previously approved these changes Nov 14, 2024
Copy link
Contributor

@georgi-l95 georgi-l95 left a comment

Choose a reason for hiding this comment

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

👁️ 👍 👉 👨‍💻

jeromy-cannon
jeromy-cannon previously approved these changes Nov 18, 2024
Copy link
Contributor

@rbarkerSL rbarkerSL left a comment

Choose a reason for hiding this comment

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

One small nit


tasks.register<Exec>("startDockerContainer") {
description = "Starts the docker container of the Block Node Server of the current version"
description =
"Starts the docker productiongit a container of the Block Node Server for the current version"
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
"Starts the docker productiongit a container of the Block Node Server for the current version"
"Starts the docker production container of the Block Node Server for the current version"

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@rbarkerSL thanks, I have missed that typo. This is pushed.

@ata-nas ata-nas force-pushed the 299-bug-gradle-tasks-from-different-subproject-are-not-isolated branch from 4afe757 to a8df065 Compare November 18, 2024 15:56
Signed-off-by: Atanas Atanasov <[email protected]>
Copy link

codecov bot commented Nov 18, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 94.05%. Comparing base (256d486) to head (0dc75b4).

Additional details and impacted files
@@            Coverage Diff            @@
##               main     #337   +/-   ##
=========================================
  Coverage     94.05%   94.05%           
  Complexity      300      300           
=========================================
  Files            68       68           
  Lines          1177     1177           
  Branches         82       82           
=========================================
  Hits           1107     1107           
  Misses           57       57           
  Partials         13       13           
---- 🚨 Try these New Features:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Block Node Issues/PR related to the Block Node. Bug A error that causes the feature to behave differently than what was expected based on design docs
Projects
None yet
Development

Successfully merging this pull request may close these issues.

fix: gradle tasks from different subproject are not isolated
6 participants