Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

A question about the letuce CI project view #1914

Closed
cjs1992-github opened this issue Nov 16, 2021 · 6 comments
Closed

A question about the letuce CI project view #1914

cjs1992-github opened this issue Nov 16, 2021 · 6 comments
Labels
type: task A general task
Milestone

Comments

@cjs1992-github
Copy link

Bug Report

Current Behavior

I'm concerned about the whole lettuce build, so I wanted to look at the lettuce build project and see that lettuce useshttps://www.travis-ci.com/lettuce-io/lettuce-coreaddress to build, but I couldn't find anything after I linked it through the README.md link,The interface reports 404, but I clicked the codecov next to it and found that the link is available, please check whether this is a problem?

Stack trace ![image](https://user-images.githubusercontent.com/74575955/141985746-1c7bcee5-46a3-4f1c-a091-00347d3c79e9.png)

If you go through this link, the 404 interface will appear. I confirm that you have logged in to travis-ci and associate github with travis-ci.
I'm not sure if it's my operation or if the link is really unavailable, please check it out.

@mp911de
Copy link
Collaborator

mp911de commented Nov 16, 2021

Travis CI has switched to a more commercial model with a set of free minutes for OSS projects. We're not using Travis CI anymore as it creates a lot of hassle and we need to clean up the CI descriptors.

@mp911de mp911de added the type: task A general task label Nov 16, 2021
@cjs1992-github
Copy link
Author

Thanks for your attention. Recently, I was compiling lettuce. I found the number and coverage of test cases that I executed using mvn test and directly executed using make test-coverage PROFILE=${PROFILE:-ci}" in .travis.yml.
It's not the same. I think you did the shielding. When I execute the .travis.yml process, I need to install a lot of software and import environment variables. Is there a guide for local compilation?

@mp911de
Copy link
Collaborator

mp911de commented Nov 17, 2021

Yes, there is at https://github.com/lettuce-io/lettuce-core#building.

However, it doesn't say which packages to install because each platform and each linux distro uses different package names.

@cjs1992-github
Copy link
Author

Thanks for your reply, I've compiled it successfully. I found the cause of the problem above, and the "build" connection is now pointed tohttps://www.travis-ci.com/lettuce-io/lettuce-coreIf this address is used, 404 will be reported, but
The previous address should be "https://www.travis-ci.org/github/lettuce-io/lettuce-coreIf you use this address, the connection is available. I see you said you want to clean up the connection, did CI project change the address?

@mp911de
Copy link
Collaborator

mp911de commented Nov 26, 2021

TravisCI switched all OSS projects to paid plans and I have no intentions to pay for TravisCI as the only value is a publicly visible CI. I have a private Jenkins machine running for Lettuce.

Bildschirmfoto 2021-11-26 um 13 48 43

mp911de added a commit that referenced this issue Dec 3, 2021
Removing our TravisCI integration after TravisCI has switched to a commercial-only subscription model making it next to impossible for unfunded open source projects to continue using TravisCI. Limits imposed by TravisCI are exceeded easily and that pushes each project that hits the limits either into a subscription or a temporarily suspended CI state. None is desirable hence we're removing the integration entirely.
mp911de added a commit that referenced this issue Dec 3, 2021
Removing our TravisCI integration after TravisCI has switched to a commercial-only subscription model making it next to impossible for unfunded open source projects to continue using TravisCI. Limits imposed by TravisCI are exceeded easily and that pushes each project that hits the limits either into a subscription or a temporarily suspended CI state. None is desirable hence we're removing the integration entirely.
mp911de added a commit that referenced this issue Dec 3, 2021
Removing our TravisCI integration after TravisCI has switched to a commercial-only subscription model making it next to impossible for unfunded open source projects to continue using TravisCI. Limits imposed by TravisCI are exceeded easily and that pushes each project that hits the limits either into a subscription or a temporarily suspended CI state. None is desirable hence we're removing the integration entirely.
@mp911de mp911de added this to the 6.0.9 milestone Dec 3, 2021
@mp911de
Copy link
Collaborator

mp911de commented Dec 3, 2021

Removed TravisCI.

@mp911de mp911de closed this as completed Dec 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: task A general task
Projects
None yet
Development

No branches or pull requests

2 participants