AutoDE - Mazoea · – give your customer demos in few minutes • validate deployment steps – build system is a proof of concept for customer usage • quality progress –by following

AutoDE Continuous Integration Server

or a friendly build server with support

1 Mazoea s.r.o.

http://www.mazoea.eu [email protected]

What is this presentation about

2

• FIRST LOOK at AutoDE

• what is it, what you get

• WHY DO YOU WANT AutoDE

• from manager, QA/developer, your customers point-of-view

• CASE STUDIES and USER STORIES

First look

Mazoea s.r.o. http://www.mazoea.eu

[email protected]

First look – what you get

3

• automated software continuous integration build server • automated build steps

• automated deployment steps

• automated basic tests

• reduced development lifecycle time; thus costs!

• more effective and happy QAs

• precise project technical status and statistics

• history with important files preserved (e.g. symbols)

• extensibility by your own programmers

First look


[email protected]

First look – what you get by example

4

First look – web frontend


[email protected]

First look – what you get by example

5

First look

• build specification python sources • user documentation • API documentation


[email protected]

Key Features

6

Features

• set of common CI build management tasks • VCS

• git, svn, cvs • builders with Visual Studio Professional integration

• ant, make, ivy, maven • VS sln builder • direct support for configurations and targets, symbol server

• informative • build errors, build warnings, files, email announcements

• validating • components, paths, urls, simple testing

• deployment • local, remote, database, rpms


[email protected]

Key Features

7

Features

• repetitive builds and focus on multiple projects • command line interface for complex build specifications • easily integrated into cron, windows task scheduler

• easy to use and fast web frontend • well-arranged dashboard, charts, documentation

• project build history and progress preserved • build log files, binary outputs • symbols


[email protected]

Why do your developers/QAs want it

8

Why

• precise technical status of your project every morning

• click and test bugs fixed yesterday

• find and solve common bugs daily (missing commits, typos, …)

• automate basic smoke/integration testing saving work hours and smile on their faces


[email protected]

Why do your managers want it

9

Why

• brief project overview every day in 1 min

• fast progress overview using build and deployed

applications in just few clicks


[email protected]

Why do your customers want it

10

Why

• fast iterative development – give your customer

demos in few minutes

• validate deployment steps – build system is a proof of

concept for customer usage

• quality progress – by following common software

development methodologies


[email protected]

11

Case study – problem formulation

Problem

Solution is AutoDE…

1. automating build steps (cvs, Visual Studio, package)

2. storing packages, debugging symbols (pdbs)

3. create and update symbol server

4. local validating of builds

5. automating copying to remote machines (ssh, sftp)

6. extensible for additional functionality and multiple projects

7. additional information (cvs diffs, automatic emails, file sizes)

Case Study 1 – pdf editor (simple)


[email protected]

12

Case study – problem solution

AutoDE offers many tasks you can compile your build specification from (these are used in pdfedit)

• checkout from cvs repository • clean/build using Visual Studio Professional (2008, 2010) • create and update symbol server from Visual Studio • run cppunit tests and other verification tools • copy files to remote destinations • show changes made to the project since yesterday • email announcement

Case Study 1 – pdf editor (simple)


[email protected]

13

Case study – problem formulation

Problem

Solution is AutoDE…

1. automating build steps (svn, ant, rpm) 2. automating deployment to remote machines (ssh, sftp, shell) 3. automating remote installation (rpms, scripts) 4. automating database initialization (oracle) 5. local and remote validating of builds 6. additional information (svn diffs, automatic emails, file sizes) 7. every day complete testing environment built from the newest sources 8. extensible for additional functionality and multiple projects 9. easily find problems, download whole project

Case Study 2 – medical web application (advanced)


[email protected]

14


AutoDE offers many tasks to compile your build specification from • checkout from svn repository, clean/build using ant

• install packages remotely

• initialize and fill oracle database on remote server

• copy/execute files to remote destinations

• remote validation of paths, urls

• show changes made to the project since yesterday

• email announcement

Problems 1-7 solved.



[email protected]

15


AutoDE gives you python sources of your build specification where you can

add functionality using any python package.

Applicable for custom static and dynamic analysers, validators, performance

checkers, coverage, stress testing, security testing…

AutoDE offers web interface where you see the status of each run, inspect

validators, inspect tasks, download created packages/binaries, inspect the

build process logs for warnings, see what changed from the day before.

Problem 8 solved.



[email protected]

User story 1

16

User story

• As a manager/team leader, I want to see

the build status.

• You can use your email client to open the

latest email sent to you by the build machine.

• You can open your browser, type the build

machine url with specific port and select the

project you want to see.


[email protected]

User story 2

17

User story

• As a developer, I want to change the build process to include installation of a new binary. • You will log into your build machine, go to build

specification directory (e.g. bs/buildspec/yourproject/) and change buildspec.py.

• As a QA, I want to create new project for automatic building of new branch. • You will log into your build machine, go to build

specification director, copy the contents of this directory to a new one (bs/buildspec/yourprojectv11) and change e.g. the repository path in buildspec.py.


[email protected]

User story 3

18

User story

• As a developer, I want to use different tasks.

• You can open your browser, type the

build machine url with specific port and

click on Project documentation where

you will find user/programming

documentation.


[email protected]

User story 4

19

User story

• As a QA, I want to see a new chart in the web

interface of the build machine.

• You will log into your build machine, go to web interface of

AutoDE and change the python source code index.py and

restart Apache.


[email protected]

20

Thank you

Please, contact us at

autode @ mazoea.eu


[email protected]

A DEMO is worth a thousand words so check our DEMO at www.mazoea.eu!

http://www.mazoea.eu/

Documents

AutoDE - Mazoea · – give your customer demos in few minutes • validate deployment steps – build system is a proof of concept for customer usage • quality progress –by following