1. 22 Jan, 2020 1 commit
  2. 19 Nov, 2019 1 commit
  3. 08 Nov, 2019 1 commit
  4. 30 Aug, 2019 1 commit
  5. 28 Aug, 2019 1 commit
  6. 26 Jul, 2019 1 commit
  7. 25 May, 2019 1 commit
  8. 09 Mar, 2019 1 commit
  9. 07 Feb, 2019 1 commit
  10. 22 Jan, 2019 1 commit
  11. 20 Dec, 2018 1 commit
    • Łukasz Nowak's avatar
      slapos-sr-testing: Common testing for Software Releases · 9fae7463
      Łukasz Nowak authored
      Since some software releases have unit tests, it is good idea to run the
      tests for each commit on slapos branch.
      
      This SR follow slapos-testing SR in a way how tests are grouped and run.
      
      Fixed erp5.util is used to expose good test suite names.
      9fae7463
  12. 12 Dec, 2018 1 commit
  13. 05 Dec, 2018 1 commit
  14. 27 Nov, 2018 1 commit
  15. 23 Nov, 2018 2 commits
  16. 02 Sep, 2018 1 commit
  17. 28 Jun, 2018 1 commit
  18. 22 Jun, 2018 1 commit
  19. 04 Apr, 2018 1 commit
    • Jérome Perrin's avatar
      slapos-testing: rework to use buildout to install eggs and dependencies · c91c4722
      Jérome Perrin authored
      Instead of letting `python setup.py test` install the depencies, use
      buildout way of installing the eggs.
      
      This software use `interpreter` recipe of `zc.recipe.egg` to install a
      python with all eggs pre-installed. This is a way to get all the
      dependencies at install time instead of getting them at run time from
      pypi when running `python setup.py test`.
      `erp5.util.testsuite` has been extended to support a parameter to
      specify which python interpreter to use.
      
      One issue is that this way of installing eggs by buildout cause chicken
      and egg problem: cloning repository containing `slapos.recipe.cmmi`
      needs git, and to compiling git needs `slapos.recipe.cmmi`.
      The consequence of this is that re-running software will install too
      many parts again.
      One solution for this would be to clone `slapos.recipe.cmmi` with a
      `git` command provided by testnode or system package.
      Another solution would be to not install `slapos.recipe.cmmi` develop
      egg, simply install the egg from it's current pypi version while
      installing the software (running tests will be from the git checkout
      anyway).
      For now this is open issue.
      
      Another point of attention is that `python setup.py test` install the
      requirements listed in `test_requires`, but `zc.recipe.egg` does not
      provide a way of installing these. Some of our packages have `[test]`
      entrypoints, in this case, the software installs the test entrypoints.
      For others, we install the eggs.
      
      Other improvements:
       * use a simple `slapos.recipe:wrapper` instead of `slapos.cookbook:egg_test`
       * fix the typo in repository name erp5-util-repository ->
         erp5.util-repository ( this mean we will have to fix the test suites in
         nexedi ERP5 )
       * document "what is this software" and a scenario of how this software
         can be used to develop slapos eggs.
       * switch to buildout-hash.cfg for easier template hash management.
      c91c4722
  20. 28 Mar, 2018 1 commit
  21. 27 Mar, 2018 1 commit
    • Alain Takoudjou's avatar
      monitor: move scripts wrapper and logrotate conf to buildout, uses some new... · 47644132
      Alain Takoudjou authored
      monitor: move scripts wrapper and logrotate conf to buildout, uses some new promises from slapos.toolbox
      
      monitor was updated in slapos.toolbox to not generate promise launcher scripts anymore. All
      generated scripts are now in buildout.
      Monitor promise run script is removed from cron, slapgrid is used to run promises.
      Replace some old promises by the new ones from slapos.toolbox. Cleanup monitor configuration.
      Monitor report and monitor-promises directory are now obsolete.
      47644132
  22. 16 Mar, 2018 1 commit
  23. 12 Feb, 2018 1 commit
  24. 01 Feb, 2018 1 commit
  25. 31 Jan, 2018 3 commits
  26. 26 Jan, 2018 1 commit
  27. 20 Jun, 2017 1 commit
  28. 12 Jun, 2017 1 commit
  29. 02 Jun, 2017 1 commit
  30. 01 Jun, 2017 1 commit
  31. 12 Apr, 2017 1 commit
  32. 06 Apr, 2017 1 commit
  33. 03 Mar, 2017 1 commit
  34. 16 Feb, 2017 1 commit