What’s the point: OpenAPI-to-GraphQL, TensorRT, Jenkins, GNU Rush

What's the point

In time for its first major release, IBM decided to rename OASGraph to OpenAPI-to-GraphQL. The project is meant to automatically generate GraphQL wrappers for RESTlike APIs and was open sourced last year.

The new name should be a clearer indicator of the project’s function and align with other libraries that follow the “x-to-y naming convention”. Other than that the tool has moved from the StrongLoop organisation to GitHub, making it more accessible and dispelling the notion it would only work with LoopBack.

Nvidia open sources inference library

Nvidia appears to have decided to put its TensorRT library and the plug-ins that go along with it into the open. It is worth noting however, that the C++ library with a focus on deep learning inference on the company’s GPUs is dependent on closed source CUDA. This isn’t really surprising given it has been developed by the same company, but makes one wonder about its stance on open source…at least a tiny bit.

Jenkins plugin handling might get a bit easier

Summer of Code participant Natasha Stopa has given a first progress update on the plugin management library and CLI tool she is working on for the Jenkins project. The goal of her project is to unify plugin management logic across different Jenkins implementations and replace the Docker install-plugins.sh script in the process. This is meant to make downloading plugins and accessing their information easier.


An alpha version of the tool she is working on can now be found on GitHub. Constructive feedback is appreciated, just remember that it’s pretty early stages at this point. In the next couple of weeks Stopa will continue to make input parsing more robust, and add things like support for security warnings and available updates, as well as Docker integration.

Rush reaches 2.0 without hurry

Meanwhile GNU Rush, the restricted user shell registered into the GNU project back in 2008, just saw its second major release. The most important change in v2.0 is the completely rewritten configuration support, which also introduces a new configuration file syntax.

Users afraid of their old installation breaking can breathe easy, as the announcement states that “backward compatibility with prior releases is retained and old configuration syntax is still supported”. Switching to the new version is highly encouraged nevertheless.

- Advertisement -