You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by "pkalsi97 (via GitHub)" <gi...@apache.org> on 2025/12/13 06:36:12 UTC
[PR] fix: Correct first-readiness metric for dry-build integrations [camel-k]
pkalsi97 opened a new pull request, #6409:
URL: https://github.com/apache/camel-k/pull/6409
Closes #6341
Changes:
- Add `DeploymentTimestamp` field to IntegrationStatus
- Set `DeploymentTimestamp` when transitioning to Deploying phase
- Update `integrationUpdateFunc` to prioritize `DeploymentTimestamp`
- Add unit tests for timestamp selection logic
- Extend E2E test to verify `DeploymentTimestamp` behavior
--
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: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] fix(ctrl): dry build - correct first-readiness metric [camel-k]
Posted by "squakez (via GitHub)" <gi...@apache.org>.
squakez merged PR #6409:
URL: https://github.com/apache/camel-k/pull/6409
--
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: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] fix(ctrl): dry build - correct first-readiness metric [camel-k]
Posted by "squakez (via GitHub)" <gi...@apache.org>.
squakez commented on PR #6409:
URL: https://github.com/apache/camel-k/pull/6409#issuecomment-3650564337
> @squakez I think the test failure is happening because I did not commit the updated CRDs ? am I thinking correctly here ? I am also working on the caCert trait option for trusted root certificates issue. do we have to commit the CRDs that we locally generate ?
Yes. If any change in the crds, `make generate` is required.
--
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: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] fix(ctrl): dry build - correct first-readiness metric [camel-k]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on PR #6409:
URL: https://github.com/apache/camel-k/pull/6409#issuecomment-3649234906
:warning: Unit test coverage report - coverage decreased from 51.6% to 51.5% (**-0.1%**)
--
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: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] fix(ctrl): dry build - correct first-readiness metric [camel-k]
Posted by "pkalsi97 (via GitHub)" <gi...@apache.org>.
pkalsi97 commented on PR #6409:
URL: https://github.com/apache/camel-k/pull/6409#issuecomment-3649332463
@squakez I think the test failure is happening because I did not commit the updated CRDs ? am I thinking correctly here ?
I am also working on the caCert trait option for trusted root certificates issue. do we have to commit the CRDs that we locally generate ?
--
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: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org