I’ve followed the guide to make a plugin upload to Jenkins Incrementals after successful builds.
It fails after a couple of minutes of uploading with 400 Bad Request, however the deploy step in Jenkins that runs this command actually passes. This doesn’t seem right - any suggestions? The relevant part of one such build log is shown below. A full build log is available at https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Faws-secrets-manager-credentials-provider-plugin/detail/master/6/pipeline 18:32:45 + curl -i -H Content-Type: application/json -d {"build_url":"https://ci.jenkins.io/job/Plugins/job/aws-secrets-manager-credentials-provider-plugin/job/master/6/"} https://jenkins-incrementals.azurewebsites.net/api/incrementals-publisher?clientId=default&code=**** 18:34:24 HTTP/1.1 400 Bad Request 18:34:24 Content-Length: 352 18:34:24 Content-Type: text/plain; charset=utf-8 18:34:24 Date: Mon, 20 May 2019 17:34:23 GMT 18:34:24 18:34:24 Invalid archive retrieved from Jenkins, perhaps the plugin is not properly incrementalized? Chris -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/ed8b95c7-8bcf-4b9b-afcc-f96ddc7b4333%40www.fastmail.com. For more options, visit https://groups.google.com/d/optout.
