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

Travis CI: Abuse detected #1494

nnposter opened this Issue Feb 23, 2019 · 2 comments


None yet
2 participants
Copy link

nnposter commented Feb 23, 2019

Travis CI is refusing to build nmap as new commits propagate from SVN to GitHub. The specific result is Job rejected with Abuse detected.

Judging by build history, this issue might have first occurred on or after August 14, 2018.


This comment has been minimized.

Copy link

dmiller-nmap commented Feb 26, 2019

I'll try to contact @travis-ci support to see if they can clue us in to why it's being flagged. Looks like they don't publicly disclose the kinds of things that trip their abuse sensors.

Unlikely to be related, but if you are making commits that don't contain things that affect the build (documentation changes, comments, etc), you can put [ci skip] in the commit message to skip the build. I hardly ever remember to do this, but it's probably a good idea to be courteous, since we're taking advantage of their free-for-open-source service.


This comment has been minimized.

Copy link

nnposter commented Feb 26, 2019

Am I correct that there is no value in invoking Travis if the commit is limited to nselib and/or scripts?

As an example, I have not noticed that luac -p gets called to assure basic syntax correctness. On the other hand, is that something that would be useful to start doing?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.