[JENKINS-33596] Delete more of UDPBroadcastThread & DNSMultiCast#5720
[JENKINS-33596] Delete more of UDPBroadcastThread & DNSMultiCast#5720timja merged 9 commits intojenkinsci:masterfrom
UDPBroadcastThread & DNSMultiCast#5720Conversation
|
Note that linked PRs mean that you will need to update tools to work with the new |
|
Hmm, it occurs to me this could cause problems for people running PCT across a lot of plugins with older POMs. Maybe I need to keep just |
…moveMulticast-redux
UDPBroadcastThread & DNSMultiCastUDPBroadcastThread & DNSMultiCast
jeffret-b
left a comment
There was a problem hiding this comment.
I'm in favor of using these old things, but I do know from experience there can be some odd dependencies on the existence of some of these pieces. While I'd like to get rid of it all, a more cautious excision as this has evolved into is more prudent.
Not sure I follow what you are saying. You approved this PR; do you have reservations? |
|
No reservations. And I think it's safer to leave a little bit of it behind like you ended up doing. |
|
To be clear, we cannot safely delete |
| <groupId>${project.groupId}</groupId> | ||
| <artifactId>jenkins-test-harness</artifactId> | ||
| <version>1589.vc23fca066d5c</version> | ||
| <version>1626.v46b0925e70db</version> |
There was a problem hiding this comment.
are the test failures related to updating this?
There was a problem hiding this comment.
any idea why dependabot isn't updating this?
updater | INFO <job_213087289> Checking if org.jenkins-ci.main:jenkins-test-harness 1589.vc23fca066d5c needs updating
proxy | 2021/09/26 19:10:19 [146] GET https://repo.jenkins-ci.org:443/public/org/jenkins-ci/jenkins/1.67/jenkins-1.67.pom
proxy | 2021/09/26 19:10:19 [146] 200 https://repo.jenkins-ci.org:443/public/org/jenkins-ci/jenkins/1.67/jenkins-1.67.pom
proxy | 2021/09/26 19:10:19 [148] GET https://repo.jenkins-ci.org:443/public/org/jenkins-ci/main/jenkins-test-harness/maven-metadata.xml
proxy | 2021/09/26 19:10:19 [148] 200 https://repo.jenkins-ci.org:443/public/org/jenkins-ci/main/jenkins-test-harness/maven-metadata.xml
proxy | 2021/09/26 19:10:19 [150] GET https://repo.maven.apache.org:443/maven2/org/jenkins-ci/main/jenkins-test-harness/maven-metadata.xml
proxy | 2021/09/26 19:10:19 [150] 404 https://repo.maven.apache.org:443/maven2/org/jenkins-ci/main/jenkins-test-harness/maven-metadata.xml
proxy | 2021/09/26 19:10:19 [152] HEAD https://repo.jenkins-ci.org:443/public/org/jenkins-ci/main/jenkins-test-harness/1589.vc23fca066d5c/jenkins-test-harness-1589.vc23fca066d5c.jar
proxy | 2021/09/26 19:10:19 [152] 200 https://repo.jenkins-ci.org:443/public/org/jenkins-ci/main/jenkins-test-harness/1589.vc23fca066d5c/jenkins-test-harness-1589.vc23fca066d5c.jar
updater | INFO <job_213087289> Latest version is 1589.vc23fca066d5c
| * | ||
| * @author Kohsuke Kawaguchi | ||
| * @deprecated No longer does anything. | ||
| * @deprecated No longer does anything. Only here to prevent errors from old versions of tools like {@code JenkinsRule}. |
There was a problem hiding this comment.
FTR tests still run with the older JenkinsRule
diff --git test/pom.xml test/pom.xml
index 1527fbcdcc..38d5934b15 100644
--- test/pom.xml
+++ test/pom.xml
@@ -81,7 +81,7 @@ THE SOFTWARE.
<dependency>
<groupId>${project.groupId}</groupId>
<artifactId>jenkins-test-harness</artifactId>
- <version>1626.v46b0925e70db</version>
+ <version>1589.vc23fca066d5c</version>
<scope>test</scope>
<exclusions>
<exclusion>…moveMulticast-redux
…kins into removeMulticast-redux
|
This PR is now ready for merge, after ~24 hours, we will merge it if there's no negative feedback. Thanks! |
Follows up #4460. See JENKINS-33596. These classes have been stubs for over a year and a half; it is just confusing to leave them in the source tree.
Proposed changelog entries
UDPBroadcastThread, and deleting more ofDNSMultiCast.Maintainer checklist
Before the changes are marked as
ready-for-merge:Proposed changelog entriesare correctupgrade-guide-neededlabel is set and there is aProposed upgrade guidelinessection in the PR title. (example)lts-candidateto be considered (see query).