Radish alpha
r
rad:zwTxygwuz5LDGBq255RA2CbNGrz8
Radicle CI broker
Radicle
Git
chore: update release 0.7.0
Merged liw opened 1 year ago

Signed-off-by: Lars Wirzenius liw@liw.fi

4 files changed +70 -2 938f6274 535b1592
modified Cargo.lock
@@ -1706,7 +1706,7 @@ dependencies = [

[[package]]
name = "radicle-ci-broker"
-
version = "0.6.3"
+
version = "0.7.0"
dependencies = [
 "anyhow",
 "clap",
modified Cargo.toml
@@ -1,6 +1,6 @@
[package]
name = "radicle-ci-broker"
-
version = "0.6.3"
+
version = "0.7.0"
edition = "2021"
rust-version = "1.80"
authors = ["Lars Wirzenius <liw@liw.fi", "cloudhead <cloudhead@radicle.xyz>"]
modified NEWS.md
@@ -4,6 +4,68 @@ This file summarizes the user-visible changes to `radicle-ci-broker`
between releases.


+
## Version 0.7.0, released 2024-10-14
+

+
This release breaks many existing instances. The event filter
+
configuration needs to be reviewed upon upgrade, and the event queue
+
in the database needs to be emptied before running the new version.
+

+
### Breaking changes
+

+
* Internally, the CI broker now converts change events from the
+
  Radicle node into "CI events". In previous versions of the CI broker
+
  it used "broker events". CI events are different from broker events,
+
  and aim to be more suitable for CI purposes. This also affects the
+
  event filter in the CI broker configuration. See the new [user
+
  guide](https://app.radicle.xyz/nodes/radicle.liw.fi/rad:zwTxygwuz5LDGBq255RA2CbNGrz8/tree/doc/userguide.md)
+
  for details on the CI events.
+
  
+
  Note that in some simple cases, the old broker events match a new CI
+
  event exactly, for filtering. As an example, a filter on a specific
+
  branch is the same.
+
  
+
  The CI event changes only affect the configuration file and the
+
  database. The CI adapters and the messages communicating with them
+
  are not affected. Existing adapters work as before.
+

+
### Bug fixes
+

+
* The CI broker no longer logs the sensitive environment variables in
+
  clear text. Fix by Michalis.
+

+
* The CI broker no longer appends a "shut down" event to the event
+
  queue when it loses connection to the local Radicle node. This was a
+
  remnant of an old development phase, used to tell other threads in
+
  the CI broker to terminate. There is now a better way to do that and
+
  the spurious event is not needed. In fact, the spurious event would
+
  be processed by the CI broker after it got re-started, meaning the
+
  new process would immediately terminate. Ars long, vita brevis.
+

+
* The log message of the CI broker process ending with an
+
  unrecoverable error is not logged at the error level instead of the
+
  info level.
+

+
### Other changes
+

+
* A start of a CI broker user guide (aimed at node operators) has been
+
  added to the source repository. It will be published by the CI
+
  broker's CI on <https://pages.radicle.liw.fi/ci-broker/>.
+

+
* The CI broker now enables logging in trace and debug levels in
+
  release builds.
+

+
* CI broker logging level can be set with new `--log-level` command
+
  line option. This functionality was dropped when structured logging
+
  was added. Note that the old way of controlling logging level with
+
  an environment variable is still absent. Please open an issue if you
+
  want it back.
+

+
* The CI broker now logs a lot more detail. Possibly too much detail.
+

+
* The `cibtool event add --base` options value is not rev-parsed. This
+
  means a value like `HEAD` or `HEAD^` will work. Previously it had to
+
  be a commit SHA.
+

## Version 0.6.3, released 2024-09-16

A very small release that I make mostly to keep up a weekly release
modified debian/changelog
@@ -1,3 +1,9 @@
+
radicle-ci-broker (0.7.0) unstable; urgency=medium
+

+
  * New release.
+

+
 -- Lars Wirzenius <liw@liw.fi>  Mon, 14 Oct 2024 11:09:05 +0300
+

radicle-ci-broker (0.6.3) unstable; urgency=medium

  * New release.