Skip to content
Snippets Groups Projects
  1. Apr 04, 2020
    • Andreas Jaeger's avatar
      Update hacking for Python3 · 45448976
      Andreas Jaeger authored
      The repo is Python 3 now, so update hacking to version 3.0 which
      supports Python 3.
      
      Fix problems found by updated hacking version.
      
      Remove hacking and friends from lower-constraints, they are not needed
      during installation.
      
      Change-Id: I7ef5ac8a89e94f5da97780198619b6facc86ecfe
      45448976
  2. Oct 23, 2019
  3. Dec 27, 2018
    • confi-surya's avatar
      Update hacking version · b41309ef
      confi-surya authored
      Use latest release 1.1.0 and compatible changes w.r.t pep8
      
      Change-Id: Ie5e5417a1d8481bb59d516a320bd7cc1dd89591e
      b41309ef
  4. Jul 24, 2018
  5. Jun 08, 2018
  6. May 21, 2018
  7. May 09, 2018
    • ghanshyam's avatar
      Gate fix: Cap hacking to avoid gate failure · ccd542f7
      ghanshyam authored
      hacking is not capped in g-r and it is in
      blacklist for requirement as hacking new version
      can break the gate jobs.
      
      Hacking can break gate jobs because of various
      reasons:
      - There might be new rule addition in hacking
      - Some rules becomes default from non-default
      - Updates in pycodestyle etc
      
      That was the main reason it was not added in g-r
      auto sync also. Most of the project maintained the
      compatible and cap the hacking version in
      test-requirements.txt and update to new version when
      project is ready. Bumping new version might need code
      fix also on project side depends on what new in that
      version.
      
      If project does not have cap the hacking version then,
      there is possibility of gate failure whenever new hacking
      version is released by QA team.
      
      Example of such failure in recent release of hacking 1.1.0
      - http://lists.openstack.org/pipermail/openstack-dev/2018-May/130282.html
      
      Change-Id: I05790c5f946a4127fe6c8d9867cc618cb83d67fb
      ccd542f7
  8. Mar 15, 2018
  9. Mar 14, 2018
  10. Mar 10, 2018
  11. Mar 06, 2018
  12. Jan 24, 2018
  13. Jan 17, 2018
  14. Jan 16, 2018
  15. Nov 16, 2017
  16. Sep 26, 2017
  17. Sep 13, 2017
  18. Sep 12, 2017
  19. Sep 06, 2017
  20. Jul 27, 2017
  21. Jul 14, 2017
  22. Jul 02, 2017
  23. Jun 27, 2017
  24. Jun 06, 2017
  25. May 22, 2017
  26. May 15, 2017
  27. Apr 06, 2017
    • Mohammed Naser's avatar
      Remove graphiz from test-requirements.txt · 034a0f58
      Mohammed Naser authored
      With the split of kolla and kolla-ansible, it seems that this
      dependency was carried over as it is used when generating
      graphs for build sequences.
      
      This patch removes it as the build process is not part of this
      project anymore.
      
      Change-Id: I7fd59fe703c2f06c003c8acda15f2a06d3fd7f3f
      034a0f58
    • Mohammed Naser's avatar
      Remove python-swiftclient from test-requirements.txt · 85b9da45
      Mohammed Naser authored
      It seems that it was added back in Liberty where an effort was
      started to setup functional tests, however it is not used at the
      moment.
      
      This patch removes it from the list of dependencies.  With time,
      Tempest should handle all integration checks.
      
      Change-Id: I9e1990e93abc6e3001f499ccc8d40b6104ed2d93
      85b9da45
    • Mohammed Naser's avatar
      Remove python-heatclient from test-requirements.txt · d6bd9e6b
      Mohammed Naser authored
      It seems that it was added back in Liberty where an effort was
      started to setup functional tests, however it is not used at the
      moment.
      
      This patch removes it from the list of dependencies.  With time,
      Tempest should handle all integration checks.
      
      Change-Id: Ieb3a000eda58dcb642cbd099273c91ad355bfb85
      d6bd9e6b
    • Mohammed Naser's avatar
      Remove python-barbicanclient from test-requirements.txt · c014d69b
      Mohammed Naser authored
      It seems that it was added back in Liberty where an effort was
      started to setup functional tests, however it is not used at the
      moment.
      
      This patch removes it from the list of dependencies.  With time,
      Tempest should handle all integration checks.
      
      Change-Id: I9dddd470db9dc42a6fa7dbe138c0c6189d8afdd7
      c014d69b
  28. Mar 29, 2017
  29. Feb 15, 2017
  30. Jan 27, 2017
  31. Jan 16, 2017
  32. Dec 05, 2016
  33. Nov 27, 2016
  34. Nov 23, 2016
  35. Nov 02, 2016
  36. Oct 19, 2016
  37. Oct 12, 2016
    • Jeffrey Zhang's avatar
      Move graphviz dependency to test stage · c0fd4389
      Jeffrey Zhang authored
      Graphviz is only helpful and used for developer. It is useless for
      deployment. So move it to test-requirements.txt file and warning users
      when he wants to save dependency feature.
      
      TrivialFix
      
      Change-Id: Id8de76baa6f1455ad032abe4738d9779cf0cc5a6
      c0fd4389
Loading