• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

OpenConext / OpenConext-engineblock-metadata
52%
master: 52%

Build:
Build:
LAST BUILD BRANCH: 3.1.2
DEFAULT BRANCH: master
Repo Added 24 Jan 2016 11:59AM UTC
Files 45
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

LAST BUILD ON BRANCH feature/support-push-pull-combination
branch: feature/support-push-pull-combination
CHANGE BRANCH
x
Reset
  • feature/support-push-pull-combination
  • 1.4.5
  • 2.0
  • 2.0.1
  • 2.1.0
  • 2.2.0
  • 2.2.1
  • 2.2.2
  • 2.2.3
  • 2.3.0
  • 2.4.0
  • 2.4.1
  • 2.4.2
  • 2.5.0
  • 3.0.0
  • 3.0.1
  • 3.1.0
  • 3.1.1
  • 3.1.2
  • engineblock5-compat
  • eol
  • feature/attribute-aggregation
  • feature/cached-repository-wayf-issue
  • feature/caching-metadata-repository
  • feature/change-behaviour-trusted-proxies
  • feature/configurable-signature-method
  • feature/doctrine-push-deletes
  • feature/remove-implicit-vo-id
  • feature/retrieve-attribute-source
  • feature/security-checker
  • feature/support-contact-telephone-number
  • feature/unconnected-idps-in-wayf
  • feature/upgrade-saml2-library
  • master
  • pr/7
  • release/3.x

pending completion
151

push

travis-ci

jorissteyn
Support combining the push and pull metadata backends

Using both the push and pull matadata backends did not work as
expected. When fetching ARP or entity manipulations, the first backend
that actually has the entity is used. But when fetching the list of
allowed idps of a service provider, all backends were queried and the
combined results were returned. This did not work for the pull backend
because it throws an error when queried about entities it does not
know about.

This commit fixes the issue by never using all backends, but only the
first backend that actually has the entity.

3 of 3 new or added lines in 1 file covered. (100.0%)

958 of 1843 relevant lines covered (51.98%)

2.91 hits per line

Relevant lines Covered
Build:
Build:
1843 RELEVANT LINES 958 COVERED LINES
2.91 HITS PER LINE
Source Files on feature/support-push-pull-combination
  • List 0
  • Changed 1
  • Source Changed 1
  • Coverage Changed 1
Coverage ∆ File Lines Relevant Covered Missed Hits/Line

Recent builds

Builds Branch Commit Type Ran Committer Via Coverage
151 feature/support-push-pull-combination Support combining the push and pull metadata backends Using both the push and pull matadata backends did not work as expected. When fetching ARP or entity manipulations, the first backend that actually has the entity is used. But when fetching th... push 14 Feb 2018 11:09AM UTC jorissteyn travis-ci pending completion  
149 feature/support-push-pull-combination Support combining the push and pull metadata backends Using both the push and pull matadata backends did not work as expected. When fetching ARP or entity manipulations, the first backend that actually has the entity is used. But when fetching th... push 14 Feb 2018 11:03AM UTC jorissteyn travis-ci pending completion  
147 feature/support-push-pull-combination Support combining the push and pull metadata backends Using both the push and pull matadata backends did not work as expected. When fetching ARP or entity manipulations, the first backend that actually has the entity is used. But when fetching th... push 14 Feb 2018 10:58AM UTC jorissteyn travis-ci pending completion  
146 feature/support-push-pull-combination Support combining the push and pull metadata backends Using both the push and pull matadata backends did not work as expected. When fetching ARP or entity manipulations, the first backend that actually has the entity is used. But when fetching th... push 14 Feb 2018 10:56AM UTC jorissteyn travis-ci pending completion  
See All Builds (103)
  • Repo on GitHub
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2025 Coveralls, Inc