Skip to content
  1. Apr 02, 2019
  2. Nov 16, 2018
  3. Jul 05, 2018
  4. May 30, 2018
    • Thomas Bouffard's avatar
      chore(db): run tests with docker db container when possible (#182) · 7f21859a
      Thomas Bouffard authored
      Available for oracle, mysql and postgres for both integration and migration tests.
      
      Documentation: explain how to choose the the db used by tests
      We now have 2 cases:
        - when using docker container started by the build
        - sqlserver which still requires an external db to run
      Also document how to run a single test from within an IDE.
      
      In addition, when depending on an external database server for tests,
      drop the created user and database to let the environment clean as before
      the tests.
      To do so, the drop part of the cleanDb task has been reworked to fix some
      issues (duplication, missing or extra parts).
      
      As part of this change, also fix an issue on postgres that prevented to
      use a non default database (not running on localhost with default port
      and with db name equal to bonita)
      The postgres specific DB parameters (required by XA drivers) were missing when launching
      Bonita Engine.
      
      Various improvements in Jenkinsfile:
      Fix: remove extra scm checkout when running db tests
      
      Sqlserver: use the 2016 instance
      
      Improvements:
        - use specific user and database name for master, dev and pr to avoid
        clash if builds are run in parallel
        - do not run db tests inside the node which run the intial build. This
        make consume an extra node for nothing (the initial node was waiting for
        nodes used for parrallel tasks before completing where it can complete
        right after the build finishes)
      
      * jenkinsfile: do not compute dbConnectionSettingValue all the time
      
      * readme: postgres running test example
      
      * readme: integration tests with sqlserver docker run manually
      
      Covers [CI-286](https://bonitasoft.atlassian.net/browse/CI-286)
      7f21859a
  5. May 25, 2018
  6. Feb 12, 2018
  7. Dec 19, 2017
    • Baptiste Mesta's avatar
      refactor(migration tool): revamp project structure (#152) · 76696d8d
      Baptiste Mesta authored
      refactor project structure to avoid code duplication when adding a step.
      
      Instead of having a project for each test step, we have only one project
      with multiple source sets, all tests are compiled with last version of
      the engine but are run using the version of the step.
      there is a filler sourceset and an enginetest source set containing code
      to prepare the migration test and one to validate the engine was
      migrated.
      migration test steps are generated for each engine version.
      
      the task integrationTest run all migration test and gradle build launch
      only normal tests.
      
      in order to be able to build community in standalone mode the plugin is in
      community/buildSrc and linked in the root folder. See info about symlinks on Windows.
      
      use axion release plugin:
      It allows to tag alpha/beta/rc with gradle commands. see README.
      
      use `gradle publish` to push artifacts to repositories.rd.lan
      
      update readme with how to run the migration
      76696d8d
  8. Aug 28, 2015
  9. Aug 10, 2015
  10. Jul 29, 2015
  11. Jun 10, 2015
  12. Jun 02, 2015
  13. Dec 24, 2013
  14. Nov 19, 2013
  15. Nov 15, 2013
  16. Nov 13, 2013
  17. Nov 06, 2013