Lists all automation actions achieved by the XWiki Community at large for improving the development of the XWiki open source software (Starting January 2015).

The idea is to favor even more automation by explicitly listing the past actions already achieved. Thus this page can also be seen as an Automation Hall of Fame for the XWiki project.

Implemented Automations

  • 4 Mar 2015, ThomasMortagne: Added new Jenkins jobs to reproduce the conditions of a release build so that when the release time comes, we're pretty sure the build will work fine.
  • 26 Feb 2015, VincentMassol: Automate creation of JIRA projects for XWiki Contrib projects. XINFRA-167, Blog post
  • 2 Feb 2015, VincentMassol: Automatically capture all logs output by code under test, using the new @AllLogRule. XCOMMONS-739.
  • 2 Feb 2015, VincentMassol: Automatically fail the build if tests output content to stdout/stderr, leading to better written tests. XCOMMONS-738, XRENDERING-380, XWIKI-11745.
  • 26 Jan 2015, VincentMassol: Automatically fail the build if an @Unstable annotation is added without @since javadoc tag + automatically fail the build when the @Unstable annotation must be removed (APIs can only stay a full development cycle in the unstable state). XCOMMONS-731, XCOMMONS-730.
  • Jan 2015, enygma: When a functional tests fails, inclusion of the screenshot of the XWiki UI at that time, displayed directly in the Jenkins failing test page. We were previously saving screenshots in the workspace, forcing developers to have to spend time to find the screenshot corresponding to the failing test.

Future Ideas

  • <add your ideas here, ideally along with a link to a JIRA issue for it>
Created by Vincent Massol on 2015/01/24 11:46

Get Connected