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

[ZOOKEEPER-4642] Remove Travis CI #1952

Merged
merged 1 commit into from
Dec 10, 2022

Conversation

eolivelli
Copy link
Contributor

No description provided.

Copy link
Contributor

@cnauroth cnauroth left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1

Thank you, @eolivelli !

@eolivelli eolivelli merged commit f1d69fd into apache:master Dec 10, 2022
@kezhuw
Copy link
Member

kezhuw commented May 9, 2023

Hmm, seems that we lost ci for arm64 ? ZOOKEEPER-4668(#1975) added back s390x in jenkins. Given that we have c client, I think it is valuable to enable ci for multiple archs. cc @ztzg @ctubbsii

@ctubbsii
Copy link
Member

ctubbsii commented May 9, 2023

@kezhuw wrote:

Hmm, seems that we lost ci for arm64 ? ZOOKEEPER-4668(#1975) added back s390x in jenkins. Given that we have c client, I think it is valuable to enable ci for multiple archs. cc @ztzg @ctubbsii

I have no idea why I'm being tagged here. @kezhuw if you don't have a specific question for somebody, I don't recommend that you tag them. If they want to follow an issue, they can do so on their own. Otherwise, all you've done is annoy them with a confusing notification that requires them to try to figure out why they are being tagged, and potentially forces them to be subscribed to an issue they did not want to follow. I don't generally mind people tagging me for a good reason, but just tagging without a reason is really frustrating. Please don't do that.

@kezhuw
Copy link
Member

kezhuw commented May 9, 2023

I saw #1508 which you created and didn't not break arm64 ci introduced in #1433 which you approved. @ctubbsii Sorry for this tagging, I will try to not unless strong reason. Thank you to let me know this! I usually tracked issue history a bit to find someone for opinion/review. Next time, I will describe the reason.

Also, I cced @ztzg for both #1433 and C skill in case he feel annoying too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
4 participants