feat: enable generic Pipeline #4384
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Step required to prepare Camel K to manage a generic pipeline Ref apache#4281
claudio4j
reviewed
May 17, 2023
* Added a condition for each container execution during build (either success or failure) * Added E2E test to cover such feature
It turns out, we did not need a big refactoring.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Enable the possibility to run a generic Pipeline instead of a "static" build. Detailed information how to use the new feature in the same PR documentation: https://github.com/apache/camel-k/blob/096d6ec53a1af13e02de8ca5c9d22422d3f482fd/docs/modules/ROOT/pages/pipeline/pipeline.adoc
4c493a4: enable the execution of any task, running an
initContainerafter the builder with the configuration provided by the user (viabuildertrait).9e104b3: added conditions to Build with the result of each container execution. As side effect we now have also the result (success or failure) of builder and publisher task (enhancing ux a lot).
Ref #4281
Release Note