Set up Github Actions pipeline for PRs #8680
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
elliedori
changed the title
spring-projects-issues
added
the
status: waiting-for-triage
elliedori
commented
Jun 10, 2020
elliedori
force-pushed
the
github-actions-pr-pipeline
branch
from
5668666
to
e213e64
Compare
rwinch
approved these changes
Jun 16, 2020
rwinch
added
in: build
Closed
elliedori
added a commit
that referenced
this pull request
Jun 17, 2020
elliedori
added a commit
to elliedori/spring-security
that referenced
this pull request
Jun 17, 2020
rwinch
pushed a commit
that referenced
this pull request
Jun 17, 2020
This was referenced Jun 17, 2020
elliedori
added
the
status: backported
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Context
We want to migrate our build pipelines to Github Actions for consistency and ease of use.
Solution
Created Github Actions build pipeline for PR requests. This is includes setting up the appropriate JDK, caching Gradle dependencies, and running a Gradle clean build. I've confirmed that the pipeline runs correctly against my forked version of spring-security.