davsclaus opened a new pull request, #3214:
URL: https://github.com/apache/camel-kamelets/pull/3214

   `JiraIT` fails on every PR since this afternoon, on 
`jira-source-route-test`. It first fails with `Validation failed: Query param 
'expand' is missing`, and then on the JQL. Main last passed at 14:13 UTC. The 
PRs built after that picked up a new Camel 4.24.0-SNAPSHOT.
   
   ### The cause
   CAMEL-27084 (apache/camel#30311) changed what the `newIssues` consumer of 
camel-jira does at startup:
   1. It now asks for the user's time zone (`/rest/api/latest/myself`) *before* 
the search for the latest issue. The test expected the search first.
   2. A failed search for the latest issue is no longer treated as "there is no 
issue".
      - The test answered that search with an issue that has no fields, which 
camel-jira cannot read.
      - Before, that error was swallowed, and the first poll ran the plain JQL.
      - Now it counts as a failed lookup, and the poll asks for the issues 
created since the start (`created > "…" AND …`).
   
   ### The change
   Only the test changes, in `jira/jira-source-route.citrus.it.yaml`:
   - It expects `/myself` first.
   - It answers the startup search with no issue (`"total": 0, "issues": []`). 
That is the situation the test meant: nothing exists at startup, so the first 
poll runs the plain JQL and routes the issue it returns.
   
   ### Verification
   `./mvnw clean verify -pl :camel-kamelets-itest -Denable.integration.tests 
-Dit.test=JiraIT` passes locally against the current Camel 4.24.0-SNAPSHOT: 3 
tests, 0 failures. With only the first part, the order of the requests, it 
still fails on the JQL of the poll.
   
   The open PRs #3204–#3209 fail on this test alone. They pass once this is 
merged and they are rebased.
   
   _Claude Code on behalf of Claus Ibsen_
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to