Skip to content

MINOR: Remove broken .travis.yml with system test hooks#9666

Closed
hachikuji wants to merge 1 commit intoapache:trunkfrom
hachikuji:remove-travis-ducktape-hook
Closed

MINOR: Remove broken .travis.yml with system test hooks#9666
hachikuji wants to merge 1 commit intoapache:trunkfrom
hachikuji:remove-travis-ducktape-hook

Conversation

@hachikuji
Copy link
Copy Markdown
Contributor

@hachikuji hachikuji commented Dec 1, 2020

This patch removes .travis.yml which has never worked as far as I know, and is lately cluttering up PR requests.

Committer Checklist (excluded from commit message)

  • Verify design and implementation
  • Verify test coverage and CI build status
  • Verify documentation (including upgrade notes)

@hachikuji
Copy link
Copy Markdown
Contributor Author

hachikuji commented Dec 1, 2020

cc @chia7712 I guess you were trying to get this working instead? I can close this if you prefer.

@dajac
Copy link
Copy Markdown
Member

dajac commented Dec 1, 2020

I am +1 on removing it. We can always bring it back to trunk if we can make it work later.

@chia7712
Copy link
Copy Markdown
Member

chia7712 commented Dec 2, 2020

guess you were trying to get this working instead?

#9652

Removing travis test is ok to me.

@hachikuji
Copy link
Copy Markdown
Contributor Author

@chia7712 Nice that you got it working! I think there is value running a subset of system tests automatically. It might even encourage us to write more system tests if we can get the feedback more easily. Not having access to logs is annoying, but might not be a dealbreaker. It looks like we need a bit of initial work to tune the build though. I'm happy to close this and merge #9652. Then perhaps we can file a few jiras for any follow-up actions. What do you think?

@chia7712
Copy link
Copy Markdown
Member

chia7712 commented Dec 2, 2020

Nice that you got it working! I think there is value running a subset of system tests automatically. It might even encourage us to write more system tests if we can get the feedback more easily. Not having access to logs is annoying, but might not be a dealbreaker. It looks like we need a bit of initial work to tune the build though. I'm happy to close this and merge #9652. Then perhaps we can file a few jiras for any follow-up actions. What do you think?

+1

@hachikuji
Copy link
Copy Markdown
Contributor Author

Closing in favor of #9652.

@hachikuji hachikuji closed this Dec 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants