setup-java
Our great sponsors
setup-java | upload-artifact | |
---|---|---|
10 | 24 | |
1,429 | 2,886 | |
3.4% | 3.7% | |
6.8 | 8.2 | |
about 10 hours ago | 2 days ago | |
TypeScript | TypeScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
setup-java
- Disable Annotations in Github Actions
-
Using Github Actions to publish your Flutter APP to Firebase App Distribution
Then, we have two important initial steps to define. The first one is an official GitHub Action used to check-out a repository so a workflow can access it. The second one it's pretty more complex but, briefly, downloads and set up a requested version of Java.
-
Top 10 GitHub Actions You Should Use to set up your CI/CD Pipeline
The most popular ones are Node.js, Python, Java JDK, Go, .Net Core SDK.
-
My summary of jPrime 2022
Finally, note that the v2 of setup-java GitHub Action limits the possible JDK distributions to four options. If you need to use one that is not listed, use foojayio/setup-java instead to configure any distribution.
-
Upgrade to Gradle JDK 11 on Github Actions
See https://github.com/actions/setup-java for more configuration regarding distribution, version and caching.
-
Github action to download and install Oracle JDK and OpenJDK (including EA) builds.
Why can't Oracle just integrate with https://github.com/actions/setup-java like everyone else?
-
Deploying to GitHub Pages using GitHub Actions
Next up we'll need to add a step to compile our production ready build. For this we can add two new steps, one which configures our Node version to ensure it matches our application, followed by another that runs the necessary commands with npm. Depending on how your application is built you may need to add another step between these to install any sort of required environments such as Python or Java.
-
JaCoCo coverage badges, PR coverage checks, and PR coverage comments, from GitHub Actions
Set up the JDK with the actions/setup-java GitHub Action.
-
JDK 17 First Release-Candidate Build Released #TestItNow
It now works (as of yesterday) with Github Actions via https://github.com/actions/setup-java and setting the distribution to temurin.
-
Hosting Kotlin/JS on GitHub Pages via GitHub Actions
The Kotlin compiler needs Java to be present, so we use a predefined GitHub Action to install Java 1.8.
upload-artifact
-
Learning GitHub Actions in a Simple Way
upload-artifact
-
GitHub Actions for Jar file deployment
Here, the concept of "upload" is a little confusing. What the GitHub action upload-artifact does is to "copy" the jar file to a publicly accessible folder.
-
CI/CI deploy a static website to AWS S3 bucket through Github Actions
The content of the build destination folder folder needs is saved and transferred to the following jobs in the workflow. We do this with the Github actions actions/upload-artifact
- You've used 100% of included services for GitHub Storage
-
Building project docs for GitHub Pages
The action for uploading the artifact doesn't do too much, but it takes care of all the nuance around GitHub Pages artifacts specifically. You can view the action's source here. It will tar the path (provided by the with option) and then call the upload artifact action. The artifact's name is github-pages and has a 1 day expiration. This artifact has the name and format required for the deploy action. It all just works (so far).
-
A guide to using act with GitHub Actions
➜ getting-started-with-act git:(master) act -j build WARN ⚠ You are using Apple M1 chip and you have not specified container architecture, you might encounter issues while running act. If so, try running it with '--container-architecture linux/amd64'. ⚠ [Node.js CI/build] 🚀 Start image=node:16-buster-slim [Node.js CI/build] 🐳 docker pull image=node:16-buster-slim platform= username= forcePull=false [Node.js CI/build] 🐳 docker create image=node:16-buster-slim platform= entrypoint=["tail" "-f" "/dev/null"] cmd=[] [Node.js CI/build] 🐳 docker run image=node:16-buster-slim platform= entrypoint=["tail" "-f" "/dev/null"] cmd=[] [Node.js CI/build] ☁ git clone 'https://github.com/actions/setup-node' # ref=v3 [Node.js CI/build] ☁ git clone 'https://github.com/actions/cache' # ref=v3 [Node.js CI/build] ☁ git clone 'https://github.com/actions/upload-artifact' # ref=v3 [Node.js CI/build] ⭐ Run Main actions/checkout@v3 [Node.js CI/build] 🐳 docker cp src=/Users/andrewevans/Documents/projects/getting-started-with-act/. dst=/Users/andrewevans/Documents/projects/getting-started-with-act [Node.js CI/build] ✅ Success - Main actions/checkout@v3 [Node.js CI/build] ⭐ Run Main Use Node.js 16.x [Node.js CI/build] 🐳 docker cp src=/Users/andrewevans/.cache/act/actions-setup-node@v3/ dst=/var/run/act/actions/actions-setup-node@v3/ [Node.js CI/build] 🐳 docker exec cmd=[node /var/run/act/actions/actions-setup-node@v3/dist/setup/index.js] user= workdir= [Node.js CI/build] 💬 ::debug::isExplicit: [Node.js CI/build] 💬 ::debug::explicit? false
-
Using Github Actions to publish your Flutter APP to Firebase App Distribution
Notice that already known commands like flutter pub get and flutter build apk (apk in case of Android; aab in case of iOS) now it shows up on our workflow. But, to upload the generated app file (artifact), we'll need to use the action upload-artifact@v1 and parse the build path which it will be storing the app file.
- github action para deploy de app vuejs 3
-
How do I write the GitHub release workflow for multiple OSs?
So the uploading will likely be done by upload artifact. Then you'll likely want to use a matrix build/package your tool across different OS's.
-
Automate Android Build Using GitHub Actions
Artifacts are files like APKs, screenshots, test reports, logs, which the workflow generates. You can upload and download artifacts to the current workflow using actions/upload-artifact@v2 and actions/download-artifact@v2 respectively.
What are some alternatives?
fetch-api-data-action - 🚚 GitHub action for handling authenticated API requests, allowing you to save the data from the request into your workspace as an environment variable and a .json file.
cache - Cache dependencies and build outputs in GitHub Actions
jacoco-badge-generator - Coverage badges, and pull request coverage checks, from JaCoCo reports in GitHub Actions
Chips-n-Salsa - A Java library of Customizable, Hybridizable, Iterative, Parallel, Stochastic, and Self-Adaptive Local Search Algorithms
publish-unit-test-result-action - GitHub Action to publish unit test results on GitHub
checkout - Action for checking out a repo
flutter-action - Flutter environment for use in GitHub Actions. It works on Linux, Windows, and macOS.
Firebase-Distribution-Github-Action - This action uploads artifacts (.apk or .ipa) to Firebase App Distribution.
github-action-sanity
setup-java - Set up your GitHub Actions workflow with a specific version of Java
metadata-action - GitHub Action to extract metadata (tags, labels) from Git reference and GitHub events for Docker