[7.17](backport #1439) ci: use downstream pattern

[mergify]

This is an automatic backport of pull request #1439 done by Mergify.
Cherry-pick of 9b2c061 has failed:

On branch mergify/bp/7.17/pr-1439
Your branch is up to date with 'origin/7.17'.

You are currently cherry-picking commit 9b2c061.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   .ci/packaging.groovy

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   .ci/Jenkinsfile

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

---

Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

• @Mergifyio refresh will re-evaluate the rules
• @Mergifyio rebase will rebase this PR on its base branch
• @Mergifyio update will merge the base branch into this PR
• @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

• look at your merge queues
• generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

[v1v]

Lets wait for backporting #756

[v1v]

@Mergifyio rebase

[mergify]

rebase

❌ Base branch update has failed

Git reported the following error:

Rebasing (1/1)
error: could not apply 7f9c12f... ci: use downstream pattern (#1439)
Resolve all conflicts manually, mark them as resolved with
"git add/rm <conflicted_files>", then run "git rebase --continue".
You can instead skip this commit: run "git rebase --skip".
To abort and get back to the state before "git rebase", run "git rebase --abort".
Could not apply 7f9c12f... ci: use downstream pattern (#1439)
Auto-merging .ci/Jenkinsfile
CONFLICT (content): Merge conflict in .ci/Jenkinsfile

err-code: 9CC70

[mergify]

This pull request is now in conflicts. Could you fix it @mergify[bot]? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b mergify/bp/7.17/pr-1439 upstream/mergify/bp/7.17/pr-1439
git merge upstream/7.17
git push upstream mergify/bp/7.17/pr-1439

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2022-05-10T16:51:13.567+0000

• Duration: 9 min 33 sec

Test stats 🧪

Test	Results
Failed	0
Passed	236
Skipped	0
Total	236

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

[v1v]

Requires #1450

[mergify]

This pull request is now in conflicts. Could you fix it @mergify[bot]? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b mergify/bp/7.17/pr-1439 upstream/mergify/bp/7.17/pr-1439
git merge upstream/7.17
git push upstream mergify/bp/7.17/pr-1439

[v1v]

Requires #1451