[JIRA] (JENKINS-57661) The incrementals-publisher does not provide a reason for some 400 Bad Request errors

[chris+jenkins@chriskilding.com (JIRA)]

Chris Kilding created an issue

Jenkins / JENKINS-57661 The incrementals-publisher does not provide a reason for some 400 Bad Request errors Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-05-24 12:34 Environment: Server: ci.jenkins.io Priority: Minor Reporter: Chris Kilding When my plugin deploys to Jenkins Incrementals on ci.jenkins.io, sometimes I get a 400 Bad Request response but with no explanation in the body. This means that I (the plugin author) cannot know what has gone wrong. In addition, the deploy step of the plugin build passes, even though an error has occurred. An example build: https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Faws-secrets-manager-credentials-provider-plugin/detail/support%2Fdocumentation/5/pipeline Note: I filed this under ‘core’ because there was no component for ‘community-functions’. Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

[chris+jenkins@chriskilding.com (JIRA)]

Chris Kilding commented on JENKINS-57661

Re: The incrementals-publisher does not provide a reason for some 400 Bad Request errors Related discussion on the mailing list: https://groups.google.com/forum/m/#!topic/jenkinsci-dev/dpfPf-qyPzQ

Add Comment

[chris+jenkins@chriskilding.com (JIRA)]

Chris Kilding commented on JENKINS-57661

Re: The incrementals-publisher does not provide a reason for some 400 Bad Request errors

After I merged my ‘enable incremental releases’ branch to master and released an initial alpha version of my plugin to Artifactory, this error went away and deployments to incrementals started working. (I do not know which of these two actions fixed the problem though.) This precondition was non-obvious and undocumented, so I propose the following changes: A comment should be added to the https://github.com/jenkinsci/incrementals-tools README to say that incrementals releases will not work from branches until (either the master branch sees a successful incrementals release, or at least one version of the plugin is published with mvn release:perform - whichever of these was the cause). An instructive warning should be emitted from the incrementals-publisher function when this edge case occurs.

Add Comment

[chris+jenkins@chriskilding.com (JIRA)]

Chris Kilding closed an issue as Duplicate

Jenkins / JENKINS-57661

The incrementals-publisher does not provide a reason for some 400 Bad Request errors

Change By: Chris Kilding Status: Open Closed Resolution: Duplicate

Add Comment