-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
fix(ci): use the right param type #26469
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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
mdelapenya
added
the
Team:Automation
Label for the Observability productivity team
label
Jun 24, 2021
botelastic
bot
added
needs_team
Indicates that the issue/PR needs a Team:* label
and removed
needs_team
Indicates that the issue/PR needs a Team:* label
labels
Jun 24, 2021
mdelapenya
added
backport-v7.13.0
Automated backport with mergify
backport-v7.14.0
Automated backport with mergify
labels
Jun 24, 2021
mdelapenya
changed the title
fix: use the right param type
fix(ci): use the right param type
Jun 24, 2021
v1v
approved these changes
Jun 24, 2021
urso
approved these changes
Jun 24, 2021
💚 Build Succeeded
Expand to view the summary
Build stats
Trends 🧪❕ Flaky test reportNo test was executed to be analysed. |
mergify bot
pushed a commit
that referenced
this pull request
Jun 24, 2021
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 bot
pushed a commit
that referenced
this pull request
Jun 24, 2021
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
mdelapenya
added a commit
to mdelapenya/beats
that referenced
this pull request
Jun 28, 2021
* master: (32 commits) [Metricbeat] Change Account ID to Project ID in `gcp.billing` module (elastic#26412) update libbeat fields.ecs.yml file and ecsVersion to 1.10.0 (elastic#26121) [Filebeat] Update AWS ELB ingest pipeline (elastic#26441) [FIlebeat] add strict_date_optional_time_nanos date format to PanOS module (elastic#26158) Fix the irregular and typo on prometheus module. (elastic#25726) [Filebeat] Parse additonal debug data fields for Okta module (elastic#25818) fix: update MSSQL Server linux image's Docker registry (elastic#26440) Update indexing.go godocs (elastic#26408) Do not close filestream harvester if an unexpected error is returned when close.on_state_change.* is enabled (elastic#26411) Add support for copytruncate method when rotating input logs with an external tool in `filestream` input (elastic#23457) Allow fields with ip_range datatype (elastic#26444) Add Anomali ThreatStream support to threatintel module (elastic#26350) fix: use the right param type (elastic#26469) [Automation] Update elastic stack version to 8.0.0-7640093f for testing (elastic#26460) Set SM Filebeat modules as GA (elastic#26226) Fix rfc5464 date parsing in the syslog input (elastic#26419) Add linked account information into billing metricset (elastic#26285) [Filebeat] Update HA Proxy log grok patterns (elastic#25835) disable metricbeat logstash test_node_stats (elastic#26436) chore: pass BEAT_VERSION when running E2E tests (elastic#26291) ...
v1v
added a commit
that referenced
this pull request
Jul 14, 2021
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 Co-authored-by: Manuel de la Peña <mdelapenya@gmail.com> Co-authored-by: Victor Martinez <victormartinezrubio@gmail.com>
v1v
added a commit
that referenced
this pull request
Jul 14, 2021
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 Co-authored-by: Manuel de la Peña <mdelapenya@gmail.com> Co-authored-by: Victor Martinez <victormartinezrubio@gmail.com>
@Mergifyio backport 7.14 |
mergify bot
pushed a commit
that referenced
this pull request
Jul 14, 2021
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
Command
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
backport-v7.13.0
Automated backport with mergify
backport-v7.14.0
Automated backport with mergify
Team:Automation
Label for the Observability productivity team
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
It uses the right param type (string instead of boolean) when triggering the e2e job after a wrong copy&paste.
Why is it important?
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.
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Related issues