WildFly Continuous Deployment on MassiveGRID PaaS
WildFly Continuous Deployment deploys a WildFly application server on MassiveGRID PaaS wired to a Git repository, so every push to the configured branch is pulled, built with Maven and redeployed automatically. It gives Jakarta EE teams a CI/CD loop without a separate build server.
Both buttons open the MassiveGRID PaaS dashboard with WildFly Continuous Deployment pre-selected. The trial needs no credit card.
WildFly Continuous Deployment Package Facts
| Attribute | Value |
|---|---|
| Package | WildFly Continuous Deployment |
| Type | Application (installs a complete environment) |
| Category | DevOps & Admin Tools |
| Software vendor / project | Red Hat (WildFly community project) |
| Licence | LGPLv2.1 (open source) |
| Runtime / stack | WildFly application server with Git-based automatic build and deployment |
| Regions | New York, London, Frankfurt, Singapore |
| Billing | Pay-per-use from $2.46/month ($0.003372/hour), no licence fee |
| Free trial | 14 days, no credit card |
| Uptime SLA | 100% |
What is WildFly Continuous Deployment?
Continuous deployment for Java has traditionally needed a CI server, an artefact repository and deployment scripts. For many teams a simpler loop is enough: commit, push, and see the change running. This package provides that loop for WildFly, the open-source Jakarta EE server behind Red Hat JBoss EAP.
The package deploys WildFly with a build node that watches your Git repository, runs the Maven build when changes land and deploys the resulting WAR or EAR to the server, with hot redeploy so downtime is minimal. A sample project is connected initially so you can see the pipeline work before pointing it at your own code. For clustered production, promote artefacts to the WildFly Managed Domain Cluster.
What the WildFly Continuous Deployment Package Deploys
Marketplace packages are not bare container images. One click provisions a complete, production-shaped environment on MassiveGRID infrastructure.
- WildFly application server: A current WildFly release on a Java node with an LTS JDK and the admin console exposed over HTTPS.
- Git integration and Maven build: A build component linked to your repository that compiles the project with Maven on each push.
- Automatic deployment: The built artefact deployed to WildFly with hot redeploy, and a deployment log available in the dashboard.
- Sample project: A connected sample application so the pipeline is proven immediately.
Why Teams Choose WildFly Continuous Deployment
Push to deploy
A Git push is the release process; no manual uploads or scripts.
Maven builds on the platform
Compile and package on the server, so developers do not need to build artefacts locally.
Fast feedback
Changes are live within a couple of minutes of pushing, ideal for development and staging environments.
Path to production
Use the same repository with the WildFly cluster or a Jenkins pipeline when you need approvals and multi-node rollout.
How to Install WildFly Continuous Deployment on MassiveGRID PaaS
Installing the package takes three steps and a few minutes of waiting. No servers to provision, no configuration files to edit.
Open the installer
Click Install with free trial or Install to my account. The MassiveGRID PaaS dashboard opens with the WildFly Continuous Deployment package pre-selected, so nothing has to be copied or pasted.
Sign up or sign in
New to the platform? Sign up for the free 14-day trial, which needs no credit card. Existing customers sign in with their usual dashboard credentials.
Choose region and deploy
Name the environment, pick New York, London, Frankfurt or Singapore, and confirm. The platform builds every WildFly Continuous Deployment node, wires them together and hands you the live URL and credentials.
Who Runs WildFly Continuous Deployment on PaaS
Development and staging servers
Teams that want the latest commit running for testers and stakeholders.
Small Java teams
Groups without a dedicated CI server who still want automated deployment.
Demos and prototypes
Jakarta EE projects that need a live URL updated on every push.
Why Run WildFly Continuous Deployment on MassiveGRID PaaS
Built for uptime. WildFly Continuous Deployment runs on MassiveGRID's high-availability platform, where every environment is covered by a 100% uptime SLA. Nodes live on redundant hosts, storage is replicated, and failed containers are restarted or migrated automatically.
Pay for what you use. Billing is hourly and per cloudlet (128 MiB RAM plus 400 MHz CPU). Vertical auto-scaling adds and removes cloudlets as load changes, so a quiet WildFly Continuous Deployment environment costs a few dollars a month and a busy one grows without a migration. Full details are on the PaaS page.
Your choice of jurisdiction. Deploy in New York, London, Frankfurt or Singapore and keep data inside the region your users or regulators require. MassiveGRID is ISO 9001 certified and GDPR compliant, and has run hosting infrastructure since 2003.
No lock-in. The package is a standard Jelastic Packaging Standard (JPS) manifest. You keep root-level access to the containers, can export the manifest, and can move the workload to any other Jelastic-compatible platform or to your own servers at any time.
Related on massivegrid.com: For Developers.
WildFly Continuous Deployment Questions
More from the Marketplace
Packages that are often deployed alongside WildFly Continuous Deployment, or that solve the same problem a different way. Browse all 84 packages.
Deploy WildFly Continuous Deployment Today
Start the free 14-day trial and have WildFly Continuous Deployment running in minutes. No credit card required.