Skip to content

Skip ssh host tests on ci.jenkins.io #1255

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

Merged

Conversation

MarkEWaite
Copy link
Contributor

Skip ssh host verifier tests on ci.jenkins.io

The GitHub SSH abuse prevention system rejects connections from the tests when they are run on ci.jenkins.io. These tests should only be run as end to end acceptance tests but they are not too disruptive (for now) to continue to be included in the default tests.

Additional tests should be created that use test containers so that they can use the ssh connection on the test container instead of using the GitHub.com SSH servers.

Unfortunately, I can't prioritize that test rewrite now, so these tests are disabled on ci.jenkins.io.

Testing done

Confirmed that automated tests pass locally where the tests are not excluded. Final confirmation on ci.jenkins.io where the tests will fail if not excluded.

Submitter checklist

  • Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
  • Ensure that the pull request title represents the desired changelog entry
  • Please describe what you did
  • Link to relevant issues in GitHub or Jira
  • Link to relevant pull requests, esp. upstream and downstream changes
  • Ensure you have provided tests - that demonstrates feature works or fixes the issue

The GitHub.com SSH abuse prevention system rejects connections from
the tests when they are run on ci.jenkins.io.  These tests should only
be run as end to end acceptance tests but they are not too disruptive
(for now) to continue to be included in the default tests.

Additional tests should be created that use test containers so that they
can use the ssh connection on the test container instead of using the
GitHub.com SSH servers.

Unfortunately, I can't prioritize that test rewrite now, so these tests
are disabled on ci.jenkins.io.
@MarkEWaite MarkEWaite added the test Automated test addition or improvement label Feb 14, 2025
@MarkEWaite MarkEWaite requested a review from a team as a code owner February 14, 2025 02:17
@github-actions github-actions bot added the tests Automated test addition or improvement label Feb 14, 2025
@MarkEWaite MarkEWaite removed the test Automated test addition or improvement label Feb 14, 2025
@MarkEWaite MarkEWaite merged commit 2d90e37 into jenkinsci:stable-5.0 Feb 14, 2025
16 checks passed
@MarkEWaite MarkEWaite deleted the stable-5.0-fix-failing-tests branch February 14, 2025 02:37
MarkEWaite added a commit that referenced this pull request Feb 14, 2025
The GitHub.com SSH abuse prevention system rejects connections from
the tests when they are run on ci.jenkins.io.  These tests should only
be run as end to end acceptance tests but they are not too disruptive
(for now) to continue to be included in the default tests.

Additional tests should be created that use test containers so that they
can use the ssh connection on the test container instead of using the
GitHub.com SSH servers.

Unfortunately, I can't prioritize that test rewrite now, so these tests
are disabled on ci.jenkins.io.

(cherry picked from commit 2d90e37)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
tests Automated test addition or improvement
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant