Ah, that means my release actually failed then. I was correctly using maven-release-plugin 2.5 though, with git 1.9.1, so I don't think this bug was the issue (unless I'm not thinking about the right bug). However it's possible that I messed up during release. I had some trouble with credentials since my jenkins name is not the same as my github name. How can I try the release again? The maven-release-plugin has already pushed changes to the jenkinsci repository: https://github.com/jenkinsci/cloudfoundry/commit/07b805b1bc59af77eb49253f48debe80b54f02aa
On Friday, November 7, 2014 3:11:55 PM UTC-8, Daniel Beck wrote: > > Only a snapshot was published to Artifactory, so it may be the > maven-release-plugin 2.5 issue? > > On 08.11.2014, at 00:00, William Gautier <[email protected] <javascript:>> > wrote: > > > Hi Daniel, > > > > I've had a successful 'mvn release:prepare release:perform' yesterday, > but I'm still not seeing the plugin on the update center. > > > > I've looked at the "Help! My plugin is not showing up in the update > center." paragraph on the Hosting Plugins page, and I'm not seeing my > plugin on either of these pages. > > What I did notice is that the Jenkins build mentioned in that paragraph, > which used to be hourly, was disabled yesterday. Is this related? Should I > just wait for this build to resume? How long could it take? > > > > I've attached the output of the mvn release command. > > > > Thanks, > > William > > > > On Wednesday, November 5, 2014 10:29:41 AM UTC-8, Daniel Beck wrote: > > Sorry about the delay! > > > > Repo: > > https://github.com/jenkinsci/cloudfoundry-plugin > > > > Issue Tracker: > > https://issues.jenkins-ci.org/browse/JENKINS/component/19824 > > > > if you tell us your jenkins-ci.org username (used for wiki, issue > tracker, releasing plugins), I'll make you default assignee of the Jira > component. > > > > A general recommendation on artifactIds is to leave out the 'plugin', so > 'cloudfoundry' would be sufficient. Don't change this after the first > release. > > > > On 05.11.2014, at 19:18, William Gautier <[email protected]> wrote: > > > > > Sorry to bump this again, but I'm seeing other hosting requests be > answered much faster, and I would like some attention on this even if it's > some negative feedback. If the Jenkins guidelines are not met, please tell > me what must be changed. > > > I'm thinking my thread title is being confused with another similar > title so if this doesn't get responses, I will make another thread with a > more descriptive title. > > > > > > Thanks, > > > William > > > > > > On Monday, November 3, 2014 11:27:46 AM UTC-8, William Gautier wrote: > > > Any update on this? I believe there is no already existing > alternative, since even the official Cloud Foundry tutorials use Jenkins > with shell commands or Maven plugins. > > > > > > On Wednesday, October 29, 2014 3:32:55 PM UTC-7, William Gautier > wrote: > > > Hi, > > > > > > I would like to request hosting of a new plugin. The plugin allows > pushing a project to a Cloud Foundry platform, as a post-build step. > > > > > > GitHub name: cloudfoundry-plugin > > > GitHub ID: WGautier > > > GitHub repository: https://github.com/WGautier/cloudfoundry-jenkins > > > > > > Not too sure about the conventions for the artifactId or the plugin > name, so feel free to advise. I renamed the plugin's name from > cloudfoundry-jenkins to cloudfoundry-plugin since I understand that would > be redundant. > > > > > > Thanks, > > > William Gautier > > > > > > -- > > > 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]. > > > For more options, visit https://groups.google.com/d/optout. > > > > <mvn_release_output.txt> > > -- 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]. For more options, visit https://groups.google.com/d/optout.
