Paul Richardson comments

Results 50 comments of


                                            Paul Richardson

Upgrade can result in integration being rebuilt using the old integrationkit

I think this has now been resolved.

Minor updates for bundle generation

Tests failing due to e2e compilation error fixed in #3527.

Minor updates for bundle generation

Tests a lot more successful now.

Add E2E workflow using Windows runner for testing Camel K CLI client and local run

Happy to take this on.

Add E2E workflow using Windows runner for testing Camel K CLI client and local run

`kind` cannot be installed on Window runners at the moment. see https://github.com/actions/runner-images/issues/5760 and https://github.com/microsoft/WSL/issues/6301

Add E2E workflow using Windows runner for testing Camel K CLI client and local run

> One idea might be just run workflows that don't require a Kind cluster, such as `build` and `local-it` for the time being. Yes. The `build` workflow is successful but...

Add E2E workflow using Windows runner for testing Camel K CLI client and local run

https://github.com/apache/camel-k/pull/3823 allows for running the build workflow. Does need to be switched on.

Log a warn message once the component used has not a quarkus extension

@squakez No. I don't believe it is. I think this refers to adding more logging messages whereas #3149 seeks to grab the quarkus logging if the command immediately [fails](https://github.com/apache/camel-k/blob/main/pkg/util/command.go#L41).

`make build-resources` does not work on Windows

Fixing this issue while looking into #3364

`make build-resources` does not work on Windows

https://github.com/apache/camel-k/pull/3823