Move openmetrics module to oss#26561
Conversation
|
Pinging @elastic/integrations (Team:Integrations) |
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
Trends 🧪💚 Flaky test reportTests succeeded. Expand to view the summary
Test stats 🧪
|
|
CI failure seems related. It'd be nice to add a changelog entry for this. |
|
This pull request is now in conflicts. Could you fix it? 🙏 |
Signed-off-by: chrismark <chrismarkou92@gmail.com>
Signed-off-by: chrismark <chrismarkou92@gmail.com>
Signed-off-by: chrismark <chrismarkou92@gmail.com>
Signed-off-by: chrismark <chrismarkou92@gmail.com>
Signed-off-by: chrismark <chrismarkou92@gmail.com>
61f2a65 to
cedb7f7
Compare
Signed-off-by: chrismark <chrismarkou92@gmail.com>
Jenkinsfile
Outdated
| if(!fileExists(module)) { | ||
| module = '' | ||
| } |
There was a problem hiding this comment.
the getCommonModuleInTheChangeSet(String directory) search for a pattern in a directory path, fi the pattern does not exist will return ''. I am not sure of the goal of check a folder with the name of the module exists in the current folder, probably will never exist.
cc @v1v
There was a problem hiding this comment.
Is pattern checked for the current(=new) state or the old one? In this particular case we have removed the openmetrics module completely from x-pack but the tester still understands that it has changes and thus it kicks the tests for it which leads to test's failure later on since the module does not actually exists under x-pack.
There was a problem hiding this comment.
A bit of context:
Unfortunately this is an edge case when moving files between x-pack and oss beats.
elastic/apm-pipeline-library#535 didn't implement a git diff by excluding files that have been deleted/moved.
So somehow it tries to run the module in x-pack when that particular module was moved to the oss.
Therefore, the validation if the module folder exists could be a good workaround.
I am not sure of the goal of check a folder with the name of the module exists in the current folder, probably will never exist.
if the module name exists in the pwd then it should work, unless module is a nested folder somewhere else, if so, it's required to consider that particular case.
There was a problem hiding this comment.
I've just confirmed what Ivan said, and there is something missing in this logic, something like the below snippet might work,
| if(!fileExists(module)) { | |
| module = '' | |
| } | |
| if(!fileExists("${directory}/module/${module}")) { | |
| module = '' | |
| } |
though I don't know if module is always a nester folder under <beat_name_folder> or x-pack/<beat_name_folder>
Actually yes:
Co-authored-by: Victor Martinez <victormartinezrubio@gmail.com>
|
Ah now another flaky test... @v1v @kuisathaverat are you ok with the change on Jenkinsfile? |
jsoriano
left a comment
There was a problem hiding this comment.
Once the changelog entry is added, ship it!
Signed-off-by: chrismark <chrismarkou92@gmail.com>
* master: [MetricBeat] [AWS] Fix aws metric tags with resourcegroupstaggingapi paginator (elastic#26385) (elastic#26443) Move openmetrics module to oss (elastic#26561) Skip flaky test TestFilestreamMetadataUpdatedOnRename (elastic#26609) [filebeat][fortinet] Use default add_locale for fortinet.firewall (elastic#26524) Enroll proxy settings (elastic#26514)
|
Wondering why mergify didn't open the backport PR for this 🤔 |
(cherry picked from commit 92143fe)
@ChrsMark , backports are automated with mergify as long as the
There is some automation to include new versions in the In fact, the PR is open, #26620 so , I'll leave that operation to the release manager in the beats team, either that PR can be merged if possible, or the mergify change to be cherry-picked and push to the master branch. |
|
Thanks @v1v ! |
…stage-failed-within-same-build * upstream/master: (36 commits) Revert "[CI] fight the flakiness with some retry option in the CI only for the Pull Requests (elastic#26617)" (elastic#26704) Packaging: linux/armv7 is not supported (elastic#26706) Cyberarkpas: Link to official docs on how to setup TLS (elastic#26614) Make network_direction, registered_domain and convert processors compatible with ES older than 7.13.0 (elastic#26676) Disable armv7 packaging (elastic#26679) [Heartbeat] use --params flag for synthetics (elastic#26674) Update dependent package to avoid downloading a suspicious file (elastic#26406) [mergify] set title and allow bp in any direction (elastic#26648) Fix memory leak in SQL helper when database is not available (elastic#26607) [CI] fight the flakiness with some retry option in the CI only for the Pull Requests (elastic#26617) [mergify] automate PRs that change the backport rules (elastic#26641) [Metricbeat] Add Airflow module in xpack (elastic#26220) chore: add-backport-next (elastic#26620) [metricbeat] Add state_job metricset (elastic#26479) CI: jenkins labels are less time consuming now (elastic#26613) [MetricBeat] [AWS] Fix aws metric tags with resourcegroupstaggingapi paginator (elastic#26385) (elastic#26443) Move openmetrics module to oss (elastic#26561) Skip flaky test TestFilestreamMetadataUpdatedOnRename (elastic#26609) [filebeat][fortinet] Use default add_locale for fortinet.firewall (elastic#26524) Enroll proxy settings (elastic#26514) ...
What does this PR do?
This PR moves
openmetricsMetricbeat module under oss directory.