Introduction

CodeRamp is an AI platform that automatically upgrades legacy code versions of Java and Java related libraries and frameworks to their any future stable version across all your repositories.

Getting Started

Step 1: Repository access

  1. Clone the Java or Java-related repositories you wish to upgrade.
    Note: CodeRamp requires repositories that build successfully.

  2. Provide access to these cloned repositories to CodeRamp via a Virtual Machine (VM).

Step 2: Provisioning AWS account

  1. CodeRamp will create a dedicated AWS Bedrock account for running an LLM endpoint that is provisioned with Anthropic Claude Sonnet 3.5 or later.

  2. A read-only role will be set up for you to monitor the AWS account.

Step 3: Running CodeRamp

  1. CodeRamp will host its tools on its S3 account which will be downloaded on the VM provisioned by you.

  2. CodeRamp will analyze your code, and generates an impact analysis document for your review.

  3. Upon your confirmation, CodeRamp will migrate the repository, producing a detailed diff for each file, including Java and configuration files.

  4. A comprehensive summary of all changes will be presented and documented for inclusion in the code review process.

Step 4: Unit Testing

  1. CodeRamp performs unit testing.

    1. If unit tests pass, proceed to Step 5.

    2. If unit tests fail, CodeRamp will address and fix the issues.

Step 5: Create code review

  1. CodeRamp offers two options for code review:

    1. Approach 1: CodeRamp will commit the changes to a custom remote branch (not the main or master branch). Authorized team members can review the diff and merge the branch into the mainline if approved. (Requires Git framework.)

    2. Approach 2: CodeRamp will generate a Git patch that your team can apply to their local repository.

  2. Review the changes:

    1. If further modifications are required, CodeRamp will incorporate them. Return to Step 4.

    2. If no changes are necessary, proceed to Step 6.

Step 6: Merging and Deployment

  1. Merge the updated code into the main branch.

  2. Deploy the code using your preferred deployment pipeline.

Step 7: Cleanup

  1. CodeRamp will remove its tools from your environment.

  2. The temporary AWS account created for the process will be deleted.

END.

Note: CodeRamp does not perform integration and manual testing.

FAQs

What Java libraries and frameworks does CodeRamp support?

CodeRamp supports a wide range of Java-related libraries and frameworks, including but not limited to Java, Spring, Mockito, Apache, Jackson, and JUnit.

How do I get support if I encounter issues? 

CodeRamp will establish a joint Slack channel for direct communication throughout the upgrade process. Additionally, we provide extended support for 30 days after completion to ensure a smooth transition and address any post-upgrade issues.

Can internal Java frameworks or custom Java libraries be migrated?

Not currently. This feature is planned for release in 2025.

How does CodeRamp handle complex issues like dependency conflicts, or outdated libraries?

CodeRamp thoroughly analyzes each Java file to map dependencies, identifying those that require upgrades. Dependencies are upgraded first, with customer confirmation. For outdated libraries, CodeRamp migrates to the latest supported versions. If a dependency replacement is required, it will need to be manually addressed by the customer.

Does CodeRamp share my code externally? What is CodeRamp's security policy?

No, CodeRamp does not share your code externally. All tools are deployed within your isolated environment, remaining under your ownership and control. Upon completion, CodeRamp removes its tools and deletes the AWS account created for the upgrade process.

How much does CodeRamp cost?

CodeRamp's pricing is determined by the type of Java libraries selected and the volume of code upgraded, measured by the number of lines of code (LOC). Reach out to support@coderamp.xyz to know more.

For more details, visit our Security policy.