Re: [Jenkins-events] Hacktoberfest - Do we want to participate this year?

Created the blogpost PR: https://github.com/jenkins-infra/jenkins.io/pull/1165 среда, 4 октября 2017 г., 0:39:55 UTC+2 пользователь alytong13 написал: > > lemme know how I can help > > On Mon, Oct 2, 2017 at 7:45 AM, Oleg Nenashev > wrote: > >> OK, I will "just do that"

Re: How to utilize maven configurations in custom plugin.

The above code helped me in getting the maven installation drop-down in my plugin. But for getting the Installer path it is suggesting me to get the path using ToolKitInstaller.getHome. How do I get the exact maven path from the bunch of available maven installations? Is there a sample code to get

Re: Request to join Jenkins CERT team

> On 5. Oct 2017, at 19:12, wfollon...@cloudbees.com wrote: > > I would like to request access to join the Jenkins CERT team. > > • GitHub 2-factor auth enabled: yes > • Signed CLA: > https://github.com/jenkinsci/infra-cla/tree/master/collected/icla/wfollonier > • GitHub

Re: Request to join Jenkins CERT team

+1 -- 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 jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit

Request to join Jenkins CERT team

Hello, I would like to request access to join the Jenkins CERT team. - GitHub 2-factor auth enabled: yes - Signed CLA: https://github.com/jenkinsci/infra-cla/tree/master/collected/icla/wfollonier - GitHub Username: wadeck - IRC Nickname: wadeck -

Re: Commit access to vstestrunner-plugin

I did read the link. I had actually read it (along with quite a bit of the rest of the documentation) before I created the PR that I was trying to merge. There is evidence of this. Notice I tagged the PR per the documentation and that was 11 days ago. The first message I forwarded to Yasu from

Re: Request for feedback: Jenkins Enhancement Proposal (JEP)

There has been a tremendous amount of productive discussion, with a lot of helpful editing work by Liam. I think the process is ready for an approval in a Governance meeting, so I'm going to put the proposal on the agenda for the Oct 11th meeting. Proposal:

Re: Commit access to vstestrunner-plugin

Well, technically if you read the link I provided, we would usually wait again ~13 days, given IIUC you've CCed Yasu yesterday (?). 2017-10-05 16:17 GMT+02:00 Erik Goughnour : > Requesting commit access again. > > Surely the touchstones are all giving favorable indications

Re: Adding DeclarativeOption to plugin

Hmm, that might actually be a better option - Thanks! Jeff On 10/4/17, 9:20 AM, "jenkinsci-dev@googlegroups.com on behalf of Jesse Glick" wrote: On Mon, Oct 2, 2017 at 3:01 PM, wrote: > I'm

Re: Commit access to vstestrunner-plugin

Requesting commit access again. Surely the touchstones are all giving favorable indications by now. Elapsed time, respect, courtesy, required information, multiple attempts to contact—was there anything else? Thanks, Erik On Wednesday, October 4, 2017, Erik Goughnour

Re: Warning during multi-branch Indexing

On Thu, Oct 5, 2017 at 6:50 AM, Paul Allen wrote: > the version mix was tricky to satisfy > and needed a few excludes... > > https://github.com/jenkinsci/p4-plugin/commit/fb48f85b0dbcf817efa6e74e236268eaf3043ebb I added some comments. -- You received this message because

Re: Warning during multi-branch Indexing

I have removed the workflow-aggregator and added the few test dependancies to the POM. All seems ok, although the version mix was tricky to satisfy and needed a few excludes... https://github.com/jenkinsci/p4-plugin/commit/fb48f85b0dbcf817efa6e74e236268eaf3043ebb I had to use a VERY OLD