rubygems / gem-testers

Tests run everywhere collected here.

RubyGems

RubyGems is a package management framework for Ruby.

A package (also known as a library) contains a set of functionality that can be invoked by a Ruby program, such as reading and parsing an XML file. We call these packages "gems" and RubyGems is a tool to install, create, manage and load these packages in your Ruby environment.

RubyGems is also a client for RubyGems.org, a public repository of Gems that allows you to publish a Gem that can be shared and used by other developers. See our guide on publishing a Gem at guides.rubygems.org

Getting Started

Installing and managing a Gem is done through the gem command. To install a Gem such as Nokogiri which lets you read and parse XML in Ruby:

$ gem install nokogiri

RubyGems will download the Nokogiri Gem from RubyGems.org and install it into your Ruby environment.

Finally, inside your Ruby program, load the Nokogiri gem and start parsing your XML:

require 'nokogiri'

Nokogiri.XML('<h1>Hello World</h1>')

For more information about how to use RubyGems, see our RubyGems basics guide at guides.rubygems.org

Requirements

• RubyGems supports Ruby 3.0 or later.

Installation

RubyGems is already installed in your Ruby environment, you can check the version you have installed by running gem --version in your terminal emulator.

In some cases Ruby & RubyGems may be provided as OS packages. This is not a recommended way to use Ruby & RubyGems. It's better to use a Ruby Version Manager, such as rbenv or chruby. If you still want to use the version provided by your OS package manager, please also use your OS package manager to upgrade rubygems, and disregard any other installation instructions given below.

If you would like to manually install RubyGems:

• Download from https://rubygems.org/pages/download, unpack, and cd into RubyGems' src
• OR clone this repository and cd into the repository

Install RubyGems by running:

$ ruby setup.rb

For more details and other options, see:

$ ruby setup.rb --help

Upgrading RubyGems

To upgrade to the latest RubyGems, run:

$ gem update --system

See UPGRADING for more details and alternative instructions.

Release policy

RubyGems and Bundler are released in sync, although they do not share their major version number. It is planned that also their major version numbers will be sync'ed in the future.

The release policy is somewhat similar to the release policy of Ruby itself:

• Frequent patch releases (every 2-4 weeks) including bug fixes, minor enhancements, small features, or even medium sized features declared as experimental for battle testing.
• Yearly minor releases including bigger features, and minor breaking changes (affecting only edge cases and a very small set of users).
• Occasional major releases (replacing yearly minors) including major breaking changes.

Documentation

RubyGems uses rdoc for documentation. A compiled set of the docs can be viewed online at rubydoc.

RubyGems also provides a comprehensive set of guides which covers numerous topics such as creating a new gem, security practices and other resources at https://guides.rubygems.org

Getting Help

Filing Tickets

Got a bug and you're not sure? You're sure you have a bug, but don't know what to do next? In any case, let us know about it! The best place for letting the RubyGems team know about bugs or problems you're having is on the RubyGems issues page at GitHub.

Bundler Compatibility

See https://bundler.io/compatibility for known issues.

Supporting

RubyGems is managed by Ruby Central, a non-profit organization that supports the Ruby community through projects like this one, as well as RubyConf, RailsConf, and RubyGems.org. You can support Ruby Central by attending or sponsoring a conference, or by joining as a supporting member.

Contributing

If you'd like to contribute to RubyGems, that's awesome, and we <3 you. Check out our guide to contributing for more information.

Code of Conduct

Everyone interacting in the RubyGems project’s codebases, issue trackers, chat rooms, and mailing lists is expected to follow the contributor code of conduct.

gem-testers's Issues

Header enhancements

• Logo
• Search bar

original: https://github.com/bluepojo/gem-testers/issues#issue/3

wrap test result output

http://gem-testers.org/gems/rubygems-update/v/1.5.0/test_results/127 is particularly bad, but there are others.

this should just be a CSS change and I can do it later tonight if you don't object josiah.

Home page recent results that require 2 lines break alignment

See screenshot here:

Does the x86_64 arch make sense for the jruby platform?

If I'm looking at jruby, does it matter that it's x86_64? If I'm looking at x86_64, does it matter that I might see jruby reports mixed in with matz's ruby? I don't think anyone thoughtful and reasonable will be confused; it's more a matter of the UI showing irrelevant or less-than-useful info.

Original: https://github.com/bluepojo/gem-testers/issues#issue/13

search by author

I had requested of me a 'search by author' funciton. This would likely require some integration with rubygems.org.

Pretty error pages

Handle 4xx/5xx responses gracefully.

Original: https://github.com/bluepojo/gem-testers/issues#issue/6

[feature] Email notifications.

It might be handy to enable Email notifications of failures, sending them to the email addresses in Gem::Specification.

Handling YAML 1.1 from the clients

JRuby 1.6 outputs YAML 1.1 which is giving our create action in test_results hives.

https://github.com/rubygems/rubygems-test/issues/#issue/30

wrong link to README

The main page links to https://github.com/rubygems/rubygems-test/blob/master/README.rdoc but the correct link would be https://github.com/rubygems/rubygems-test/blob/master/README.txt

Gem testers website needs short description of what service provides

It needs a tagline, just as rubygems.org has 'your community gem host' directly beneath the main logo, gem-testers.org needs one too. Just a short, pithy description of the service, even something like they have on cpan-testers.org "Find gem testers reports for all your rubygems"

better pagination

we should probably leverage the server-side processing features of datatables to present our paginated views:

http://datatables.net/examples/data_sources/server_side.html

this will require some significant restructuring of the rubygems_controller.rb

Original: https://github.com/bluepojo/gem-testers/issues#issue/12

Can't add feed to google reader

http://gem-testers.org/gems/4/feed.xml is the feed. Works fine in Safari with feed://

Deployment

Write capfile

Original: https://github.com/bluepojo/gem-testers/issues#issue/5

show time of submission in test results

I don't think there's really room for this in the grid, but it would be nice to fit the test result submission time in there. Where should it go?

Expanded search functionality

Sorry for the lack of details, but our search sucks and I'd like to improve it.

test_results page should have a raw link

So I may download the logs or easily cut/paste them.

Test null fields

Integration and unit tests

Original: https://github.com/bluepojo/gem-testers/issues#issue/16

pre-release checks

Please see https://github.com/rubygems/rubygems-test/issues/#issue/17

Output text not printed as submitted

Need to honor newlines in text output: (missing <pre> tags)

Better handling of ANSI character codes in output.

The Test Output should either strip ANSI character codes or colourize them. This would be helpful for viewing Test Output which invoke Thor::Actions.

Prerelease versions are sorted to be after release versions

Use Gem::Version to sort versions

[feature] Categorisation of Failures.

Could use basic Regular Expressions to categorize Failures:

• LoadError / Gem Dependencies
• FFI::NotFoundError
• Segfault

JSON responders

Here a summary of the information I need for the bot, as discussed in IRC:

• add total_successes and total_fails fields to each individual
  version reported in the per-gem JSON responders. Those should not be
  affected by the limit on individual reports in the JSON
• provide a global JSON stream with the latest reports (optimally
  always for a specific time frame, e.g. the last hour; maybe capped
  to X reports if the report counts get too high)
  • the global JSON should not only contain the links to the reports,
    but also directly inline the most important information, i.e. gem
    name, version, interpreter/architecture, success/fail. The
    complete output of the test is not needed.

copy log to clipboard feature

Browse page: Alphabetical list of gems

Requested via tweet:

Provide a list of all gems with test results, organized alphabetically for browsing.