Plugin and mod builds
Push to GitHub, get a jar and a page
FadeHost compiles your Minecraft plugin or mod on every push and puts each build on a public page with its commit, its log and its jars. One link always downloads the newest build. No Jenkins to run, no Actions workflow to write, no release to cut.
- One public repository, free
- Gradle and Maven, JDK 8 to 25
- A page, a badge and a stable link
- Install a build into your server
Already have an account? Open Builds in the panel.
SkyQuests by aurorastudio
- #18a7f3c912 hours agoDownloadSkyQuests-1.4.2.jar412 KB
- #175b0e2d4yesterdayDownloadSkyQuests-1.4.1.jar411 KB
- #169c81f606 days agoDownloadSkyQuests-1.4.0.jar408 KB
Always the newest jar
https://builds.fadehost.net/aurorastudio/SkyQuests/latest/SkyQuests.jar
Who it is for
Anyone whose jar other people download. The service turns a repository into a page, a link and a badge.
Plugin authors
Paper, Spigot, Bukkit, Velocity and BungeeCord projects compile on every push. Testers take the newest jar off the page instead of asking you to build one.
Modpack and mod teams
Fabric, Forge and NeoForge projects build the same way, and a monorepo can connect each mod as its own project with its own page and jar.
Server owners
One link that never goes stale, for your README, your Discord or your wiki. Run a server with us and any build installs into it from the panel.
From a repository to a download link
- 1
Connect the repository
Sign in to the panel, open Builds and paste the GitHub URL of a public Gradle or Maven project. Connecting GitHub takes one click, and the App only needs to read public code. If the project sits in a subdirectory, name it here.
- 2
Push, and it builds
FadeHost watches the branch you connected. With the GitHub App on the repository a push queues a build in seconds; without it the branch is checked every five minutes. You can also start a build by hand from the panel.
- 3
Share the page and the link
The project gets a public page listing every build with its commit, its log and its jars, a link that always downloads the newest one, and a badge for your README.
Two lines in your README
The badge follows your newest build and the link always fetches the newest jar. Copy both from your project page.
[](https://builds.fadehost.net/aurorastudio/SkyQuests/)
[Download the latest build](https://builds.fadehost.net/aurorastudio/SkyQuests/latest/SkyQuests.jar)Neither line ever needs updating, whatever the next jar is called.
What every project gets
The build page every plugin used to need a Jenkins for, plus the parts around it.
Builds on every push
A push to the connected branch queues a build: in seconds through the GitHub App, or within five minutes through the branch check when the App is not installed. A new project gets its first build the same way.
Gradle and Maven
Your wrapper if you ship one, or Gradle 8.4, 8.10, 9.2 and 9.5 and Maven 3.9 from the image. Temurin JDK 8, 11, 17, 21 and 25, picked from your build files or set on the project.
A public build page
builds.fadehost.net/aurorastudio/SkyQuests/ lists every build, newest first, with its status, its commit, when it ran and the files it produced.
A link that never goes stale
One URL always serves the newest successful jar, from a worldwide cache. Paste it once into your README, your Discord or your wiki and never update it again.
A README badge
build: passing, failing or building, drawn by us as a small SVG. Two lines of Markdown, copied from your project page.
Full build logs
Every attempt keeps its log on its own build page, so a contributor who broke the build can read why without asking you, and so can you from your phone.
Older builds stay
A successful build keeps its files for 90 days, and longer while it is one of your ten newest. The newest successful build keeps its files for good, so the stable link never breaks.
Install into a server
FadeHost customers install any build straight into a server from the panel: the jar lands in its plugins or mods folder, ready for the next restart.
Pricing
One public repository builds for free on every account. The Builds add-on costs $2 a month or $20 a year per unit, on the same bill as your servers.
Free builds
$0- One public repository, on the branch you choose
- Ten builds a day, ten minutes each on 4 GB and two cores
- The public page, the badge, the logs and the stable link
- Files kept 90 days, the newest ten builds, 1 GB per project
Builds add-on
$2per unit, per month, or $20 a year- Private repositories, cloned with the FadeHost GitHub App
- Ten projects per unit, up to 25 units on one account
- Your builds go ahead of free builds in the queue
- 50 builds a day, 30 minutes each on 8 GB and four cores
- 500 MB of files per build, a year of history, 20 GB per project
| Free | Add-on, one unit | Each further unit | |
|---|---|---|---|
| Projects | 1, public only | 10, public or private | +10 |
| Builds per project per day | 10 | 50 | +50, up to 1,000 |
| Time per build | 10 minutes | 30 minutes | +10 minutes, up to 90 |
| Memory and CPU | 4 GB, 2 cores | 8 GB, 4 cores | +2 GB and +1 core, up to 16 GB and 6 |
| Files per build | 200 MB | 500 MB | +250 MB, up to 2 GB |
| Files kept | 90 days, newest 10 builds, 1 GB | 1 year, newest 50 builds, 20 GB | +50 builds and +10 GB, up to 100 GB |
| Queue | in order | ahead of free builds | earlier still with every unit |
What a typical setup costs
A public plugin
Free, one public repository
$0
Every push builds, the page and the badge are public, and the newest jar keeps the same link for good.
A private repository with a few projects
Builds, one unit at $2 a month
$2/mo
Private repositories, up to ten projects on the unit, builds ahead of the free queue and every limit in the table above. $20 a year instead, if you pay yearly.
Frequently asked questions
- Why is it free?
- Every README that links to a FadeHost build page introduces us to server owners, which is exactly who we host for. One public repository per account is free to connect, with no ads and no surveys. Private repositories and more projects are the paid part.
- What can I connect?
- Any public GitHub repository that builds with Gradle or Maven and produces a jar: Paper, Spigot and Bukkit plugins, Velocity and BungeeCord plugins, Fabric, Forge and NeoForge mods, and libraries. Monorepos work too: name the subdirectory when you connect.
- How soon after a push does a build start?
- With the FadeHost GitHub App installed on the repository, a push arrives as a webhook and the build is queued within seconds. Without it, FadeHost checks the connected branch every five minutes and queues a build when the branch has moved, which is also how a new project gets its first build. You can start a build by hand from the panel at any time.
- Which build tool and which Java version?
- Gradle or Maven, read from the repository, using your wrapper when you ship one. The image carries Gradle 8.4, 8.10, 9.2 and 9.5, Maven 3.9 and Temurin JDK 8, 11, 17, 21 and 25. The Java version comes from your build files, and you can set the tool and the JDK on the project yourself.
- How is my build isolated?
- Each build runs in a fresh container with no credentials of any kind, capped at 4 GB of memory, two CPU cores and ten minutes on the free tier. Your build scripts never see a token: the repository is cloned by a step that runs no project code, and the jar is uploaded afterwards by another one.
- Do I need a FadeHost server?
- No. A FadeHost account is enough. If you also run a server with us, you get the one-click install on top.
- What about private repositories?
- The Builds add-on, $2 a month or $20 a year per unit, lets you connect private repositories and ten projects per unit, puts your builds ahead of free ones in the queue, and raises every limit: 50 builds a day, 30-minute builds on 8 GB and four cores, 500 MB of files, a year of history and 20 GB per project at one unit, and more with every further unit. Install the FadeHost GitHub App on the repository so we can clone it; the token stays in the clone step and never enters the build container.
- Can I keep the page private?
- Yes. Turn the public page off in the project settings and the page, the badge and the stable link answer 404 while you still see everything in the panel.
- Where is my build page?
- At builds.fadehost.net, under your GitHub name and your repository name. Every jar on it is served from a worldwide cache, so downloads are fast wherever your players are.
- Is there a live example?
- Yes: our own GracefulStop plugin builds through the service, and its build page and README are exactly what yours would look like.
- How long are builds kept?
- Build records and logs stay as long as the repository is connected. A successful build keeps its files for 90 days, or longer while it is one of your project's ten newest successful builds, and the newest successful build always keeps its files, so the stable link never breaks. Files from a build that did not succeed go after a day. A project holds 1 GB of files on the free tier and 20 GB on one unit of the add-on; past that the oldest files go first. Disconnecting a project removes its builds and its files.
Free for one public repository. No card, and no server needed.
Read on
builds.fadehost.net
The public build pages themselves, with the projects that build here and their jars.
App hosting
Run an app or a bot from the same GitHub repository, redeployed on every push.
Installing plugins
How a jar gets into a server's plugins folder and what to check when it does not load.
Running a custom jar
Upload a jar you built yourself, turn on Custom JAR and pick the Java version it needs.