Bug 508282 - Unable to list image tags on DockerHub

Refactored the code in the AbstractRegistry class to move the logic of
retrieving the tags by type of registry in private methods, and
implemented
the workflow to retrieve a Bearer token if needed when querying on
DockerHub.

Also, providing the resulting list of tags in a sorted, reverse order.

Added a few tests to verify the parsing of the 'Www-Authenticate'
response header,
and verify that the list of tags for an official image (eg: "php") and a
regular image (eg: "jboss/wildfly") can be retrieved. These tests are
temporarily ignored because they fail on Hudson (can the salve machine
connect to Docker Hub ?)

Also: refactored some loops to use the Stream API.

Change-Id: I60d7d71188e2e6e3d19a32e6fb1e53cb11605bf8
Signed-off-by: Xavier Coulon <xcoulon@redhat.com>
Reviewed-on: https://git.eclipse.org/r/85887
Tested-by: Hudson CI
Reviewed-by: Jeff Johnston <jjohnstn@redhat.com>
17 files changed
tree: 556cd72d03463da5361ba34937d28a2494fc5fef
  1. changelog/
  2. containers/
  3. gcov/
  4. gprof/
  5. javadocs/
  6. libhover/
  7. lttng/
  8. man/
  9. oprofile/
  10. perf/
  11. profiling/
  12. releng/
  13. rpm/
  14. systemtap/
  15. vagrant/
  16. valgrind/
  17. .gitignore
  18. pom.xml
  19. README.md
README.md

Contributing to Linux Tools

Thanks for your interest in this project.

Project description:

The Linux Tools project aims to bring a full-featured C and C++ IDE to Linux developers. We build on the source editing and debugging features of the CDT and integrate popular native development tools such as the GNU Autotools, Valgrind, OProfile, RPM, SystemTap, GCov, GProf, LTTng, etc. Current projects include LTTng trace viewers and analyzers, an RPM .spec editor, Autotools build integration, a Valgrind heap usage analysis tool, and OProfile call profiling tools. The project also provides a place for Linux distributions to collaboratively overcome issues surrounding distribution packaging of Eclipse technology. The project produces both best practices and tools related to packaging. One of our features is a source archive of the Eclipse SDK that can be used by all Linux distributions building and distributing it.

Developer resources:

Information regarding source code management, builds, coding standards, and more.

Contributor License Agreement:

Before your contribution can be accepted by the project, you need to create and electronically sign the Eclipse Foundation Contributor License Agreement (CLA).

Contact:

Contact the project developers via the project's “dev” list.

Search for bugs:

This project uses Bugzilla to track ongoing development and issues.

Create a new bug:

Be sure to search for existing bugs before you create another one. Remember that contributions are always welcome!