This repository has been archived by the owner on Aug 2, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 35
Get aggregate code coverage, add coverage upload in test workflow and add badges in README #87
Closed
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
Update code of conduct link
* Support ES7.0, use primary_term and seq_no for job doc versioning
* support scheduledJob with locks. * Use ClusterService instead of Client to check the index exists. address some minor comment. * Updated through the comment. 1. Move the LockService in the SPI package 1. Added deleteLock to test. 1. Updated naming from job_type to job_index_name 1. updated delete lock to be safe with non existing index name. * Use ClusterStateService for lockIndexExist * Update acquireLock to take JobParam and JobContext * add some documentation to LockService
* Update release-note for OpenDistro 1.0.0 release * Add Debian package build * Update Rpm build
* Filter clusterChangedEvent when doing sweeping * Format code
* Update release lock log level * Update sweeper version compare log level
* update ScheduledJobParser to use the JobDocVersion
* support ES 7.1.1 and upgrade to Opendistro 1.1
* Add spi subproject maven publish task
* Support Elasticsearch 7.2
* Support ES version 7.4.2 * change LockServiceIT timing * give unique table name and job id for each test * upload artifacts if failed * include spi build upload artifacts
* Updates release notes * Changes runs-on to Mac for github workflow
* add jitter in job parameters * add jitter limit * set default jitter limit as 0.6; add more comments
* Create push-jdbc-jar.yml * Update and rename push-jdbc-jar.yml to push-job-sched-jar.yml * Update push-job-sched-jar.yml * Update push-job-sched-jar.yml * Update push-job-sched-jar.yml
… interface in Elasticsearch 7.9.0 (#67) * Support Elasticsearch 7.9.0 * Update the release note for 1.10.0.0 to satisfy the unified format
…e notes (#68) * Add a config file to organize all labeled PRs and place under headers in the release notes * Add a workflow to create draft release notes under ‘Releases’ tab in GitHub * Reformat old release notes to meet the unified standard
* Making Schedule interface Writeable and relevant changes for CronScheduler and IntervalScheduler classes. - This is needed for converting Anomaly Detection API's to integrate with RestActions. * Removing intervalInMillis from Transport * Adding Unit Tests for Cron and Interval Schedules
* Add a function to renew lock in LockService class and add integration test for it * return the renewed lock instead of a boolean value when calling 'renewLock()'
* Bump plugin version and update release notes
* Support Elasticsearch 7.10 * Fix link for release notes
* Rename plugin artifacts for more consistent naming convention
* Support Elasticsearch 7.10.2 * Update release notes
* Change release workflow to use new staging bucket for artifacts
Codecov Report
@@ Coverage Diff @@
## master #87 +/- ##
=========================================
Coverage ? 43.93%
Complexity ? 118
=========================================
Files ? 15
Lines ? 858
Branches ? 89
=========================================
Hits ? 377
Misses ? 454
Partials ? 27 Continue to review full report at Codecov.
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Issue #, if available:
Description of changes:
alerting
repo: https://github.com/opendistro-for-elasticsearch/alerting/blob/master/build-tools/merged-coverage.gradleThis PR carries the code coverage visualization that already in
index-management
and ‘alerting’ repo tojob-scheduler
opendistro-for-elasticsearch/index-management#230
opendistro-for-elasticsearch/index-management#231
opendistro-for-elasticsearch/index-management#232
opendistro-for-elasticsearch/index-management#251
opendistro-for-elasticsearch/alerting#223
opendistro-for-elasticsearch/alerting#231
Concern: I think we should discuss which class is needed to do the code coverage analysis, and which don't.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.