Release Delete Request

[JordanGS]

There werre some problems because i released with Java 8, i was unable to run this properly on my Java 7 jenkins. I thought i could just release again and overwrite the existing folder but i can't. Live and learn i suppose. Next time i'll increment to 1.0.1 as a hotfix but for now because i already deleted the tags from my GitHub can you please delete the the release from (https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/zap/1.0.0/)

Error i get is, Access denied, ReasonPhrase: Forbidden which makes sense since it already exists.

Sorry for the trouble and thank you.

[Daniel Beck]

We're typically not deleting releases. Create a new release 1.0.1 which will supersede this one, or (only if not reasonably possible) file a PR (with explanation) at https://github.com/jenkinsci/backend-update-center2 to ignore it from the file artifact-ignores.properties.

FWIW nobody cares about the exact version numbers, and many plugins occasionally have an unusable release. Just fix it in the next one and move on.

[JordanGS]

@Daniel Beck You said typically, is there any way you can make an exception in this one instance? Most people don't care but in this instance I care simply because it's the initialy release. I don't plan on releasing unusable releases in the future either. I would simply do a 1.0.1 if i had kept the release tags in my github repository but i didn't. Now if i could do it myself i would but i can't and i have to ask for help.

FYI, a useful addition/warnings/notices to add to https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins would be

How to setup the Jenkins Cloudbee's github webhooks and a notice about that default builds on jenkins.ci.cloudbees.com are configured with Java 7 because Jenkins itself is always supposed to be compatible with J7, the build can be configured to use J8 but in that case you'll have to correctly document that your plugin won't run on instances using J7. Sadly there is no metadata in the update center to let users know it from the plugins manager.

I can add it myself if you like later on.

[Jesse Glick]

On Fri, Nov 18, 2016 at 5:56 PM, JordanGS <develop...@gmail.com> wrote:
> a useful addition/warnings/notices to add to
> https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins would be
>
> How to setup the Jenkins Cloudbee's github webhooks and a notice about that
> default builds on jenkins.ci.cloudbees.com are configured with Java 7
> because Jenkins itself is always supposed to be compatible with J7, the
> build can be configured to use J8 but in that case you'll have to correctly
> document that your plugin won't run on instances using J7.

Again this is *not* correct.

[JordanGS]

I understand that now. Thank you Jesse, but adding the webhook to  jenkins.ci.cloudbees.com (howto/information on github settings to cloudbees) would be useful i think, i couldn't find that anywhere and i was wondering the entire time why it wasn't building on there since it says "To have your plugin built on jenkins.ci.cloudbees.com, you do not need to do anything".