Ok sorry, I'm fairly new to using Google's API and Jenkins and I think I
see where my confusion lies, I was thinking that the Google OAuth Plugin
automatically provides the scopes, however after relooking
at https://wiki.jenkins-ci.org/display/JENKINS/Google+OAuth+Plugin, I
realize that this pl
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 requirement:
Hi Jenkins Dev team,
I am with the Rational Team Concert(RTC) Development team in IBM
(www.ibm.com, www.jazz.net). We are developing a plugin which will
integrate Jenkins Builds using Git as Source control to RTC Work items and
builds. We would like to publish the plugin at jenkins-ci.org. Her
Update on Components refactoring:
- All required commands have been added to Jenkins IRC Bot (see
https://wiki.jenkins-ci.org/display/JENKINS/IRC+Bot)
- Major core components have been renamed and merged (see the status on
https://wiki.jenkins-ci.org/display/JENKINS/2014+JIRA+Components+Refactori
Hello Anthony,
Are there any other possible use-cases excepting the pyblishing to your
server?
If no, what about changing the plugin's name to codedx-publisher?
Best regards,
Oleg Nenashev
пятница, 26 сентября 2014 г., 22:50:58 UTC+4 пользователь Anthony DeMartini
написал:
>
> Greetings,
>
>
Thanks Richard, let's take this off list.
2014-09-26 21:23 GMT-07:00 Richard Lavoie :
> Hi Kohsuke,
>
> That could be a very good opportunity I am interested in but I'm currently
> based near Montreal, Canada.
>
> I'm currently the maintainer of the selenium plugin, even though I haven't
> had ti
In my opinion, the plugin's name is too vague.
Ratchet and Ratcheting words are just the slang without a valuable info
about the real functionality (build log analysis?).
Could you consider the plugin's renaming?
Several proposals regarding pom.xml
- groupId: What about com.mattersight.jenkin
Hi,
Can I be provided with commit access to the configuration slicing plugin
github repository please, in line with what is suggested in
https://wiki.jenkins-ci.org/display/JENKINS/Governance+Document#GovernanceDocument-Makingchangestoexistingplugins?
I’ve contacted the previous maintainer, and
Hi,
I want to publish a new release of the gradle-jpi-plugin. Previous release
artifacts of that plugin have been signed with some GPG key, e.g.
http://repo.jenkins-ci.org/public/org/jenkins-ci/tools/gradle-jpi-plugin/0.5.0/
Signing artifacts seems to be a good idea in general. Is there some kind
