Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Kogito 9691 test 2 #2

Merged
merged 700 commits into from
Oct 3, 2023
Merged

Kogito 9691 test 2 #2

merged 700 commits into from
Oct 3, 2023

Conversation

MarianMacik
Copy link
Owner

Description of the change:

Motivation for the change:

Checklist

  • Add or Modify a unit test for your change
  • Have you verified that tall the tests are passing?
How to backport a pull request to a different branch?

In order to automatically create a backporting pull request please add one or more labels having the following format backport-<branch-name>, where <branch-name> is the name of the branch where the pull request must be backported to (e.g., backport-7.67.x to backport the original PR to the 7.67.x branch).

NOTE: backporting is an action aiming to move a change (usually a commit) from a branch (usually the main one) to another one, which is generally referring to a still maintained release branch. Keeping it simple: it is about to move a specific change or a set of them from one branch to another.

Once the original pull request is successfully merged, the automated action will create one backporting pull request per each label (with the previous format) that has been added.

If something goes wrong, the author will be notified and at this point a manual backporting is needed.

NOTE: this automated backporting is triggered whenever a pull request on main branch is labeled or closed, but both conditions must be satisfied to get the new PR created.

vaibhavjainwiz and others added 30 commits March 26, 2021 11:25
…… (#809)

* [KOGITO-4731] - Conditions should reflect latest evaluated status - Review comments

* Gix Lint issue

* Remove failed condition when service recovered from failure

* Set failed condition to false when reconcilation recovered from failure
* [KOGITO-3105] - Missing status for failures for KogitoRuntime CRs

* Set reconcilation time to 1min

Co-authored-by: Vaibhav <[email protected]>
* KOGITO-4858 Automatic build of examples

* update

* Moved to pkg

* lint correction

* update

* small update on examples images deploy
* KOGITO-4858 Automatic build of examples

* update

* Moved to pkg

* lint correction

* update

* small update on examples images deploy
* [KOGITO-5005] - Operator print irrelevant metadata in logs

* Fix Kustomize version and release note
* [KOGITO-5005] - Operator print irrelevant metadata in logs

* Fix Kustomize version and release note
* fix explainability dto

* add space
…s (#868)

* [KOGITO-5104] - RHPAM Kogito operator creates wrong default image tags

* fix failing olm test
…s (#868)

* [KOGITO-5104] - RHPAM Kogito operator creates wrong default image tags

* fix failing olm test
…s (#868)

* [KOGITO-5104] - RHPAM Kogito operator creates wrong default image tags

* fix failing olm test
radtriste and others added 26 commits March 31, 2023 09:30
@MarianMacik MarianMacik changed the base branch from main to main-test-PR October 3, 2023 20:10
@MarianMacik MarianMacik changed the base branch from main-test-PR to main October 3, 2023 20:10
@MarianMacik MarianMacik changed the base branch from main to main-test-PR October 3, 2023 20:11
@MarianMacik MarianMacik merged commit c411d34 into main-test-PR Oct 3, 2023
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.