[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[hono-dev] Build failed in Jenkins: Hono-Website-Declarative-Pipeline #567
|
See <https://ci.eclipse.org/hono/job/Hono-Website-Declarative-Pipeline/567/display/redirect>
Changes:
------------------------------------------
[...truncated 87668 lines...]
</ul>
-<h3 id="fixes--enhancements-36">Fixes & Enhancements</h3>
+<h3 id="fixes--enhancements-37">Fixes & Enhancements</h3>
<ul>
<li>When a message arrived, the <em>message limit</em> checks failed to calculate the payload size
of the incoming message based on the configured <em>minimum message size</em>. Instead, it used the
@@ -1347,7 +1367,7 @@ Consequently, the C&C functionality of the Kerlink Lora provider which relie
method has been removed.</li>
</ul>
<h2 id="111">1.1.1</h2>
-<h3 id="fixes--enhancements-37">Fixes & Enhancements</h3>
+<h3 id="fixes--enhancements-38">Fixes & Enhancements</h3>
<ul>
<li>The <em>FireFly</em> LoRa adapter now supports mapping of the <em>mic</em> property.</li>
<li>A bug preventing the lora and SigFox adapters to start up correctly has been fixed.</li>
@@ -1392,7 +1412,7 @@ This is configured using the property <code>sendTimeOutInMs</code> in <code>org.
All future development of the chart will be done in the IoT Packages project only.
The deployment guide has been adapted accordingly.</li>
</ul>
-<h3 id="fixes--enhancements-38">Fixes & Enhancements</h3>
+<h3 id="fixes--enhancements-39">Fixes & Enhancements</h3>
<ul>
<li>Hono’s Helm chart now supports configuring resource requests and limits of the container images.</li>
<li>The MQTT adapter now includes a device’s MQTT client ID in its request to retrieve the device’s
@@ -1430,7 +1450,7 @@ Consequently, the C&C functionality of the Kerlink Lora provider which relie
method has been removed.</li>
</ul>
<h2 id="103">1.0.3</h2>
-<h3 id="fixes--enhancements-39">Fixes & Enhancements</h3>
+<h3 id="fixes--enhancements-40">Fixes & Enhancements</h3>
<ul>
<li>Hono’s Helm Chart now correctly configures Prometheus based resource limit checks if
a Prometheus server is being used for collecting metrics.</li>
@@ -1441,7 +1461,7 @@ to other services after a connection loss. This might result in fewer messages b
in such situations.</li>
</ul>
<h2 id="102">1.0.2</h2>
-<h3 id="fixes--enhancements-40">Fixes & Enhancements</h3>
+<h3 id="fixes--enhancements-41">Fixes & Enhancements</h3>
<ul>
<li>The example deployment now also works with Kubernetes 1.16 using Helm 2.15 and later.</li>
<li>The Hono chart can now also be deployed using the recently released Helm 3. In fact,
@@ -1463,7 +1483,7 @@ Note that with this option it is not supported for the authenticated gateway to
device that has last sent a telemetry or event message via this gateway.</li>
</ul>
<h2 id="101">1.0.1</h2>
-<h3 id="fixes--enhancements-41">Fixes & Enhancements</h3>
+<h3 id="fixes--enhancements-42">Fixes & Enhancements</h3>
<ul>
<li>The AMQP protocol adapter now requests devices to send traffic periodically in order
to prevent a time out of the connection. This way the adapter is able to detect and
@@ -1534,7 +1554,7 @@ All standard protocol adapters have been adapted to this change.
The <em>Tenant</em> JSON schema object used in the tenant related resources of the Device Registry Management API
has also been adapted to contain a list of trusted authorities instead of a single one.</li>
</ul>
-<h3 id="deprecations-7">Deprecations</h3>
+<h3 id="deprecations-8">Deprecations</h3>
<ul>
<li>The OpenShift specific source-to-image deployment model has been removed in
favor of the Helm charts and the Eclipse IoT Packages project. You can still
@@ -1571,7 +1591,7 @@ additional OpenTracing span parameter should be used.</li>
have been removed. The alternate variant of these methods which accepts an additional OpenTracing span parameter
should be used.</li>
</ul>
-<h3 id="deprecations-8">Deprecations</h3>
+<h3 id="deprecations-9">Deprecations</h3>
<ul>
<li>The deprecated Kura adapter is no longer deployed by default by the Helm chart.
However, it can still be deployed by means of <a href="https://www.eclipse.org/hono/docs/deployment/helm-based-deployment/#deploying-optional-adapters";>setting a configuration property</a>.</li>
@@ -1590,7 +1610,7 @@ and command messages are calculated in accordance with the <em>minimum message s
protocol adapters and then recorded in the metrics system.
See <a href="https://www.eclipse.org/hono/docs/api/metrics/#minimum-message-size";>Metrics</a> for more details.</li>
</ul>
-<h3 id="fixes--enhancements-42">Fixes & Enhancements</h3>
+<h3 id="fixes--enhancements-43">Fixes & Enhancements</h3>
<ul>
<li>The automatic reconnect handling of the <code>HonoConnection</code> implementation has been
improved and now applies an exponential back-off algorithm. The behavior can be
@@ -1688,7 +1708,7 @@ contains an exemplary implementation of this API included in the device registry
to be able to set and retrieve information about the connections from devices or gateways to the protocol adapters.</li>
<li>This version implements the new HTTP management API for tenants, devices, and credentials.</li>
</ul>
-<h3 id="fixes--enhancements-43">Fixes & Enhancements</h3>
+<h3 id="fixes--enhancements-44">Fixes & Enhancements</h3>
<ul>
<li>The Hono Sandbox’s protocol adapters support using the gateway mode again.</li>
<li>The <a href="/hono/getting-started/">Getting Started</a> guide has been rewritten
@@ -1758,7 +1778,7 @@ Please refer to the <a href="https://www.eclipse.org/hono/docs/concepts/resource
the <a href="https://www.eclipse.org/hono/docs/user-guide/sigfox-adapter/";>Sigfox protocol adapter</a>
documentation to learn more about pre-requisites and limitations.</li>
</ul>
-<h3 id="fixes--enhancements-44">Fixes & Enhancements</h3>
+<h3 id="fixes--enhancements-45">Fixes & Enhancements</h3>
<ul>
<li>vert.x has been updated to version 3.7.0.</li>
</ul>
@@ -1788,13 +1808,13 @@ the <code>to</code> property to be set to <code>control/${tenant_id}/${device_id
as sender link address is still possible but gateway agnostic addressing of devices is not supported for
such command messages.</li>
</ul>
-<h3 id="deprecations-9">Deprecations</h3>
+<h3 id="deprecations-10">Deprecations</h3>
<ul>
<li>Instructions for script based deployment to Kubernetes have been removed from the deployment guide.
Using Helm is now the only supported way of deploying Hono to Kubernetes.</li>
</ul>
<h2 id="10-m3">1.0-M3</h2>
-<h3 id="fixes--enhancements-45">Fixes & Enhancements</h3>
+<h3 id="fixes--enhancements-46">Fixes & Enhancements</h3>
<ul>
<li>The protocol adapters add tracing information about invocations of the Device Registry
services again.</li>
@@ -1812,7 +1832,7 @@ the maximum number of device connections to be allowed per tenant can be configu
adapters can be enabled to verify this connection limit before accepting any new connections. Please
refer to the <a href="https://www.eclipse.org/hono/docs/concepts/resource-limits/";>resource limits</a> for details.</li>
</ul>
-<h3 id="fixes--enhancements-46">Fixes & Enhancements</h3>
+<h3 id="fixes--enhancements-47">Fixes & Enhancements</h3>
<ul>
<li>The base classes for implementing the AMQP and HTTP endpoints for the Credentials, Tenant
and Device Registration APIs now create an OpenTracing Span for tracking the
@@ -1911,7 +1931,7 @@ adapters are located in that package already.</li>
<code>org.eclipse.hono.client.HonoConnection</code> to better reflect its sole responsibility
for establishing (and maintaining) the connection to a Hono service endpoint.</li>
</ul>
-<h3 id="deprecations-10">Deprecations</h3>
+<h3 id="deprecations-11">Deprecations</h3>
<ul>
<li>The optional operations defined by the Tenant, Device Registration and Credentials API
have been deprecated. They will be removed from Hono 1.0 altogether.
@@ -1936,7 +1956,7 @@ to decouple the sender and receiver from each other.</li>
<li>The <code>org.eclipse.hono.service.tenant.CompleteBaseTenantService</code> class now rejects malformed
encodings of public keys/certificates included in a request to add a trust anchor to a tenant.</li>
</ul>
-<h3 id="deprecations-11">Deprecations</h3>
+<h3 id="deprecations-12">Deprecations</h3>
<ul>
<li>The <code>HonoClient.closeCommandConsumer()</code> method will be removed in Hono 1.0.
The <code>CommandConsumer.close()</code> method should be used instead.</li>
@@ -1952,7 +1972,7 @@ to prevent running out of resources. Please refer to
<li>The new <em>Helm deployment</em> for Kubernetes has been added. Please refer to
<a href="https://www.eclipse.org/hono/docs/deployment/helm-based-deployment/";>Helm based deployment guide</a> for details.</li>
</ul>
-<h3 id="fixes--enhancements-47">Fixes & Enhancements</h3>
+<h3 id="fixes--enhancements-48">Fixes & Enhancements</h3>
<ul>
<li><code>org.eclipse.hono.util.RequestResponseResult</code> now provides access to AMQP application-properties conveyed in the
response message.</li>
@@ -1986,7 +2006,7 @@ accept the tenant and device IDs as parameters.</li>
connection establishment but also for the SASL handshake and the exchange of the AMQP <em>open</em> frame.</li>
<li>The (already deprecated) Hono Messaging component has been removed from Hono.</li>
</ul>
-<h3 id="deprecations-12">Deprecations</h3>
+<h3 id="deprecations-13">Deprecations</h3>
<ul>
<li>The script based deployment to Kubernetes has been deprecated and will be removed in the next version.
The Helm based deployment should be used instead.</li>
@@ -2001,7 +2021,7 @@ will be removed in the next version. Custom protocol adapters should use
<li>The MQTT protocol adapter now supports authentication of devices using X.509 client certificates. Please refer to
the <a href="https://www.eclipse.org/hono/docs/user-guide/mqtt-adapter/";>MQTT adapter user guide</a> for details regarding configuration.</li>
</ul>
-<h3 id="fixes--enhancements-48">Fixes & Enhancements</h3>
+<h3 id="fixes--enhancements-49">Fixes & Enhancements</h3>
<ul>
<li>
<p>The OpenShift <em>source-to-image</em> (S2I) deployment is now the default
@@ -2041,7 +2061,7 @@ that a message has been received over, has been replaced by the generic <em>comp
of the component that a metric has been reported by. Please refer to the <a href="https://www.eclipse.org/hono/docs/api/metrics/";>Metrics API</a>
for details. Note that these changes do not affect the legacy Graphite based metrics back end.</li>
</ul>
-<h3 id="deprecations-13">Deprecations</h3>
+<h3 id="deprecations-14">Deprecations</h3>
<ul>
<li>The Hono Messaging component is now deprecated and will be removed from Hono in version 0.9 altogether.
The example deployment has not been using Hono Messaging since 0.6 and there is no practical reason for
@@ -2059,7 +2079,7 @@ Please refer to the <a href="https://www.eclipse.org/hono/docs/admin-guide/monit
<em>on-the-fly</em> hashing of clear text passwords contained in <em>hashed-password</em> credentials. Please refer to the
<a href="https://www.eclipse.org/hono/docs/user-guide/device-registry/#managing-credentials";>Device Registry user guide</a> for details.</li>
</ul>
-<h3 id="fixes--enhancements-49">Fixes & Enhancements</h3>
+<h3 id="fixes--enhancements-50">Fixes & Enhancements</h3>
<ul>
<li>The base classes for implementing the Device Registration and Tenant APIs have been instrumented
with OpenTracing. New variants of the <code>RegistrationService.assertRegistration</code>, <code>TenantService.get</code> and <code>CredentialsService.get</code>
+ 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-567'
[master 0678598d0c] Website build Hono-Website-Declarative-Pipeline-567
1011 files changed, 26000 insertions(+), 25993 deletions(-)
+ git log --graph --abbrev-commit --date=relative -n 5
* commit 0678598d0c
| Author: Hono Bot <hono-bot@xxxxxxxxxxx>
| Date: 20 seconds ago
|
| Website build Hono-Website-Declarative-Pipeline-567
|
| Signed-off-by: Hono Bot <hono-bot@xxxxxxxxxxx>
|
* commit 4e35eea196
| Author: Hono Bot <hono-bot@xxxxxxxxxxx>
| Date: 6 days ago
|
| Website build Hono-Website-Declarative-Pipeline-561
|
| Signed-off-by: Hono Bot <hono-bot@xxxxxxxxxxx>
|
* commit 188707bd8a
| Author: Hono Bot <hono-bot@xxxxxxxxxxx>
| Date: 8 days ago
|
| Website build Hono-Website-Declarative-Pipeline-557
|
| Signed-off-by: Hono Bot <hono-bot@xxxxxxxxxxx>
|
* commit f07b23b3bb
| Author: Hono Bot <hono-bot@xxxxxxxxxxx>
| Date: 12 days ago
|
| Website build Hono-Website-Declarative-Pipeline-553
|
| Signed-off-by: Hono Bot <hono-bot@xxxxxxxxxxx>
|
* commit d7cce066ef
| Author: Hono Bot <hono-bot@xxxxxxxxxxx>
| Date: 2 weeks ago
|
| Website build Hono-Website-Declarative-Pipeline-549
|
| 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 640 killed;
[ssh-agent] Stopped.
[Pipeline] // sshagent
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Declarative: Post Actions)
[Pipeline] step
