1. 18 May, 2019 1 commit
  2. 04 Feb, 2019 8 commits
  3. 03 Dec, 2018 1 commit
  4. 04 Oct, 2018 1 commit
  5. 06 Sep, 2018 1 commit
  6. 31 Aug, 2018 1 commit
    • component/firefox: simplify profile · 654ac2e1
      Major change is that slapos compatible wrapper is no longer installed in
      parts/firefox/firefox-slapos , but directly as "firefox" in the
      buildout:bin-directory of the software profile.
      geckodriver is also in the same buildout:bin-directory.
      This way, softwares using this just need to add
      buildout:bin-directory to $PATH
      
      erp5testnode knows since
      nexedi/erp5@59ee7970
      that it should look for firefox in buildout:bin-directory of the
      installed SR, so we should not need backward compatibility here.
      
      Adjust seleniumrunner and jstestnode for the changes
      
      Also drop unused firefox 45
      
      Jérome changes from original 8cf6908df752b9e7632b2910ffc85027f1f4f22c :
       - name sections [firefox-wrapper] and [firefox] because including the
      version in section name means we have to also update section name when
      we update version. Users have to be careful of installing
      ${firefox-wrapper:} and not ${firefox:}
       - introduce macros for implementation and simple section using the
      macros, to make it easy to had more versions or to increase versions,
      for both firefox and geckodriver. They are slightly different because
      for firefox we need a wrapper, but geckodriver is usable directly.
       - use same version, the "versions up" will be separate commits.
       - now that seleniumrunner and jstestnode are using buildout.hash.cfg,
      md5sums are in separate files.
      
      Co-authored-by: Jérome Perrin <jerome@nexedi.com>
      Julien Muchembled committed
  7. 30 Aug, 2018 1 commit
  8. 22 Jun, 2018 1 commit
  9. 22 May, 2018 2 commits
  10. 16 Apr, 2018 1 commit
  11. 04 Apr, 2018 1 commit
    • slapos-testing: rework to use buildout to install eggs and dependencies · c91c4722
      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.
      Jérome Perrin committed
  12. 28 Mar, 2018 1 commit
  13. 27 Mar, 2018 1 commit
    • monitor: move scripts wrapper and logrotate conf to buildout, uses some new… · 47644132
      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.
      Alain Takoudjou committed
  14. 16 Mar, 2018 1 commit
  15. 12 Feb, 2018 1 commit
  16. 01 Feb, 2018 1 commit
  17. 31 Jan, 2018 3 commits
  18. 26 Jan, 2018 1 commit
  19. 20 Jun, 2017 1 commit
  20. 12 Jun, 2017 1 commit
  21. 02 Jun, 2017 1 commit
  22. 01 Jun, 2017 1 commit
  23. 12 Apr, 2017 1 commit
  24. 06 Apr, 2017 1 commit
  25. 03 Mar, 2017 1 commit
  26. 16 Feb, 2017 1 commit