We have collection of more than 1 Million open source products ranging from Enterprise product to
small libraries in all platforms. We aggregate information from all open source repositories.
Search and find the best for your needs. Check out projects section.
MassTransit is a lightweight message bus for creating distributed applications using the .NET framework. MassTransit provides an extensive set of features on top existing message transports, resulting in a developer friendly way to asynchronously connect services using message-based conversation patterns. Message-based communication is a reliable and scalable way to implement a service oriented architecture.
Run one simple command to install and use the interactive project generator. You'll need Node v8.9 (the current LTS release) or later. The interactive CLI will help you create and configure your project automatically.
Python wheels are great. Building them across Mac, Linux, Windows, on multiple versions of Python, is not. cibuildwheel is here to help. cibuildwheel runs on your CI server - currently it supports GitHub Actions, Azure Pipelines, Travis CI, AppVeyor, CircleCI, and GitLab CI - and it builds and tests your wheels across all of your platforms.
Bors-NG implements a continuous-testing workflow where the master branch never breaks. It integrates GitHub pull requests with a tool like Travis CI that runs your tests. Change the name of this function, as well as every call site that currently exists in master. I've thought of making it a method on Crab instead of on Sword, but then it would be bifurcateWithSword(), which hardly seems like an improvement.
Set the APM_TEST_PACKAGES environment variable in your .travis.yml or circle.yml file to a space-separated list of packages to install before your package's tests run.It will always download the latest available version. You can read more about the latest Atom release here.
This is a unittest framework for Sublime Text 3. It runs unittest testcases on local machines and CI services such as Travis CI, Circle CI and Appveyor. It also supports testing syntax_test files for the new sublime-syntax format. UnitTesting can be triggered via the command palette command UnitTesting. Enter the package name in the input panel and hit enter, a console should pop up and the tests should be running. To run only tests in particular files, enter <Package name>:<filename>. <filename> should be a unix shell wildcard to match the file names, <Package name>:test*.py is used in default.
Bring your stream to life with more modern effects! Stream Effects adds several much needed features to OBS Studio, such as real time Blur and 3D Transform. Now you can blur out sources you think may be questionable, add sick 3D effects or recreate the Heroes of the Storm displacement overlay with the Displacement filter. Building the project is fairly easy and relies on CMake to ease the process.
Return CI job number to run huge tests only on first job. Often we test different Node.js versions on Travis CI. But Node.js version doesn’t affect on many tests. For example, using external API for docs spelling check.
Fast spelling check for Travis CI and AppVeyor. It is just simple wrap for yaspeller, CLI for Yandex.Speller API. But it run spelling check only in first CI job, to speed up build time and reduce unnecessary burden for CI service and Yandex.Speller API.
Console application which brings appveyor.yml to the center of your build process by making possible to execute its build jobs, locally. LocalAppVeyor tries to strictly follow same build pipeline as AppVeyor CI itself.
Use cwd to specify the working directory from which the process is spawned. If not given, the default is to inherit the current working directory. Use env to specify environment variables that will be visible to the new process, the default is process.env.
Simple PHP library to detect in what continuous integration server is current script being run and to provide unified interface for accessing the build properties. The detection is based on environment variables injected to the build environment by each of continuous integration server. However, these variables are named differently in each CI. This library contains adapter for each supported CI server which handles these differences so you don't have to and you can make your scripts (and especially CLI tools) portable for multiple build environments.
This is a solution for continuous integration for R projects on Windows, using AppVeyor -- a CI testing service similar to Travis-CI. Under the hood, r-travis is used to perform the testing; this works even on Windows thanks to MinGW and MSYS. The travis-tool used in appveyor.yml is a modified copy of the r-travis project, documentation is available on its wiki.
Community-supported framework for testing Smalltalk projects on Linux, OS X, and Windows with built-in support for Travis CI, AppVeyor, and GitLab CI/CD. It is inspired by builderCI and aims to provide a uniform and easy way to load and test Smalltalk projects.
The goal of tic is to facilitate testing and deployment tasks for R projects in Travis CI, AppVeyor, or the CI tool of your choice. It comes with pre-defined templates for various R projects (package, bookdown, blogdown, etc.) and provides CI-agnostic workflow definitions (for the CI stages).
This is a quick and dirty PowerShell module with a variety of helper functions for PowerShell CI/CD scenarios. Many of our build scripts explicitly reference build-system-specific features. We might rely on $ENV:APPVEYOR_REPO_BRANCH to know which branch we're in, for example.
Parses webhooks and forwards them in the proper format to Discord. If you want support for a new provider, just create a pull request and add it! Alternatively, a new provider can also be requested by creating an issue.