compose-ci | based container , listening to github webhooks | Continuous Deployment library

by docteurklein Python Version: Current License: No License

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | compose-ci Summary

compose-ci is a Python library typically used in Devops, Continuous Deployment, Docker applications. compose-ci has no bugs, it has no vulnerabilities, it has build file available and it has low support. You can download it from GitHub.

SaaS CIs are cool and all, but you clearly don't have the same flexibility as this \o/ This also prepares the environment with latest versions of docker and compose, making it a breeze to run your tests. It's self hosted. It can be used wherever docker is running.

Support

Quality

Security

License

Reuse

Support

compose-ci has a low active ecosystem.

It has 22 star(s) with 1 fork(s). There are no watchers for this library.

It had no major release in the last 6 months.

There are 1 open issues and 1 have been closed. On average issues are closed in 353 days. There are 1 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of compose-ci is current.

Quality

compose-ci has 0 bugs and 0 code smells.

Security

compose-ci has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

compose-ci code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

compose-ci does not have a standard license declared.

Check the repository for any license declaration and review the terms closely.

Without a license, all rights are reserved, and you cannot use the library in your applications.

Reuse

compose-ci releases are not available. You will need to build from source code and install.

Build file is available. You can build the component from source.

Installation instructions are not available. Examples and code snippets are available.

compose-ci saves you 170 person hours of effort in developing the same functionality from scratch.

It has 422 lines of code, 37 functions and 14 files.

It has low code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed compose-ci and discovered the below as its top functions. This is intended to give you an instant insight into compose-ci implemented functionality, and help decide if they suit your requirements.

Run the build
Convert to HTML
Send a failed message to the mailer
Post a commit
Create a pending commit
Mark a commit as failed
Reconfigure all services
Pull images
Login to project
Return True if the result is successful
Send a POST request
Builds a docker container
Fetch a tarball
Send a email
Execute tests
Handle HTTP POST request
Build Docker container

Get all kandi verified functions for this library.

compose-ci Key Features

No Key Features are available at this moment for compose-ci.

compose-ci Examples and Code Snippets

No Code Snippets are available at this moment for compose-ci.

Community Discussions

Trending Discussions on compose-ci

ASP.NET Core WebApplicationFactory CreateClient Booting Server Blocking on GitLab CI When Run In Docker Compose Environment

QUESTION

ASP.NET Core WebApplicationFactory CreateClient Booting Server Blocking on GitLab CI When Run In Docker Compose Environment

Asked 2020-Nov-19 at 19:16

I have a functional tests project for my ASP.NET Core 3.1 API that uses WebApplicationFactory to create a test server for the API. The tests pass locally and within a local docker-compose environment.

However when run on the GitLab CI server within the same docker-compose environment the WebApplication factory's CreateClient method is blocking. When the test server starts the confluent Kafka Admin Service is blocking, i.e no confirmation log message is displayed confirming the topic created. I have created a small project on GitLab to highlight the issue.

The issue appears to be with the WebApplication test server and Confluent Kafka somehow, since I have created a docker-compose stack that starts the Software Under Test WebApp on GitLab CI and it starts successfully.

The Software Under Test contains Background / Hosted Services:

Kafka Admin Service to create topic - this is blocking on CI server when using WebAppicationFactory test server
Kafka Consumer
MqttKafkaBridge

It also uses Autofac and starts a SignalR Hub.

Has anyone experienced similar issue/problems when using WebApplicationFactory on a remote CI server such as Gitlab or Travis?

Is it because WebApplicationFactory.CreateClient() creates a TestServer that runs as localhost??

Test using WebApplicationFactory

Create a WebApplicationFactory for the Sofware Under Test and display console log message once created. When run on CI Server no console message is displayed for after the factory client has been created.

...

ANSWER

Answered 2020-Nov-19 at 19:16

After reading this aspnetcore issue discovered that the problem was with the implementation of my IHostedService implementation.

The StartAsync method was performing the task, running until the request completed. By design this method is meant to be fire and forget, i.e. start the task and then continue. Updated my KafkaAdmin service to be a BackgroundService, overriding ExecuteAsync method, as listed below. Subsequently, tests no longer blocks.

Source https://stackoverflow.com/questions/64899839

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install compose-ci

You can download it from GitHub.
You can use compose-ci like any standard Python library. You will need to make sure that you have a development environment consisting of a Python distribution including header files, a compiler, pip, and git installed. Make sure that your pip, setuptools, and wheel are up to date. When using pip it is generally recommended to install packages in a virtual environment to avoid changes to the system.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: