Increase test timeout of MavenTest#sensitiveParameters()

[NotMyFault]

The change proposed updates the test timeout of MavenTest#sensitiveParameters(). For some yet unknown reason, the test takes ~220 (!!) seconds to complete on ci.jenkins.io.

Locally, the entire MavenTest takes less than 30s to complete, and used to take ~60s on ci.jenkins.io, as seen in a recent build a couple of days ago.

Out of an abundance of caution, looking towards the next weekly release, I'd propose to raise the test timeout temporarily, to restore a functional build on ci.jenkins.io and give us some time to look into it .

Testing done

mvn clean verify -Dtest=hudson.tasks.MavenTest is successful.

Proposed changelog entries

• JENKINS-XXXXX, human-readable text

Proposed upgrade guidelines

N/A

Submitter checklist

Beta Give feedback

1. The Jira issue, if it exists, is well-described.
2. 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.
3. There is automated testing or an explanation as to why this change has no tests.
4. New public classes, fields, and methods are annotated with @Restricted or have @since TODO Javadocs, as appropriate.
5. New deprecations are annotated with @Deprecated(since = "TODO") or @Deprecated(forRemoval = true, since = "TODO"), if applicable.
6. New or substantially changed JavaScript is not defined inline and does not call eval to ease future introduction of Content Security Policy (CSP) directives (see documentation).
7. For dependency updates, there are links to external changelogs and, if possible, full differentials.
8. For new APIs and extension points, there is a link to at least one consumer.

Desired reviewers

@mention

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

Maintainer checklist

Beta Give feedback

1. There are at least two (2) approvals for the pull request and no outstanding requests for change.
2. Conversations in the pull request are over, or it is explicit that a reviewer is not blocking the change.
3. Changelog entries in the pull request title and/or Proposed changelog entries are accurate, human-readable, and in the imperative mood.
4. Proper changelog labels are set so that the changelog can be generated automatically.
5. 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).
6. If it would make sense to backport the change to LTS, a Jira issue must exist, be a Bug or Improvement, and be labeled as lts-candidate to be considered (see query).

[MarkEWaite]

We had a problem with the artifact caching proxy on at least one of the cloud providers. That problem inserted a 30 second timeout into certain maven operations. The test may be affected by that problem. Refer to the help desk ticket for more info

• Artifact caching proxy repo.do.jenkins.io is not answering requests from bom build jenkins-infra/helpdesk#3889

Currently being discussed and explored in the Jenkins infra gitter channel

[MarkEWaite]

The artifact caching proxy issue seems to be resolved. I've restarted several core pull request builds to check. Those builds incluide:

• https://ci.jenkins.io/job/Core/job/jenkins/view/change-requests/job/PR-8831/
• https://ci.jenkins.io/job/Core/job/jenkins/view/change-requests/job/PR-8832/
• https://ci.jenkins.io/job/Core/job/jenkins/view/change-requests/job/PR-8834/
• https://ci.jenkins.io/job/Core/job/jenkins/view/change-requests/job/PR-8835/
• https://ci.jenkins.io/job/Core/job/jenkins/view/change-requests/job/PR-8836/

[MarkEWaite]

Merging to fix tests on the master branch

[NotMyFault]

Despite replaying the job, https://ci.jenkins.io/job/Core/job/jenkins/view/change-requests/job/PR-8835/ failed for the same reason. I'll file an independent helpdesk issue, thanks nonetheless!