Incrementals builds are not published for bitbucket-source-plugin

28 views
Skip to first unread message

Nikolas Falco

unread,
Jun 2, 2025, 7:36:36 PM6/2/25
to Jenkins Developers
I notice that is more than a week that increments build are no more published for PRs of bitbucket-source-plugin.

I verify that this behaviour happens in most recent PRs like this

and PR built on 28 may

I notice in this PR in blue-ocean plugin that fails with the following error
[ERROR] dependency: org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source:jar:936.3.21098.v755e044fdce9 (compile) 00:52:52 [ERROR] Could not find artifact org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source:jar:936.3.21098.v755e044fdce9 in artifact-caching-proxy (http://artifact-caching-proxy.artifact-caching-proxy.svc.cluster.local:8080/)


I had analyze logs from PR build and seems that the HTTP POST to artifactory does not work as expected:

14:31:19 [Pipeline] withCredentials
14:31:19 Masking supported pattern matches of $FUNCTION_TOKEN
14:31:19 [Pipeline] {
14:31:19 [Pipeline] httpRequest
14:31:19 HttpMethod: POST
14:31:19 Content-Type: application/json 
14:31:19 Authorization: ***** 
14:31:19 Sending request to url: https://incrementals.jenkins.io/ 
14:31:20 Response Code: HTTP/1.1 400 Bad Request 
14:31:20 Response: 
14:31:20 Invalid archive retrieved from Jenkins, perhaps the plugin is not properly incrementalized? 
14:31:20 Error: ZIP error: Error: Wrong commit hash in /project/scm/tag, expected 783ed3a83e084dda50218b28bde2eb6ad618b623, got 936.3.1 from https://ci.jenkins.io/job/Plugins/job/bitbucket-branch-source-plugin/job/PR-976/8/artifact/**/*783ed3a*83e08*/*783ed3a*83e08*/*zip*/archive.zip 
14:31:20 Success: Status code 400 is in the accepted range: 100:599

It say success also if artifactory respond with a failure, the correct success range should be 200:399 or better 200:299

Anyone can have a look? Should I open defect to jenkins-infra?

Basil Crow

unread,
Jun 2, 2025, 7:58:20 PM6/2/25
to jenkin...@googlegroups.com
This ought to do the trick:

diff --git a/pom.xml b/pom.xml
index 529c0e2..4d2cce0 100644
--- a/pom.xml
+++ b/pom.xml
@@ -64,7 +64,7 @@
<connection>scm:git:https://github.com/${gitHubRepo}.git</connection>
<developerConnection>scm:git:g...@github.com:${gitHubRepo}.git</developerConnection>
<url>https://github.com/${gitHubRepo}</url>
- <tag>936.3.1</tag>
+ <tag>${scmTag}</tag>
</scm>

<dependencyManagement>

Nikolas Falco

unread,
Jun 2, 2025, 8:14:15 PM6/2/25
to Jenkins Developers
The same happens for other plugins i managed like nodejs-plugin, dependecy-check, xunit-plugin
Thanks I'm try the patch
Reply all
Reply to author
Forward
0 new messages