Remove CI gem dependency

.gitlab-ci.yml

@@ -85,7 +85,7 @@ promote-image:
   script:
     # This would install all dependencies
     - .gitlab/prepare_pkg_directory.sh
-    - ruby pkg/install_ddtrace_deps.rb debase-ruby_core_source libdatadog libddwaf datadog-ci msgpack ffi ddtrace
+    - ruby pkg/install_ddtrace_deps.rb debase-ruby_core_source libdatadog libddwaf msgpack ffi ddtrace
   artifacts:
     paths:
       - pkg

ddtrace.gemspec

@@ -68,8 +68,5 @@ Gem::Specification.new do |spec|
   # When updating the version here, please also update the version in `native_extension_helpers.rb` (and yes we have a test for it)
   spec.add_dependency 'libdatadog', '~> 5.0.0.1.0'
 
-  # used for CI visibility product until the next major version
-  spec.add_dependency 'datadog-ci', '~> 0.5.0'
-
   spec.extensions = ['ext/ddtrace_profiling_native_extension/extconf.rb', 'ext/ddtrace_profiling_loader/extconf.rb']
 end

docs/Compatibility.md

@@ -108,14 +108,6 @@ For a list of available integrations, and their configuration options, refer to
 | Stripe                     | `stripe`                   | `>= 5.15.0`              | `>= 5.15.0`               | [Link][47]                          | [Link](https://github.com/stripe/stripe-ruby)                                |
 | Sucker Punch               | `sucker_punch`             | `>= 2.0`                 | `>= 2.0`                  | [Link][48]                          | [Link](https://github.com/brandonhilkert/sucker_punch)                       |
 
-### CI visibility integrations
-
-These are the available CI visibility integrations:
-
-| Name      | Key        | Versions Supported: MRI | Versions Supported: JRuby | How to configure    | Gem source                                          |
-|-----------|------------|-------------------------|---------------------------|---------------------|-----------------------------------------------------|
-| Cucumber  | `cucumber` | `>= 3.0`                | `>= 1.7.16`               | [Link][49]          | [Link](https://github.com/cucumber/cucumber-ruby)   |
-| RSpec     | `rspec`    | `>= 3.0.0`              | `>= 3.0.0`                | [Link][50]          | [Link](https://github.com/rspec/rspec)              |
 
 [1]: https://github.com/DataDog/dd-trace-rb
 [2]: https://docs.datadoghq.com/tracing/trace_collection/dd_libraries/ruby#action-cable
@@ -165,6 +157,4 @@ These are the available CI visibility integrations:
 [46]: https://docs.datadoghq.com/tracing/trace_collection/dd_libraries/ruby#sneakers
 [47]: https://docs.datadoghq.com/tracing/trace_collection/dd_libraries/ruby#stripe
 [48]: https://docs.datadoghq.com/tracing/trace_collection/dd_libraries/ruby#sucker-punch
-[49]: https://docs.datadoghq.com/tracing/trace_collection/dd_libraries/ruby#cucumber
-[50]: https://docs.datadoghq.com/tracing/trace_collection/dd_libraries/ruby#rspec
 

docs/GettingStarted.md

@@ -333,18 +333,7 @@ For a list of configuration options for the available integrations, refer to the
 
 #### CI Visibility
 
-For Datadog CI Visibility, library instrumentation can be activated and configured by using the following `Datadog.configure` API:
-
-```ruby
-Datadog.configure do |c|
-  # Activates and configures an integration
-  c.ci.instrument :integration_name, **options
-end
-```
-
-`options` are keyword arguments for integration-specific configuration.
-
-For a list of available integrations and their supported versions, see [Ruby CI Integration Compatibility][3]
+Checkout [Datadog's Ruby Library for instrumenting your test and continuous integration pipeline](https://github.com/DataDog/datadog-ci-rb)
 
 ### Action Cable
 
@@ -602,41 +591,6 @@ Datadog::Tracing.trace('outer') do
 end
 ```
 
-### Cucumber
-
-Cucumber integration will trace all executions of scenarios and steps when using `cucumber` framework.
-
-To activate your integration, use the `Datadog.configure` method:
-
-```ruby
-require 'cucumber'
-require 'ddtrace'
-
-# Configure default Cucumber integration
-Datadog.configure do |c|
-  c.ci.instrument :cucumber, **options
-end
-
-# Example of how to attach tags from scenario to active span
-Around do |scenario, block|
-  active_span = Datadog.configuration[:cucumber][:tracer].active_span
-  unless active_span.nil?
-    scenario.tags.filter { |tag| tag.include? ':' }.each do |tag|
-      active_span.set_tag(*tag.name.split(':', 2))
-    end
-  end
-  block.call
-end
-```
-
-`options` are the following keyword arguments:
-
-| Key | Description | Default |
-| --- | ----------- | ------- |
-| `enabled` | Defines whether Cucumber tests should be traced. Useful for temporarily disabling tracing. `true` or `false` | `true` |
-| `service_name` | Service name used for `cucumber` instrumentation. | `'cucumber'` |
-| `operation_name` | Operation name used for `cucumber` instrumentation. Useful if you want rename automatic trace metrics e.g. `trace.#{operation_name}.errors`. | `'cucumber.test'` |
-
 ### Dalli
 
 Dalli integration will trace all calls to your `memcached` server:
@@ -1112,30 +1066,6 @@ Datadog.configure do |c|
 end
 ```
 
-### Minitest
-
-The Minitest integration will trace all executions of tests when using `minitest` test framework.
-
-To activate your integration, use the `Datadog.configure` method:
-
-```ruby
-require 'minitest'
-require 'ddtrace'
-
-# Configure default Minitest integration
-Datadog.configure do |c|
-  c.ci.instrument :minitest, **options
-end
-```
-
-`options` are the following keyword arguments:
-
-| Key | Description | Default |
-| --- | ----------- | ------- |
-| `enabled` | Defines whether Minitest tests should be traced. Useful for temporarily disabling tracing. `true` or `false` | `true` |
-| `service_name` | Service name used for `minitest` instrumentation. | `'minitest'` |
-| `operation_name` | Operation name used for `minitest` instrumentation. Useful if you want rename automatic trace metrics e.g. `trace.#{operation_name}.errors`. | `'minitest.test'` |
-
 ### MongoDB
 
 The integration traces any `Command` that is sent from the [MongoDB Ruby Driver](https://github.com/mongodb/mongo-ruby-driver) to a MongoDB cluster. By extension, Object Document Mappers (ODM) such as Mongoid are automatically instrumented if they use the official Ruby driver. To activate the integration, simply:
@@ -1795,30 +1725,6 @@ end
 | --- | ----------- | ------- |
 | `service_name` | Service name for `roda` instrumentation. | `'nil'` |
 
-### RSpec
-
-RSpec integration will trace all executions of example groups and examples when using `rspec` test framework.
-
-To activate your integration, use the `Datadog.configure` method:
-
-```ruby
-require 'rspec'
-require 'ddtrace'
-
-# Configure default RSpec integration
-Datadog.configure do |c|
-  c.ci.instrument :rspec, **options
-end
-```
-
-`options` are the following keyword arguments:
-
-| Key | Description | Default |
-| --- | ----------- | ------- |
-| `enabled` | Defines whether RSpec tests should be traced. Useful for temporarily disabling tracing. `true` or `false` | `true` |
-| `service_name` | Service name used for `rspec` instrumentation. | `'rspec'` |
-| `operation_name` | Operation name used for `rspec` instrumentation. Useful if you want rename automatic trace metrics e.g. `trace.#{operation_name}.errors`. | `'rspec.example'` |
-
 ### Sequel
 
 The Sequel integration traces queries made to your database.
@@ -2789,4 +2695,3 @@ See [this issue](https://github.com/DataDog/dd-trace-rb/issues/3015) for a discu
 [header tags]: https://docs.datadoghq.com/tracing/configure_data_security/#applying-header-tags-to-root-spans
 [1]: https://docs.datadoghq.com/tracing/trace_collection/compatibility/ruby/
 [2]: https://docs.datadoghq.com/tracing/trace_collection/compatibility/ruby#integrations
-[3]: https://docs.datadoghq.com/tracing/trace_collection/compatibility/ruby#ci-visibility-integrations