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

[7.x](backport #26469) fix(ci): use the right param type #26470

Merged
merged 2 commits into from
Jul 14, 2021

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Jun 24, 2021

This is an automatic backport of pull request #26469 done by Mergify.
Cherry-pick of f429a82 has failed:

On branch mergify/bp/7.x/pr-26469
Your branch is up to date with 'origin/7.x'.

You are currently cherry-picking commit f429a82b9.
  (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)

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

no changes added to commit (use "git add" and/or "git commit -a")

To fix up this pull request, you can check it out locally. See documentation: https://help.github.com/articles/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.io/

Jenkins, as expected, is honouring the param type used in the caller, but
not honouring the type in the triggered pipeline. This issue has historical
rationale, as the parameters are created dynamically

(cherry picked from commit f429a82)

# Conflicts:
#	.ci/packaging.groovy
@mergify mergify bot added backport conflicts There is a conflict in the backported pull request labels Jun 24, 2021
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Jun 24, 2021
@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview

Expand to view the summary

Build stats

  • Build Cause: Pull request #26470 opened

  • Start Time: 2021-06-24T12:36:42.544+0000

  • Duration: 14 min 34 sec

  • Commit: 8e52df1

Trends 🧪

Image of Build Times

❕ Flaky test report

No test was executed to be analysed.

@v1v v1v added automation Team:Automation Label for the Observability productivity team and removed conflicts There is a conflict in the backported pull request labels Jul 14, 2021
@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Jul 14, 2021
@v1v v1v merged commit ca703d2 into 7.x Jul 14, 2021
@mergify mergify bot deleted the mergify/bp/7.x/pr-26469 branch July 14, 2021 15:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automation backport Team:Automation Label for the Observability productivity team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants