Add Jenkinsfile for Continuous Integration Setup #22
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request introduces a Jenkinsfile to set up Continuous Integration for the mock-company-webapp repository. The Jenkinsfile includes two main stages: Build and Test.
./gradlew assemble
to compile the application../gradlew test
to ensure code quality and correctness.Additionally, the post-processing steps include:
This CI setup will help maintain code quality by automatically running builds and tests on each commit.
To demonstrate the CI setup, I modified the
SearchService
class to returnCollections.emptyList()
to simulate a failing test case. This change has been validated by confirming that the CI pipeline fails as expected.Please review the changes and let me know if there are any questions or further adjustments needed.