[JENKINS-75409] Write a core it test for -noCertificateCheck and -cert for inbound agents

[gbhat618]

This is downstream PR for jenkinsci/remoting#786

I am currently not able to understand how I can configure -noCertificateCheck and -cert option to the InboundAgentRule

This is draft PR to get help how to accomplish this.

See JENKINS-XXXXX.

Testing done

Proposed changelog entries

• human-readable text

Proposed changelog category

/label

Proposed upgrade guidelines

N/A

Submitter checklist

• The Jira 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.
• New public classes, fields, and methods are annotated with @Restricted or have @since TODO Javadocs, as appropriate.
• New deprecations are annotated with @Deprecated(since = "TODO") or @Deprecated(forRemoval = true, since = "TODO"), if applicable.
• 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).
• For dependency updates, there are links to external changelogs and, if possible, full differentials.
• 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

• 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, a Jira issue must exist, be a Bug or Improvement, and be labeled as lts-candidate to be considered (see query).

[welcome]

Yay, your first pull request towards Jenkins core was created successfully! Thank you so much!

A contributor will provide feedback soon. Meanwhile, you can join the chats and community forums to connect with other Jenkins users, developers, and maintainers.

[gbhat618]

The build seems to be not having these certificate related options,
https://github.com/jenkinsci/jenkins-test-harness/blob/42ffa3423ed97d8d589c7ea26998325019b747f3/src/main/java/org/jvnet/hudson/test/InboundAgentRule.java#L96

I see there is some argument parsing in here,
https://github.com/jenkinsci/jenkins-test-harness/blob/42ffa3423ed97d8d589c7ea26998325019b747f3/src/main/java/org/jvnet/hudson/test/InboundAgentRule.java#L523-L529

but I am not able to understand if I can pass arguments like -noCertificateCheck or -cert

[gbhat618]

my goal is to reproduce and later test passes after jenkinsci/remoting#786

[gbhat618]

@jglick or @Vlatombe can you help with some pointers how to go about

[jglick]

From a five-second glance, I guess you would need to add an option to IAR to add custom agent arguments.

[github-actions]

Missing required label for changelog. Requires at least 1 of: bug, developer, dependencies, internal, localization, major-bug, major-rfe, rfe, regression-fix, removed, skip-changelog. Found: tests.

You can add the required label by adding a comment with the following text: /label <category>