The BridgePoint development team combined modeling and model-driven development practices with cloud-based tools to support its engineering workflow. The original article described an integrated toolchain that included GitHub, Amazon Web Services, Redmine, Jenkins, Eclipse, and online discussion.
Example workflow
- A user discusses a desired feature with the team and creates an issue in the cloud-hosted Redmine tracker.
- A developer takes ownership of the issue, creates a Git fork and feature branch, and uses the issue number for requirements tracing. Development and local testing follow.
- The developer creates a pull request and sends the issue for review.
- An automated build environment retrieves the named branches from GitHub, builds BridgePoint with Maven, runs the test framework, reports unit-test results, and publishes successful build artifacts to Amazon S3.
- After successful testing and review, the issue is resolved and the updated functionality is made available in the nightly build.
The article characterized this as a process that was lightweight yet accountable: issue tracking connected the requested change to its implementation, review, testing, and delivery.
Historical note: the tools and infrastructure named here reflect the team’s 2019 environment. The workflow concepts remain useful, but the specific services and implementation details should be adapted to current tools.