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

1.13.x blue merge #1689

Merged
merged 13 commits into from
Sep 6, 2023
Merged

Conversation

rgdoliveira
Copy link
Contributor

Many thanks for submitting your Pull Request ❤️!

Please make sure your PR meets the following requirements:

  • You have read the contributors guide
  • Pull Request title is properly formatted: [KOGITO|RHPAM-XYZ] Subject
  • Pull Request contains link to the JIRA issue
  • Pull Request contains description of the issue
  • Pull Request does not include fixes for issues other than the main ticket
  • Your feature/bug fix has a testcase that verifies it
  • You've tested the new feature/bug fix in an actual OpenShift cluster
  • You've added a RELEASE_NOTES.md entry regarding this change
How to retest this PR or trigger a specific build:
  • (Re)run Jenkins tests
    Please add comment: Jenkins [test|retest] this

  • Prod tests
    Please add comment: Jenkins (re)run [prod|Prod|PROD]

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.

github-actions bot and others added 13 commits April 28, 2023 10:12
) (apache#1499)

* Separate Maven behave tests for community and prod

* correct CI

* correction

* corrected some tests

* Fix failing native s2i build

* Revert "corrected some tests"

This reverts commit d1caf5f.

* correction

* added backporting GHA

Co-authored-by: Tristan Radisson <[email protected]>
…ies (apache#1502) (apache#1505)

* RHPAM-4680 maven rpm module should include Red Hat repositories

* correct after review

Co-authored-by: Tristan Radisson <[email protected]>
* [1.13.x] Setup prod CI (apache#1498)

* Setup prod CI

* updated makefile

* updated cekit validator

* corrected makefile

* update

* correction

* update

* correction

* correction

* Update Jenkinsfile

---------

Co-authored-by: Tristan Radisson <[email protected]>
…mage to enable lice… (apache#1520)

* [RHPAM-4560] - Adjust rhpam-kogito-builder-rhel8 image to enable license compliance via publication of source containers

Signed-off-by: Spolti <[email protected]>

* Update tests/features/bamoe-kogito-builder-jvm.feature

* Update tests/features/bamoe-kogito-builder-jvm.feature

---------

Signed-off-by: Spolti <[email protected]>
Co-authored-by: Tristan Radisson <[email protected]>
* CI: Fix env variables missing

* corrections

Co-authored-by: Tristan Radisson <[email protected]>
…pache#1645)

* [KOGITO-9633] - tzdb.dat (No such file or directory)



* Apply suggestions from code review

---------

Signed-off-by: Spolti <[email protected]>
Co-authored-by: Filippe Spolti <[email protected]>
Co-authored-by: Tristan Radisson <[email protected]>
…-builder image (apache#1648)

* [KOGITO-9465] - Fix behave test for the kogito-s2i-builder image (apache#1610)

* [KOGITO-9465] - Fix behave test for the kogito-s2i-builder image

Signed-off-by: Spolti <[email protected]>

* test config

* try 2 builds in one scenario

* update

* correction

* Update tests/features/kogito-common-builder-jvm.feature

* Revert "test config"

This reverts commit 79eff86.

* Update feature files

* Update tests/features/kogito-s2i-builder-native.feature

* Update tests/test-apps/clone-repo.sh

* review

Signed-off-by: Spolti <[email protected]>

---------

Signed-off-by: Spolti <[email protected]>
Co-authored-by: radtriste <[email protected]>
Co-authored-by: Tristan Radisson <[email protected]>

* Update Makefile

---------

Signed-off-by: Spolti <[email protected]>
Co-authored-by: Filippe Spolti <[email protected]>
Co-authored-by: radtriste <[email protected]>
Co-authored-by: Tristan Radisson <[email protected]>
@kie-ci1
Copy link

kie-ci1 commented Sep 6, 2023

@spolti
Copy link
Member

spolti commented Sep 6, 2023

@rgdoliveira this is a example of manual merge needed, do you to try yourself or should I merge it?

@rgdoliveira rgdoliveira merged commit 36be4ae into apache:1.13.x-blue Sep 6, 2023
4 checks passed
@rgdoliveira
Copy link
Contributor Author

@spolti I just did it following the suggested commands, please double-check if it is correct. thanks!

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.

5 participants