1. 18 Jan, 2021 1 commit
  2. 15 Jan, 2021 4 commits
  3. 14 Jan, 2021 1 commit
  4. 13 Jan, 2021 5 commits
  5. 12 Jan, 2021 5 commits
  6. 11 Jan, 2021 2 commits
  7. 08 Jan, 2021 2 commits
  8. 07 Jan, 2021 1 commit
  9. 05 Jan, 2021 1 commit
  10. 03 Jan, 2021 1 commit
  11. 31 Dec, 2020 3 commits
  12. 28 Dec, 2020 2 commits
  13. 24 Dec, 2020 4 commits
  14. 23 Dec, 2020 1 commit
  15. 22 Dec, 2020 2 commits
  16. 21 Dec, 2020 4 commits
    • Jérome Perrin's avatar
      cafa2ec5
    • Jérome Perrin's avatar
      software/erp5: simple SlapOS upgrade test · 8a61ff90
      Jérome Perrin authored
      Confirms SlapOS ERP5 software release can be updated from
      a reference version to current version
      8a61ff90
    • Jérome Perrin's avatar
      stack/erp5: new promise to check software release URL of zope instances · a8271791
      Jérome Perrin authored
      When root instance is updated to a new software release URL, it will re-request
      all the instances with the new software release URL.
      To make sure the new root instance does not appear has ready when it is
      re-requested with new software release URL, introduce a promise that will check
      that the instances requested by the root instance have the same software
      release URL. For now we do this only for Zope instances, because they are
      stateless and restart automatically on configuration changes, unlike stateful
      instances like mariadb or ZEO that we don't restart automatically (yet ?).
      a8271791
    • Jérome Perrin's avatar
      stack/erp5: restart zopes on configuration changes · 59745322
      Jérome Perrin authored
      We are using this pattern for most of our services since several
      months without any issue, so let's also use it for zopes. This
      makes automatic upgrade possible.
      
      Also remove "zope running current products" promise, since we
      restart we no longer need to check this.
      59745322
  17. 17 Dec, 2020 1 commit
    • Léo-Paul Géneau's avatar
      software/jupyter: move to python 3 · b15cac5f
      Léo-Paul Géneau authored
      moves python2 release to component/jupyter-py2 because it is required by ERP5
      but not maintained anymore
      
      moves to python 3 :
      - test/test.py
      - jupyter_notebook_config.py.jinja
      - ERP5kernel.py
      
      modifies custom.js to create a workaround for events issue
      see (https://github.com/jupyter/notebook/issues/2499)
      
      upgrades slapos.cookbook version to 1.0.171 to use zero_knowledge recipe
      with python 3
      
      adds jupyter partition check in software/erp5/test/test_erp5.py
      b15cac5f