release of branch-api plugin

Hey folks, I'm hoping to get a release of the branch-api plugin cut, so I can fix the YAML plugin's support for '/' named branches. The README mentions how to release, so is it OK for me to try to go ahead and do a release of this? If not, could I bug someone to do so? thanks, -M --

Re: [branch-api-plugin] Make triggering per-branch projects optional and use the SCMTriggerCause (#1)

Ping On Mon, Sep 29, 2014 at 8:57 PM, Matthew Moore mattm...@google.com wrote: *the other one needs discussion* Stephen, I repurposed this PR for this portion of the change. Would you like me to further elaborate on the use case? If not, what aspect would you like to discuss? I'm

Re: [ANN] Freestyle Multibranch Plugin looking for a maintainer

(shameless plug) FWIW, you can create a Multibranch Freestyle project using the YAML Project plugin http://github.com/jenkinsci/yaml-project-plugin today. (shrug), -M On Wed, Oct 8, 2014 at 7:30 AM, Jesse Glick jgl...@cloudbees.com wrote: On Wed, Oct 8, 2014 at 5:45 AM, Stephen Connolly

Re: Google OAuth Plugin does not load scope

Hrm, sadly there doesn't seem to be a nice client library for this API like there are for a lot of the cloud APIs... Regardless, the various Credential http://javadoc.google-oauth-java-client.googlecode.com/hg/1.8.0-beta/com/google/api/client/auth/oauth2/Credential.html?is-external=true objects

Re: Google OAuth Plugin does not load scope

I assume you are building a plugin to access this API, using an OAuth2 credential? Otherwise, I'll probably need some more context on how you plan to wire things up... If you are building such a plugin you should look at how the Google Cloud Storage plugin specifies its OAuth2 scope

Re: Google OAuth Plugin does not load scope

What plugins do you have installed that require OAuth? This plugin dynamically determines the set of OAuth scopes that might be required by installed plugins, to allow you to pick and choose which should be allowed for a given credential. Try installing google-storage-plugin, for example, and

Re: [branch-api-plugin] Make triggering per-branch projects optional and use the SCMTriggerCause (#1)

Is anyone willing/able to review this PR? There doesn't seem to be a huge amount of active development on this plugin, so I wanted to ping more broadly. thanks, -M On Fri, Sep 12, 2014 at 11:00 AM, Jenkins admin notificati...@github.com wrote: Thank you for a pull request! Please check this

new plugin hosting request

I have posted a new plugin here: https://github.com/mattmoor/yaml-project-plugin and added its associated wiki page here: https://wiki.jenkins-ci.org/display/JENKINS/YAML+Project+Plugin FWIW, this is the basis of the talk I plan to give at JUC 2014 this Fall. thanks, -M -- Matthew Moore

Re: new plugin hosting request

jenkinsci org at GitHub? Thanks! Bruno -- *From:* 'Matthew Moore' via Jenkins Developers jenkinsci-dev@googlegroups.com *To:* jenkinsci-dev@googlegroups.com jenkinsci-dev@googlegroups.com *Sent:* Tuesday, September 9, 2014 12:41 PM *Subject:* new plugin hosting

Re: new plugin hosting request

already tried the YAML plug-in and I liked it. Are there other ways to get the YAML file, like from some web site, ftp, etc? Thanks! Bruno [1] https://github.com/jenkinsci/yaml-project-plugin -- *From:* 'Matthew Moore' via Jenkins Developers jenkinsci-dev

Re: Global Post-Build Step

I'd bet you could build something with: http://javadoc.jenkins-ci.org/hudson/model/BuildStepListener.html However, their intent is purely observation, so YMMV. Not sure if there are any more suitable hooks that are intended for mutation. I think there is definitely a use case for global