[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[hono-dev] Build failed in Jenkins: Hono-Website-Declarative-Pipeline #524
|
See <https://ci.eclipse.org/hono/job/Hono-Website-Declarative-Pipeline/524/display/redirect>
Changes:
------------------------------------------
[...truncated 105894 lines...]
<ul>
<li>The <code>hono.kafka.defaultClientIdPrefix</code> configuration property needs to be removed from existing configurations.
Configuring parts of the created Kafka client identifiers should usually not be needed any more. To still set a custom
@@ -505,7 +515,7 @@ file system while the latter keeps all data in memory only.</li>
of existing data. In real life deployments this feature has no meaning because write access to data will need to
be authorized more explicitly anyway, e.g. at the tenant level.</li>
</ul>
-<h2 id="api-changes-2">API Changes</h2>
+<h2 id="api-changes-3">API Changes</h2>
<ul>
<li>The client classes used by the protocol adapters for accessing the device registry, the Command Router
and the south bound C&C APIs have been reorganized into dedicated modules.
@@ -718,7 +728,7 @@ Please refer to the
<a href="https://www.eclipse.org/hono/docs/admin-guide/common-config/#resource-limits-checker-configuration";>Protocol Adapter Common Configuration guide</a>
for details.</li>
</ul>
-<h3 id="api-changes-3">API Changes</h3>
+<h3 id="api-changes-4">API Changes</h3>
<ul>
<li>The already deprecated classes <code>org.eclipse.hono.service.cache.SpringBasedExpiringValueCache</code> and
<code>org.eclipse.hono.service.cache.SpringCacheProvider</code> have been removed.</li>
@@ -919,7 +929,7 @@ content type is set, as it is also done for telemetry/event HTTP requests with n
<li>There were errors sending Connection Events via the Events API if the corresponding tenant didn’t
have a non-default <code>max-ttl</code> resource limit configuration. This has been fixed.</li>
</ul>
-<h3 id="api-changes-4">API Changes</h3>
+<h3 id="api-changes-5">API Changes</h3>
<ul>
<li>The deprecated configuration property <code>singleTenant</code> of the protocol adapters and the device registry has been removed.</li>
<li>The default pattern for valid device identifiers used for the file based and the MongoDB based registry
@@ -976,7 +986,7 @@ update Credentials request. This has been fixed.</li>
<li>The AMQP protocol adapter did accept messages from clients (devices) exceeding the adapter’s configured
max-message-size. This has been fixed and the adapter now closes the link to the device in this case.</li>
</ul>
-<h3 id="api-changes-5">API Changes</h3>
+<h3 id="api-changes-6">API Changes</h3>
<ul>
<li>The default pattern for valid device identifiers used for the file based and the MongoDB based registry
implementations now also contains a colon (<code>:</code>) for compatibility with Eclipse Ditto.</li>
@@ -1045,7 +1055,7 @@ update Credentials request. This has been fixed.</li>
<li>The AMQP protocol adapter did accept messages from clients (devices) exceeding the adapter’s configured
max-message-size. This has been fixed and the adapter now closes the link to the device in this case.</li>
</ul>
-<h3 id="api-changes-6">API Changes</h3>
+<h3 id="api-changes-7">API Changes</h3>
<ul>
<li>The default pattern for valid device identifiers used for the file based and the MongoDB based registry
implementations now also contains a colon (<code>:</code>) for compatibility with Eclipse Ditto.</li>
@@ -1115,7 +1125,7 @@ DTLS handshake. This will allow the adapter to handle a lot more handshakes conc
The adapter also employs a more efficient message de-duplicator which reduces the adapter’s
memory footprint.</li>
</ul>
-<h3 id="api-changes-7">API Changes</h3>
+<h3 id="api-changes-8">API Changes</h3>
<ul>
<li>The <code>getRemoteContainer</code> method in <code>org.eclipse.hono.client.HonoConnection</code> has been
renamed to <code>getRemoteContainerId</code>.</li>
@@ -1177,7 +1187,7 @@ no global expiration configuration is needed anymore for the cache.</li>
<li>Protocol adapters failed to re-establish receiver links for commands to be routed after loss
of connection to the AMQP Messaging Network. This has been fixed.</li>
</ul>
-<h3 id="api-changes-8">API Changes</h3>
+<h3 id="api-changes-9">API Changes</h3>
<ul>
<li>The <code>org.eclipse.hono.client.DeviceRegistration</code> interface’s <em>get</em> methods have been removed
because the Device Registration API does not define a corresponding operation.
@@ -1248,7 +1258,7 @@ be implemented.</li>
both systems. A command response message from a device will by default be forwarded using the messaging system
that the corresponding command message was received in.</li>
</ul>
-<h3 id="api-changes-9">API Changes</h3>
+<h3 id="api-changes-10">API Changes</h3>
<ul>
<li>The device registry credentials endpoint will no longer hand out sensitive details for hashed-password secrets.
<code>pwd-hash</code>, <code>salt</code> and <code>hash-function</code> are stored by the device registry but not returned to the user.
@@ -1268,7 +1278,7 @@ can be referenced in a device’s <em>viaGroups</em> property in order to au
of any of the groups to act on behalf of the device.</li>
</ul>
<h2 id="112">1.1.2</h2>
-<h3 id="api-changes-10">API Changes</h3>
+<h3 id="api-changes-11">API Changes</h3>
<ul>
<li>The <code>org.eclipse.hono.client.DeviceRegistration</code> interface’s <em>get</em> methods have been removed
because the Device Registration API does not define a corresponding operation.
@@ -1341,7 +1351,7 @@ and for configuring a heath check server have been fixed.</li>
contain any payload. Such responses are useful to only convey a status code in reply to
a command.</li>
</ul>
-<h3 id="api-changes-11">API Changes</h3>
+<h3 id="api-changes-12">API Changes</h3>
<ul>
<li>The already deprecated endpoints with the <code>control</code> prefix have been removed. The northbound and southbound
Command & Control endpoints can now only be used with the <code>command</code> and <code>command_response</code> prefixes
@@ -1351,7 +1361,7 @@ address pattern. This is now used for internal communication between protocol ad
<li>The <code>create</code> method in <code>org.eclipse.hono.client.HonoConnection</code> now requires its Vertx parameter to be not null.</li>
</ul>
<h2 id="104">1.0.4</h2>
-<h3 id="api-changes-12">API Changes</h3>
+<h3 id="api-changes-13">API Changes</h3>
<ul>
<li>The <code>org.eclipse.hono.client.DeviceRegistration</code> interface’s <em>get</em> methods have been removed
because the Device Registration API does not define a corresponding operation.
@@ -1440,7 +1450,7 @@ applications will get notified of such a subscription along with the specific de
<li>Now a <em>max-ttd</em> value, which is used as an upper boundary for the <em>hono-ttd</em> value specified by the devices,
can be set as an <em>extension</em> property in the adapters section of the tenant configuration.</li>
</ul>
-<h3 id="api-changes-13">API Changes</h3>
+<h3 id="api-changes-14">API Changes</h3>
<ul>
<li>The already deprecated <em>legacy metrics</em> support has been removed.</li>
<li>The already deprecated <em>legacy device registry</em> and the corresponding base classes, which had been deprecated
@@ -1488,7 +1498,7 @@ might only record a certain percentage of traces). See
<a href="https://www.eclipse.org/hono/docs/admin-guide/monitoring-tracing-config/#enforcing-the-recording-of-traces-for-a-tenant";>Monitoring & Tracing</a>
for more details.</li>
</ul>
-<h3 id="api-changes-14">API Changes</h3>
+<h3 id="api-changes-15">API Changes</h3>
<ul>
<li>The obsolete method variants of <code>reportTelemetry</code> in <code>org.eclipse.hono.service.metric.Metrics</code>
have been removed. The new variants of this method accept an additional parameter of type <code>TenantObject</code>.</li>
@@ -1534,7 +1544,7 @@ server (using different ports)
Refer to the <a href="https://www.eclipse.org/hono/docs/admin-guide/monitoring-tracing-config";>Monitoring configuration guide</a>
for details.</li>
</ul>
-<h3 id="api-changes-15">API Changes</h3>
+<h3 id="api-changes-16">API Changes</h3>
<ul>
<li>With the implementation of the new HTTP management API for the device registry,
the class hierarchy for implementing device registry was significantly
@@ -1625,7 +1635,7 @@ to use the <a href="/hono/sandbox/">Hono Sandbox</a> or a local Minikube cluster
instead of Docker Swarm.</li>
<li>The MQTT adapter now closes the network connection to device on publish failures.</li>
</ul>
-<h3 id="api-changes-16">API Changes</h3>
+<h3 id="api-changes-17">API Changes</h3>
<ul>
<li>The optional methods of the <a href="https://www.eclipse.org/hono/docs/api/tenant/";>Tenant API</a> have been
removed. Implementations of the Tenant API are encouraged to expose the <em>tenants</em> endpoint defined by
@@ -1691,7 +1701,7 @@ documentation to learn more about pre-requisites and limitations.</li>
<ul>
<li>vert.x has been updated to version 3.7.0.</li>
</ul>
-<h3 id="api-changes-17">API Changes</h3>
+<h3 id="api-changes-18">API Changes</h3>
<ul>
<li>The <code>org.eclipse.hono.util.RegistrationConstants.FIELD_DEFAULTS</code> constant
has been renamed to <code>org.eclipse.hono.util.RegistrationConstants.FIELD_PAYLOAD_DEFAULTS</code>.</li>
@@ -1757,7 +1767,7 @@ and deployment entries for the <code>device-identities.json</code>.</li>
<li>Before uploading command responses, the MQTT and AMQP adapters now check whether the device is
registered and also the adapter is enabled for the tenant.</li>
</ul>
-<h3 id="api-changes-18">API Changes</h3>
+<h3 id="api-changes-19">API Changes</h3>
<ul>
<li>The <code>hono-client</code> module has undergone several major and incompatible changes. The most
important change affects the <code>HonoClient</code> interface which no longer serves as a factory
@@ -1891,7 +1901,7 @@ the <code>via</code> property of the device’s registration information may
multiple strings. Based on this, a device can now be configured to connect via arbitrary gateways instead of just a single
one.</li>
</ul>
-<h3 id="api-changes-19">API Changes</h3>
+<h3 id="api-changes-20">API Changes</h3>
<ul>
<li>The layout and structure of the metrics reported by Hono have been changed substantially. Many of the existing meters and tags
have been changed or replaced in order to provide a more consistent set of metrics and increase the value of the information
@@ -1962,7 +1972,7 @@ for details regarding the new configuration variables.</p>
</ul>
</li>
</ul>
-<h3 id="api-changes-20">API Changes</h3>
+<h3 id="api-changes-21">API Changes</h3>
<ul>
<li>Some of the <em>tags</em> used by Hono’s components when reporting metrics have been changed. The common tag <em>component</em>
has been renamed to <em>component-type</em>. The <em>protocol</em> tag formerly used by adapters to indicate the transport protocol
@@ -1999,7 +2009,7 @@ passed on to the <code>assertRegistration</code> method and finished eventually.
based on <code>BaseTenantService</code> concerning the <code>get</code> method and to <code>CredentialsService</code> implementations based on
<code>BaseCredentialsService</code> concerning the <code>get</code> method.</li>
</ul>
-<h3 id="api-changes-21">API Changes</h3>
+<h3 id="api-changes-22">API Changes</h3>
<ul>
<li>The <code>org.eclipse.hono.service.credentials.CompleteBaseCredentialsService</code> class now requires an
<code>org.eclipse.hono.auth.HonoPasswordEncoder</code> to be passed into its constructor.
+ echo 'Changes have been detected, publishing to repo '\''www.eclipse.org/hono'\'''
Changes have been detected, publishing to repo 'www.eclipse.org/hono'
+ git config user.email hono-bot@xxxxxxxxxxx
+ git config user.name 'Hono Bot'
+ git commit -s -m 'Website build Hono-Website-Declarative-Pipeline-524'
[master 3d3e8d22e6] Website build Hono-Website-Declarative-Pipeline-524
1016 files changed, 27828 insertions(+), 37069 deletions(-)
rewrite docs/user-guide/file-based-device-registry/index.html (100%)
+ git log --graph --abbrev-commit --date=relative -n 5
* commit 3d3e8d22e6
| Author: Hono Bot <hono-bot@xxxxxxxxxxx>
| Date: 12 seconds ago
|
| Website build Hono-Website-Declarative-Pipeline-524
|
| Signed-off-by: Hono Bot <hono-bot@xxxxxxxxxxx>
|
* commit 027e44b0a9
| Author: Hono Bot <hono-bot@xxxxxxxxxxx>
| Date: 3 days ago
|
| Website build Hono-Website-Declarative-Pipeline-521
|
| Signed-off-by: Hono Bot <hono-bot@xxxxxxxxxxx>
|
* commit 7ad561a561
| Author: Hono Bot <hono-bot@xxxxxxxxxxx>
| Date: 4 days ago
|
| Website build Hono-Website-Declarative-Pipeline-520
|
| Signed-off-by: Hono Bot <hono-bot@xxxxxxxxxxx>
|
* commit 09b0f77550
| Author: Hono Bot <hono-bot@xxxxxxxxxxx>
| Date: 7 days ago
|
| Website build Hono-Website-Declarative-Pipeline-517
|
| Signed-off-by: Hono Bot <hono-bot@xxxxxxxxxxx>
|
* commit 3401ad5c5a
| Author: Hono Bot <hono-bot@xxxxxxxxxxx>
| Date: 8 days ago
|
| Website build Hono-Website-Declarative-Pipeline-516
|
| Signed-off-by: Hono Bot <hono-bot@xxxxxxxxxxx>
+ git push origin HEAD:refs/heads/master
error: pack-objects died of signal 9
error: pack-objects died of signal 9
error: remote unpack failed: error Packfile is truncated.
fatal: Unpack error, check server log
error: failed to push some refs to 'ssh://genie.hono@xxxxxxxxxxxxxxx:29418/www.eclipse.org/hono.git'
[Pipeline] }
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 559 killed;
[ssh-agent] Stopped.
[Pipeline] // sshagent
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Declarative: Post Actions)
[Pipeline] step
