Skip to content

Fail build when unittests fail for PRs #60

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

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

Conversation

BertScholten
Copy link
Member

Be more strict on failing tests for PRs, to avoid missing a failing test before merging.

@BertScholten BertScholten requested review from Hilbrand and SerhatG April 7, 2025 10:12
Copy link
Member

@Hilbrand Hilbrand left a comment

Choose a reason for hiding this comment

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

LGTM

Be more strict on failing tests for PRs, to avoid missing a failing test before merging.
@BertScholten BertScholten force-pushed the fail_pr_build_when_tests_fail branch from 49ad3b6 to 068ce32 Compare April 7, 2025 10:16
Not sure what the idea was behind not publishing the service and its dependencies, but it's causing the code not to be compiled/tested when building the PR. And these should be published to nexus anyway I think?
@BertScholten BertScholten requested a review from Hilbrand April 7, 2025 10:30
@BertScholten
Copy link
Member Author

Apparantly the service modules were never tested with PR builds. Not sure if this is the correct change (I think putting the service jars in Nexus makes sense, but there might be other reasons why this shouldn't be done?), or if we should change the action to not use publish as profile.

@SerhatG
Copy link
Member

SerhatG commented Apr 8, 2025

The reasoning was that only the client parts are used by other projects. The service parts are never used by others.
What we might do is make a two step approach. Do unittests on everything, but only push the client parts.

As a little bonus this also allows us to do the Docker part before the Maven Publish part, so that if the Docker images fail to build, it won't have pushed the client libraries.

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