…pache#279)

This PR changes the way jenkins works to make cp-downstream-builds failures mark the build as unstable (yellow) rather than failed (red). We have previously seen committers treating red/failed builds as successful due to a lack of test failures, even though code may have failed to compile or jenkins workers may have exited with non-zero status codes.

We now also capture a text file with the downstream build number in it as a jenkins artifact.

…e#279)

TICKET = KAFKA-7016
LI_DESCRIPTION = The current code base has the stack trace of ApiExceptions disabled.
However, the stack trace can provide valuable information for troubleshooting.
Although getting the stack trace may be expensive, exceptions should happen rarely,
and thus it's better to pay the cost when they do happen.

EXIT_CRITERIA = When KAFKA-7016 is resolved and the changes are pulled in.

(cherry picked from commit 22868e2)

Co-authored-by: Lucas Wang <luwang@linkedin.com>

…e#279)

TICKET = KAFKA-7016
LI_DESCRIPTION = The current code base has the stack trace of ApiExceptions disabled.
However, the stack trace can provide valuable information for troubleshooting.
Although getting the stack trace may be expensive, exceptions should happen rarely,
and thus it's better to pay the cost when they do happen.

EXIT_CRITERIA = When KAFKA-7016 is resolved and the changes are pulled in.

(cherry picked from commit 22868e2)

Co-authored-by: Lucas Wang <luwang@linkedin.com>

…e#279)

TICKET = KAFKA-7016
LI_DESCRIPTION = The current code base has the stack trace of ApiExceptions disabled.
However, the stack trace can provide valuable information for troubleshooting.
Although getting the stack trace may be expensive, exceptions should happen rarely,
and thus it's better to pay the cost when they do happen.

EXIT_CRITERIA = When KAFKA-7016 is resolved and the changes are pulled in.

(cherry picked from commit 22868e2)

Co-authored-by: Lucas Wang <luwang@linkedin.com>

* chore(inkless:docker): use aivenoy docker organization for inkless image

* chore(inkless:demo): use published kafka image

* chore(inkless:docker): use aivenoy docker organization for inkless image

* chore(inkless:demo): use published kafka image

Single bulk apply of the Language Engine's IntelliJ-style format
profile across the kafka source tree. Pairs with the IntelliJ-real
control branch `intellij-formatting` for side-by-side comparison.

Engine state at apply time includes the following format fixes
landed against the language-engine repo:

  Pre-PR #11:
  - PR apache#275 multi-line // comment indent group
  - PR apache#276 BLANK_LINES_AROUND_CLASS + sibling no-op repair
  - PR apache#277 string-concat chain anchor preservation
  - PR apache#279 forward style through apply routes
  - PR apache#281 Result-tab line-number alignment
  - PR apache#282 spaces after return / throw / yield / instanceof
  - PR apache#283 chain-dot postfix preservation
  - PR apache#284 BlankLines sibling minimum.* conversion
  - PR apache#285 chain-dot single-anchor (N=1) preservation
  - PR apache#286 string-concat chain partial-cascade fix
  - PR apache#287 method-decl param re-align for misaligned source
  - PR apache#288 annotation-in-array-init indent

  Post-original-PR #11 (new in this re-apply):
  - PR apache#289 partial-cascade post-rewrite-anchor (4 shape fixes:
    chain-dot postfix follow-on, MI/NewClass close-paren cascade,
    ternary continuation, lambda body continuation)

Stats: 3101 files written, 0 failures, 2678 already-idempotent
files skipped (no_change). Corpus byte delta vs trunk: -510 bytes
(106275 insertions / 106785 deletions).