modloom.

Guides

Builds and downloads

How builds run, where to find logs, and how to get the jar.

A build compiles your project into plugin.jar.

How a build runs#

Builds run in an isolated sandbox using Maven (clean package, tests skipped). A build has a hard limit of about five minutes. If it takes longer it is stopped and reported as a timeout.

When Maven finishes, Modloom checks the result before it offers a download:

  • the jar must contain a plugin.yml,
  • it must contain at least one compiled Java class,
  • it is only registered if your source did not change while the build ran.

A build that fails these checks is marked failed, even if Maven printed a jar.

Build runs and manual builds#

There are two ways to build.

  • As part of a Build run. The agent builds and fixes errors by itself. A Build run does not finish as successful unless the final source built successfully.
  • Manually. Press Build plugin in the Build panel. This compiles the current files with no model involved, so it spends build minutes but no credits. Use it after editing code yourself.

Finding logs#

The Build tab of the activity panel shows a history of builds for the project. Select one to see its Maven log, its status and its download.

Statuses are:

  • Running: the build is in progress.
  • Succeeded: a jar is available.
  • Failed: compile errors or a check failed. Read the log.
  • Interrupted: the build was stopped before it finished.

The Builds page in the sidebar lists your most recent builds across all projects, 25 per page, with a download for each successful one.

Downloading#

Press Download on a successful build. The jar is delivered over a short-lived private link and verified before it is served, so a download is always the exact file that was built.

Build minutes#

Compile time counts against your plan's build minutes each week. A build that times out is not charged. If you run out, Build runs and manual builds are blocked until the weekly reset, but you can still plan. See Plans and limits.

When a build fails#

Read the log from the bottom. The first ERROR line is usually the real cause. Then:

  1. Ask the agent to fix it, and paste the key lines if it does not see them.
  2. Check the engine and version target. A mismatch can cause missing classes.
  3. See Troubleshooting.