Continuous Integration at #NWCloudPortal . TAKE IT HIGHER

What is good Continuous Integration (AKA CI) process? Am I doing CI properly? Are we satisfy with the results? Are we catch issues on time? Do we have surprises?

Those questions are being asked normally on daily basis among each development operations teams.

How can we have a proper CI process which can answer the needs above and provide instant feedback?

The answer isQuality On Submit.

Mainly when we say “continuous integration” – we means that this is a software development practice where members of a team integrate their work frequently on daily basis and each integration is verified by an automated build and sometime few tests. Are we happy with it? Is it answers our problem described above. Well… not sure…

$ whoami (Nir Koren)

I’m working in SAP Labs Israel in Technology Innovation Platform under Portal Platform. Our main business is the incredible SAP NW Cloud Portal. It is a cloud-based solution that provides easy site creation and consumption with a superior user experience and is also designed for mobile consumption. I am the development Integration Lead which responsible for all development operations (Source control, build, deployment and runtime), product integration, deployment and cloud operations. In addition to that – I am provide internal tools which make internal processes easier.

I’ve been working for SAP for 6 years so far. Prior to that I came from the communication industry in similar roles.

What is Quality On Submit?

Quality On Submit (AKA QOS) is End to end SW development quality process that provides instant feedback and transparency to the development teams.

The motivation is normally questions like: was the nightly build was broken? No systems for today… Who broke the build? Who broke the runtime? How many changes do we have today? Did Jack already check-in his stuff? What is the status of our product today? Now? Why do we fix PMD issues right before the release?

Therefore we developed the QOS process which is SAP Patent pending application title “Quality on Submit Process”. Ref: 2010P00489US.

How it looks like?

We actually listens to our source control system (GIT. previously Perforce). It all starts with developers code check-in…