The docker-wildfly images

Table of Contents

• 1. Project structure
  • 1.1. /dockerfile
  • 1.2. /script
• 2. Development
• 3. Release

The repository is a collection of wildfly docker images used in icellmobilsoft, to keep projects and their builds on the same basis.

The project can be divided into several parts, completing each other.

Important

The docker images contain the following components: Wildfly: 30.0.x (Jakarta EE10) Java: 17.x Base image version: 1.4.x

Table 1. Compatibility

Version	Jakarta EE	Java	Wildfly
1.0.x (internal only)	Jakarta EE 10	17	Widlfy 27.0.1.Final
2.0.x (first public)	Jakarta EE 10	17	Widlfy 27.0.1.Final
3.0.x	Jakarta EE 10	17	Widlfy 30.0.1.Final

The repository is a collection of wildfly docker images used in icellmobilsoft, to keep projects and their builds on the same basis.

The project can be divided into several parts, completing each other.

1. Project structure

1.1. /dockerfile

Collection of the dockerfiles. For a detailed description of the docker image created, see Docker Wildfly Images.

1.2. /script

Common scripts that are also used by dockerimages, but can also be used on their own.

2. Development

All you need to know is the following command:

docker compose -f <PATH>/docker-compose-1.yml build
docker compose -f <PATH>/docker-compose-2.yml build
docker compose -f <PATH>/docker-compose-3.yml build

Important

The release and docker push commands MUST be handled exclusively by Github Actions!

3. Release

The release is done by Github Actions. Basically we handle 2 cases:

1. Major, Minor version - major version release, can only be generated from master branch.

2. Bugfix version - can only be generated from release branch.

The associated CI appears only for the corresponding branches.