The concept of Pull Requests brought development and collaboration to the next level. Thus, developers can now work in isolation and submit their changes to approval through pull requests reviews and merge.

However, merging a pull request does not guarantee that the resulting commit will build successfully on the target branch. In a context where tens of pull requests are created each day on a single repository, how to ensure that the merge operation will not break the target branch?

Amadeus created the concept of Merge Request and Unbreakable Branches to setup a secured continuous integration. Come and discover how this feature can improve developer's efficiency and continuous integration in your company!


Outline/Structure of the Demonstration

  • The problem statement - Failing master every time a Pull Requested is merged
  • How to solve this problem using Unbreakable branches feature created by Amadeus in Bitbucket and Jenkins
  • A demo
  • Q/A

Learning Outcome

The audience after this session will be able to implement unbreakable branches in their projects using Bitbucket and Jenkins. Since Amadeus will open source the plugins, anyone can use them and even contribute to the feature.

It will enhance the Continuous Integration in their companies and would increase developer's productivity.

Target Audience

Developers, Managers, Devops Practitioners, Executives,

Prerequisites for Attendees

  • A very basic understanding of Continuous Integration
schedule Submitted 2 years ago

Public Feedback

    • Arun Narayanaswamy

      Arun Narayanaswamy / Rajat Pandit - Economics of Cloud

      45 Mins

      Cloud is one of the core components during an Agile Development process. What are the enterprise viewpoints for going for a cloud? There are no two thoughts that the entry barrier for a new company to launch a platform on the cloud is low, but enterprises who have been running these systems for ages - is it viable to move to the cloud and be more agile. How do the economics work?
      Cloud is seen as the means to competitive superiority, but if implemented wrong it can spiral out of control. The talk explains the various concerns the enterprises see when adopting the cloud.
      - Capex vs Opex
      - Tax benefits
      - IAAS, PAAS, everything as a service! How the costs vary
      - Adoption concerns
      - Tools to monitor spends
      - Tools to control spends
      - Costs of these monitoring and control
      - Costs of cloud neutral strategies
      - Cost of migration
      - Cost of training
      - Cost of re-training the datacentre teams
      - Cost of leadership effort
      - Cost of adoption
      With all the various costs, how to build the right mix of strategies to adopt cloud