loader image

The New Generation of Software Development Lifecycle Tools for IBM i

Avalon represents the next stage in the evolution of change management and application lifecycle management for IBM i.

Seamlessly integrate classic and modern IBM i development into the toolchains your company already uses for Java, .NET, JavaScript, Python, Rust, and other platforms.

Whether it’s GitHub, Azure DevOps, GitLab, Bitbucket, or GitBucket; whether it’s Jenkins, GitHub Actions, Azure DevOps, or GitLab CI; whether it’s Nexus or Artifactory: Avalon integrates IBM i into your existing development and DevOps landscape.

Or you can continue to run the entire development process 100% on IBM i.

Your IBM i. Your toolchain. Your development process. Avalon connects it all.

How Avalon works
Get to Know Avalon

IBM i

Application, source code and objects

Avalon

Record, prepare, build

Git & VS Code

Sectors, Development and Cooperation

WHAT IS AVALON?

A modern workflow for established IBM i applications.

Your IBM i development doesn’t have to be an isolated island. The customer decides where their toolchain runs: integrated into existing platforms such as GitHub, Azure DevOps, or GitLab—or entirely on IBM i. With GitBucket, Jenkins, and Avalon, Git, builds, and automation can be run entirely on IBM i. External cloud or DevOps platforms are not a prerequisite for Avalon.

The application remains on IBM i. The way your team develops it is becoming more modern.

THE BENEFITS

Fewer disruptions in the development process.

From the handover of the existing application right through to delivery, tools and processes are seamlessly integrated.

01

Building on existing knowledge

Avalon identifies source members, objects, relationships and RPG includes, and prepares the application for Git.

02

Working with Git and VS Code
Use GitHub, Azure DevOps, GitLab, Bitbucket, GitBucket, or any other Git-compatible platform. Avalon integrates your IBM i sources into your existing Git strategy. Git can be used via the standard Git client in VS Code or, optionally, via the LIGHTMAN Git Explorer. LIGHTMAN is an optional add-on and not a prerequisite for Avalon.

03

Building and testing on IBM i

Builds run on IBM i. Modified objects are created in a separate workspace library for each user and branch.

04

Compile changes only

Avalon supports incremental compilation and returns build results and logs.

05

Automate Workflows
Jenkins, GitHub Actions, Azure DevOps, GitLab CI, or other CI/CD platforms can automate the build, test, and deployment process set up with Avalon. After a successful commit, your existing CI/CD platform takes over the rest of the process.

06

Structuring the Release
Artifacts that have been generated can, for example, be versioned in Nexus or Artifactory and made available for further deployment processes. Save the file and the deployment archive.

HOW YOUR TEAM WORKS

From the change to the verified version.

A development workflow that integrates Git and VS Code with the build process on IBM i.

01 / DEVELOP

Working in VS Code

The developer edits the code locally in VS Code; Avalon handles IBM i and automatically manages the build environment, dependencies, libraries, object generation, and feedback on compiler errors.

02 / BUILD

Start the build

Start the build from VS Code; Avalon compiles on IBM i.

03 / TEST

Test in isolation

After the build, Avalon automatically runs existing unit tests or, optionally, ReplicTest. Errors from the build or tests are returned directly to VS Code and can be addressed immediately.

04 / REWORKING

Repeat if necessary

Modify the code and run the build and test again.

05 / SHARE

Push changes

Commit the reviewed version and push it to the central Git repository.

GOOD TO KNOW

From commit to production—fully automated

Your CI/CD platform can automatically deploy the objects generated by Avalon through the designated development, test, QA, and production environments. Target libraries can be located on the same IBM i system or on different IBM i partitions. Jenkins, GitHub Actions, Azure DevOps, GitLab CI, or other CI/CD platforms can automate the build, test, and deployment process set up with Avalon. After a successful commit, your existing CI/CD platform takes over the rest of the process.

GETTING STARTED

The existing application is now ready for Git.
Avalon integrates your existing IBM i application into the modern development process. During the analysis phase, Avalon builds an Application Knowledge Base. This base stores, among other things, object relationships, include dependencies, cross-references, build information, and program characteristics. This creates a machine-readable model of the existing IBM i application, which Avalon later uses for build, analysis, and automation processes. Avalon simultaneously analyzes dependencies, cross-references, object relationships, and structural properties of your programs.

Capturing Objects, Source Members, and Cross-References

Taking RPG and RPGLE Includes into Account

Mapping Objects Without Traditional Source Code Using Pseudo-Sources

Preparing Source Code for a Git Repository

SIMPLIFIED OVERVIEW

Here’s how the application is integrated into the new workflow.

01 Analyze IBM i libraries

02 Capture source code and relationships

03 Prepare for Git

AUTOMATION

From Git to deployment.

In a CI/CD pipeline, an automation server retrieves the code from Git and launches the Avalon build on IBM i. The resulting artefacts are stored and transferred to the target system as part of a separate deployment process.

01 / Git

Load code and branch

02 / Automation

For example, Jenkins or GitHub Actions

03 / Avalon on IBM i

Build, compilation and logs

04 / Artefact Repository

Generated artifacts can, for example, be versioned in Nexus or Artifactory and made available for further deployment processes. Save the file and the deployment archive. Avalon integrates seamlessly into existing enterprise toolchains.

05 / Deployment

Separate process: Update target libraries

The specific process and the tools used will depend on your existing infrastructure.

FREQUENTLY ASKED QUESTIONS

The most important information at a glance.
Will Avalon replace our IBM i application?

No. Avalon builds on the existing application and supports a modern development and deployment process. The builds continue to run on IBM i.

The development process described on this page uses a Git repository and VS Code. Avalon links this local workflow with builds on IBM i.

Yes. The processes described involve the integration of an automation server such as Jenkins, GitHub Actions or GitLab CI/CD. The specific integration will depend on your environment.

The objects modified in the branch are created in a separate workspace library for the respective user and branch. The changes can be checked there before being pushed.

Yes. AI agents can use LIGHTMAN and Avalon to analyze existing applications, make changes, start builds, and run tests. The existing CI/CD and deployment process remains unchanged.

Get in touch.
Connect with knowledge.

Digital IT training, learning platforms, and customized solutions to help you advance.