Continuous Integration

The BridgePoint development team understands modeling, model-driven development and the benefits of abstraction, methodology and rigor.  Additionly, the team leverages the latest cloud-based technologies to support the engineering flow.  GitHub, Amazon Web Services, Redmine, Jenkins, Eclipse, real-time web chatting and more combine to take requirements to deployment.


A typical scenario might be as follows:

  1. A user wants a new feature, chats about it in the online discussion group and then raises an issue in the Redmine issue tracker hosted in the cloud on an amazon t2.micro instance.
  2. A BridgePoint developer moves the issue to ‘In Progress’, forks and branches the git repository using the issue number for requirements tracing.  Local development and testing are done.  A pull request is created, and the issue is passed to the reviewer for promotion.
  3. As part of testing a new build of BridgePoint is launched on an Amazon m5.large.  This instance connects to GitHub to retrieve the named branches, builds with Maven, runs the testing framework, reports unit test results and publishes to S3… automatically and unattended.
  4. Upon successful completion of test and review the issue is marked Resolved, and the updated functionality is available in the Nightly Build.

The process is lightweight yet accountable.


Related Articles
Dear Modelers, Significant progress has been made on a specifications of textual xtUML and separately…
At xtUML Days 2020 UK, Marc Balcer explained model-driven test case generation with TAME.
BridgePoint is Open Source Software (OSS). It is free. However, OSS is not free like…