It has been a long time that our developers are working on the develop branch in each repository in the networknt organization. Recently, we have to change the release process to release from three release branches to meet the requirement from our users. The 1.5.x and 1.6.x branches for JDK 8 are the stable for production upgrade as only defect fixes backport to these branch. The master branch for JDK 11 is our main development branch with new features added daily and release under 2. Read More »

This task is used to merge from one branch to another for a list of repositories. Here are the steps in the task. it clones all projects defined in the checkout section into a workspace. if the workspace exists, then it will iterate each repository to switch to the branch specified in the checkout and pull from the remote. merge the from branch to the to branch locally. push the merged branch to the remote Git server For live configuration example, please visit light-config-test. Read More »

This task is used to create a new branch for a list of repositories from an existing branch or an existing tag. Here are the steps in the task. it clones all projects defined in the checkout section into a workspace. if the workspace exists, then it will iterate each repository to switch to the branch specified in the checkout and pull from the remote. create a new branch locally from an existing the current checked out branch or an existing tag. Read More »

This is the task that is used to do the regular expression replacement across multiple repositories. We are using this to change the dependencies version for hundreds of projects within the networknt GitHub origanization. Here are the steps for the task. check out repositories to a workspace and switch to the specified branch. If the repsoitory has been checked already, swith to the specified branch and pull the latest code from the remote. Read More »

This is the task to release all services for the networknt organization to the docker hub. It first checkout repositories into a workspace and switch to the release branch defined in the release-docker.yml file. If the workspace exists, then it will switch to the release branch and run git pull origin (release-branch) to ensure the codebase is the same as remote. Then the release process is started with the following step for each repository. Read More »

This is the task to release all frameworks and modules all together for the networknt organization on the GitHub. It first checkout repositories into a workspace and switch to the release branch defined in the release-maven.yml file. If the workspace exists, then it will switch to the release branch and run git pull origin (release-branch) to ensure the codebase is the same as remote. Then the release process is started with the following step for each repository. Read More »

This should be called right after a new release so that all repository versions can be upgraded to the next one in one shot and check in into each release branch. Here are the steps in the process. clone all projects to a workspace defined in the version-upgrade.yml in your home directory and switch to the release branch specified. if the workspace exists, then switch each project to the release branch and pull from remote to make sure you have the latest. Read More »

This is a task that is used to build all related repositories from a specific branch and perform unit, integration as well as end-to-end tests. It should be set up as a scheduled process on build server for now, and in the future, it should be called by agent server once the controller receives push event from github.com This task is mostly used by the developer to build all dependencies on their local from master branch daily. Read More »