1. 13 Jan, 2021 1 commit
    • Jérome Perrin's avatar
      slapos-testing: don't pin tested eggs · 217f7f05
      Jérome Perrin authored
      We want the tests to use the code from the repository, but when we have a
      pinned version, buildout will use the code from repository only when the
      version from the repository match the version spec from the pin.
      
      The way slapos.recipe.template was pinned to 4.4 caused issues when we made
      a change in slapos.recipe.template to make it 4.5, because tests were no
      longer using code from slapos.recipe.template repository, but from 4.4 egg
      from pypi.
      
      To prevent this kind of issues, unset the slapos.recipe.template = 4.4
      version pin and also unset the version for all tested egg, to prevent
      similar issues if extended profiles also have version pins.
      217f7f05
  2. 12 Jan, 2021 5 commits
  3. 11 Jan, 2021 2 commits
  4. 08 Jan, 2021 2 commits
  5. 07 Jan, 2021 1 commit
  6. 05 Jan, 2021 1 commit
  7. 03 Jan, 2021 1 commit
  8. 31 Dec, 2020 3 commits
  9. 28 Dec, 2020 2 commits
  10. 24 Dec, 2020 4 commits
  11. 23 Dec, 2020 1 commit
  12. 22 Dec, 2020 2 commits
  13. 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
  14. 17 Dec, 2020 2 commits
  15. 16 Dec, 2020 1 commit
  16. 15 Dec, 2020 2 commits
  17. 14 Dec, 2020 2 commits
  18. 10 Dec, 2020 1 commit
  19. 09 Dec, 2020 3 commits