Blog entries

Continuous Integration platform for Mercurial with apycot

2010/03/15 by Arthur Lutz

Since the mercurial 1.5 sprint Pierre-Yves has been working on improving Continuous Integration for Mercurial. All developers are encouraged to run the test suites and code quality checkers but it's no always feasible to test every cases, different OS, different python versions, strange test dependencies, slow coverage run, etc. Moreover it's generally useful to keep track of the results of previous tests, especially for benchmarks.

At http://apycot.hg-scm.org/ you will find a production setup that now runs several variants of the tests-suite for all official repo and checks code style and documentation. Notification by email or RSS is available. For more details check out the FAQ.

apycot is open source and uses the cubicweb platform, if you want to set up one for your project, check out the step by step documentation.

http://www.cubicweb.org/image/749160?vid=download

Fun with graphs in apycot

2010/03/24 by Arthur Lutz

Yesterday I had a little quick fun with apycot in the train, using the existing plots infrastructure I managed to quickly add a few graphs to the application. I only had an old dump of our apycot for mercurial (http://apycot.hg-scm.org/) so the timespan is not huge, but I like it anyway! Here are some dev screenshots while you wait for this feature your your application... The pylint grades where pretty constant so I'm not including that graph.

http://www.cubicweb.org/image/779761?vid=downloadhttp://www.cubicweb.org/image/779768?vid=download

Now, I have to make solid code and integrate it properly.


Summer CubicWeb/Narval Sprint

2010/08/10 by Sylvain Thenault

Although this week is normally the regular annual holidays here at Logilab, some of us will sprint in Paris exceptionally.

Focus

We're starting this week with an exciting goal: integrating all our release process into our continuous integration suite (through the apycot cube). Including Debian repository management, pypi registration, etc...

The hot stuff to achieve this is the third resurrection of Narval, the project Logilab was originaly based on, but this time it is built on top of CubicWeb framework. Narval will be used to rewrite some parts of apycot, in order to make it more flexible and powerful.

It is not just a refactoring or a simple upgrade! We hope to automate common tasks, simplify maintenance, and thus enhance release quality, but also gain a lot of functionality in near future.

Sprint roadmap

  • merge Apycotbot process manager into a new Narval incarnation, and rewrite it as Narval actions and recipes
  • improve vcsfile cube with a new cache system for mercurial
  • define Logilab's release process as new Narval recipes, triggered by actions such as adding release tag into the source repository

More detailed stuff will come with the sprint reports that we'll try to issue each day.

Information

This sprint is taking place in Logilab's offices in Paris from Monday the 9th to the 13th of August 2010.


Summer CubicWeb/Narval Sprint - Day 1

2010/08/10 by Sylvain Thenault

We started this first day by several presentations by Sylvain about Logilab's current development process workflow, and compared it to what it should be after the sprint. Sylvain also introduced Narval.

We then set up a dev environment on everyone's computer: a working forge with a local Narval agent that can be used for tests during the week.

Regarding more concrete tasks:

  • Charles and Alexandre started writing some basic Narval actions such as move, to move a file from a place to another, and had to grasp narval's concepts on the way.
  • Pierre-Yves dug into the code to understand how exceptions are propagated in the Narval engine, his goal was to get better reports.
  • Stéphanie and Alain worked on a nice bot status view.
  • Katia, Aurélien studied the new mercurial cache solution for vcsfile
  • Julien started some piece of documentation.
  • Celso, our Mexican friend, discovered some new features of recent cubicweb releases and setup his environment to later work on Spanish translation, CSS, etc.
  • Sylvain came with a basically working narval implementation on top of cubicweb, and spent the day helping various people...

Summer CubicWeb/Narval Sprint - Day 2

2010/08/11 by Katia Saurfelt

During the second day of our Summer CubicWeb/Narval Sprint, several tasks started on the first day were completed and new tasks started:

  • Charles, Alexandre and Julien finished writing the "copy" and "move" Narval actions, and then started transforming existing apycot checkers into Narval actions.
  • Pierre-Yves managed to improve Narval reports with more explicit and relevant content.
  • Stéphanie and Alain finished the bot status view as well as the recipe graph view.
  • Katia and Aurélien finished writing the new mercurial cache solution for vcsfile and started improving the security of Narval recipes (i.e. who can start which recipe).
  • Celso kept on his life-long work of translating CubicWeb to Spanish.
  • Sylvain wrote some Narval views, improved Narval execution logs handling and kept on reviewing patches and helping various people...

Summer CubicWeb/Narval Sprint - Day 3

2010/08/13

CubicWeb/Narval Sprint is going on !

The third day of our sprint focused on the following points:

  • Pierre-Yves worked to prevent duplicate test executions (eg running several time the same test with the same version configuration),
  • Celso has terminated the spanish translation of CubicWeb. He's now working on various cubes translation,
  • Stéphanie and Alain spent some time on the narval bot view. They also modified ProjectEnvironement's attributes in order to use similar information available on the vcsfile repository, hence simplifying the configuration (more to do on this!),
  • Julien worked on the debian package recipe,
  • Katia and Aurélien worked on recipe security (using CWPermission),
  • Alexandre and Charles produced a first template of a full test recipe using pyunit and pycoverage,
  • Finally, our captain, Sylvain, is at the helm !

We'll hopefuly be able to present a functionnal demo at the end of the week.

Narval/Cubicweb left off !


Summer CubicWeb/Narval Sprint - Day 4

2010/08/13 by Pierre-Yves David

In this fourth day of the our Summer Sprint important progress have been made.

  • Stéphanie and Alain cleaned up the Apycot's bot sources from deprecated code and rewrite part of the test suite to follow the new way to launch apycot. They cleaned up the handling of VCS sources for tested project taking advantages of the new mercurial cache for vcsfile implemented by Katia and Aurélien last Tuesday. This feature keep a local clone of the remote repository and allow much faster checkout during test runs.
  • Julien made significant progress in the writing of the Debian recipe. A recipes can now successfully build Debian packages of a project and validate them with lintian and lgp. He later paired with Pierre-Yves and they improved the annotation of Apycot's Narval variable to enhance Input validation in Apycot's Narval recipes. For example, the action building a Debian package will explicitly refuse to run on a project not yet checked-out.
  • Aurelien first paired with Pierre-Yves to improve some views and the consistency of the database schema, then he worked on a dashboard displaying various indicators useful to the version publishing process.
  • Pierre-Yves spent some time improving the ability of Narval to recover on errors and to display meaningful logs about them.
  • Alexandre and Charles finished the re-implementation of the full python recipe.They used options at the Narval level to run test suite with the coverage enabled and re-enabled the coverage checker to process the result, discovering some problems in Narval's engine on the way...
  • Celso finished Spanish translation of Cubicweb's core and started to work on a new css theme
  • Sylvain helped several groups along the day and reviewed patches from them.

Summer CubicWeb/Narval Sprint - Final report

2010/08/18 by Sylvain Thenault

For that last sprint day, each team made some nice achievements:

  • Steph & Alain worked on the mv/cp actions implementation to makes them working properly and supporting globs. Last but not least, with a full set of tests.
  • Alex & Charles got back what we call apycot 'full' tests, eg running test with coverage enabled, checking that code coverage is greater than a given threshold, but also running pylint and checking that its global evaluation is at least 7 (configurable, of course).
  • Katia & Aurélien provided a sharp implementation of recipe checking, so that we know we don't launch a recipe badly constructed, as well as informing the user nicely from what errors his recipe suffer.
  • Julien managed to set up a recipe managing from Debian package construction to Debian repository publication, going through lintian on the way
  • Pierre-Yves helped other teams to solve the narval related bugs they encountered, and finished by writing a thread-safe implementation of apycot's writer so we can run several checker simultaneously.
  • Celso continued working on a proof of concept blue-theme cube, wondering how to make CubicWeb looks nicer and be easily customisable in future versions.
  • Sylvain helped there and there and integrated patches...

So we finally didn't get up to the demo. But we now have everything to set it up, so I've a good hope that we will have a beta version of our brand new production chain up and running before the end of August!

Thanks to everyone for all this good work, and for this time spent all together!


CubicWeb Sprint report for the "Benchmarks" team

2012/02/17 by Arthur Lutz

One team during the CubicWeb sprint looked at issues around monitoring benchmark values for CubicWeb development. This is a huge task, so we tried to stay focused on a few aspects:

  • production reponse times (using tools such as smokeping and munin)
  • response times of test executions in continuous integration tests
  • response times of test instances runinng in continuous integration

We looked at using cpu.clock() instead of cpu.time() in the xunit files that report test results so as to be a bit more independent of the load of the machine (but subprocesses won't be counted for).

Graphing test times in hudson/jenkins already exists (/job/PROJECT/BUILDID/testReport/history/?) and can also be graphed by TestClass and by individual test. What is missing so far is a specific dashboard were one could select the significant graphs to look at.

By the end of the first day we had a "lorem ipsum" test instance that is created on the fly on each hudson/jenkins build and a jmeter bench running on it, it's results processed by the performance plugin.

http://www.cubicweb.org/file/2184036?vid=download

By the end of the second day we had some visualisation of existing data collected by apycot using jqplot javascript visulation (cubicweb-jqplot):

http://www.cubicweb.org/file/2184035?vid=download

By the end of the sprint, we got patches submitted for the following cubes :

  • apycot
  • cubicweb-jqplot
  • the original jqplot library (update : patch accepted a few days later)

On the last hour of the sprint, since we had a "lorem ipsum" test application running each time the tests went through the continuous integration, we hacked up a proof of concept to get automatic screenshots of this temporary test application. So far, we get screenshots for firefox only, but it opens up possibilities for other browsers. Inspiration could be drawn from https://browsershots.org/