Skip to content

Check security tests on master branch#26081

Closed
MarkEWaite wants to merge 7 commits intojenkinsci:masterfrom
MarkEWaite:master-branch-security-tests
Closed

Check security tests on master branch#26081
MarkEWaite wants to merge 7 commits intojenkinsci:masterfrom
MarkEWaite:master-branch-security-tests

Conversation

@MarkEWaite
Copy link
Contributor

Check security tests on master branch

Do not merge.

A few builds of the master branch have reported failures in one or more of the security tests on Windows. Rather than wait for the long test time on Windows, this draft pull request will only run the security tests, skipping ATH and skipping other tests.

Testing done

Confirmed that tests run locally on my Linux computer with Java 21. Rely on ci.jenkins.io for Windows

Proposed changelog entries

  • N/A

Proposed changelog category

/label skip-changelog

Proposed upgrade guidelines

N/A

Submitter checklist

  • The issue, if it exists, is well-described.
  • The changelog entries and upgrade guidelines are appropriate for the audience affected by the change (users or developers, depending on the change) and are in the imperative mood (see examples). Fill in the Proposed upgrade guidelines section only if there are breaking changes or changes that may require extra steps from users during upgrade.
  • There is automated testing or an explanation as to why this change has no tests.

Desired reviewers

N/A

Before the changes are marked as ready-for-merge:

Maintainer checklist

  • There are at least two (2) approvals for the pull request and no outstanding requests for change.
  • Conversations in the pull request are over, or it is explicit that a reviewer is not blocking the change.
  • Changelog entries in the pull request title and/or Proposed changelog entries are accurate, human-readable, and in the imperative mood.
  • Proper changelog labels are set so that the changelog can be generated automatically.
  • If the change needs additional upgrade steps from users, the upgrade-guide-needed label is set and there is a Proposed upgrade guidelines section in the pull request title (see example).
  • If it would make sense to backport the change to LTS, be a Bug or Improvement, and either the issue or pull request must be labeled as lts-candidate to be considered.

@MarkEWaite MarkEWaite added work-in-progress The PR is under active development, not ready to the final review skip-changelog Should not be shown in the changelog labels Jan 7, 2026
Needs to be a bundled plugin.

It is desirable to have the image URL be unlikely to change in the
future, and matrix project seems unlikely to have major user interface
work in the future.
@MarkEWaite
Copy link
Contributor Author

Closing. The issue this was exploring is resolved by pull request:

@MarkEWaite MarkEWaite closed this Jan 8, 2026
@MarkEWaite MarkEWaite deleted the master-branch-security-tests branch January 8, 2026 12:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

skip-changelog Should not be shown in the changelog work-in-progress The PR is under active development, not ready to the final review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant