Re: [GSoC 2018] - Preliminary announcement

2018-01-23 Thread Oleg Nenashev 
Hi Willy,

Sure, it is possible. The list is here

.
You could just add your name to the projects you would be interested in.

BR, Oleg


2018-01-24 5:27 GMT+01:00 Willy Aguirre :

> Hi Oleg!
> what happend If I don't an idea for GSoC =/ could I mentor with someone?
> or there are list of possible ideas I could take?
>
> On Friday, December 15, 2017 at 9:31:54 AM UTC-5, Oleg Nenashev wrote:
>>
>> Hi all,
>>
>> I am preparing to the launch of Google Summer of Code 2018
>>  in the Jenkins
>> project. As in 2016/2017, we will be looking for mentors
>> . It is
>> critical to have a diverse number of proposal so that the Jenkins Project
>> could get accepted this year, so I want to start it early this year.
>>
>> GSoC is a pretty big deal for mentors (several hours per week), but it is
>> possible to get a full-time student working on your project for almost 4
>> months. Mentorship does not require deep knowledge of Jenkins development
>> itself, because there will be advisors around. So any contributor can
>> participate if he has interest in it and opportunity to dedicate enough
>> time.
>>
>> Would somebody be interested to be a mentor? If yes, just respond to this
>> thread.
>>
>> -
>>
>> Useful links:
>>
>>- GSoC 2018 timeline
>>
>>- GSoC 2017 announcement with details
>>
>>- GSoC 2016 project idea examples
>>
>>- GSoC Mentor Guide 
>>
>> More documentation will be published this month if there is an interest
>> in the community.
>>
>> Best regards,
>> Oleg
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/jenkinsci-dev/We-14-z_YXU/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-dev/71fae086-1f23-490a-b97a-b6dc93d5e1b5%
> 40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 
https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLAjZEKQotMV5TQP1k807OzMvy53t%3D4w2E3WAu64-8HGcA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [GSoC 2018] - Preliminary announcement

2018-01-23 Thread Willy Aguirre 
Hi Oleg! 
what happend If I don't an idea for GSoC =/ could I mentor with someone? or 
there are list of possible ideas I could take?

On Friday, December 15, 2017 at 9:31:54 AM UTC-5, Oleg Nenashev wrote:
>
> Hi all,
>
> I am preparing to the launch of Google Summer of Code 2018 
>  in the Jenkins project. 
> As in 2016/2017, we will be looking for mentors 
> . It is 
> critical to have a diverse number of proposal so that the Jenkins Project 
> could get accepted this year, so I want to start it early this year.
>
> GSoC is a pretty big deal for mentors (several hours per week), but it is 
> possible to get a full-time student working on your project for almost 4 
> months. Mentorship does not require deep knowledge of Jenkins development 
> itself, because there will be advisors around. So any contributor can 
> participate if he has interest in it and opportunity to dedicate enough 
> time.
>
> Would somebody be interested to be a mentor? If yes, just respond to this 
> thread.
>
> -
>
> Useful links:
>
>- GSoC 2018 timeline 
>
>- GSoC 2017 announcement with details
>
>- GSoC 2016 project idea examples 
>
>- GSoC Mentor Guide 
>
> More documentation will be published this month if there is an interest in 
> the community.
>
> Best regards,
> Oleg
>

-- 
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 
https://groups.google.com/d/msgid/jenkinsci-dev/71fae086-1f23-490a-b97a-b6dc93d5e1b5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Pluging development - version confusion

2018-01-23 Thread Jesse Glick 
On Tue, Jan 23, 2018 at 3:40 PM, Scott Dunbar  wrote:
> I was attempting
> to get a nested JSON structure parsing from an optionBlock inside of the
> Jelly file and had added two of the constructors.  Obviously that's not
> correct.

No, it is not. To do things the Jenkins Way™ you need something like
`f:optionalProperty` and a distinct `Describable` type (with its own
`config.jelly`) for the nested structure, at which point you simply
declare a property of that nested type and there is no need to fool
around with low-level JSON stuff or legacy controls. See
`ui-samples-plugin` for examples of this kind of thing.

-- 
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 
https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1LXsaRn2xuR2AabwO%3DByhoVEnZfPrAmQ21VbDMPRzDHA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Pluging development - version confusion

2018-01-23 Thread Scott Dunbar 


On Monday, January 22, 2018 at 3:19:31 PM UTC-7, Scott Dunbar wrote:
>
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-compiler-plugin:3.6.1:compile 
> (default-compile) on project formPoller: Compilation failure
> [ERROR] javax.annotation.processing.FilerException: Attempt to reopen a 
> file for path 
> C:\Users\sdunbar\work\company\jenkins-form-poller\target\classes\com\company\jenkins\form\NewFormPoller.stapler
>

For intrepid future web surfers running across the same issue - the issue 
was that I had two @DataBoundConstructors in my Builder.  I was attempting 
to get a nested JSON structure parsing from an optionBlock inside of the 
Jelly file and had added two of the constructors.  Obviously that's not 
correct.

-- 
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 
https://groups.google.com/d/msgid/jenkinsci-dev/06f065f1-afd1-4f59-9fe1-976a3bc93645%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: repository-connector plugin maintainence

2018-01-23 Thread domi 
Hey Jae,

I don’t know why my last email did not reach you, but I did answer you a few 
days ago…
Here is a copy:


Hi Jae,

There is no need to enable travis, as every Jenkins Plugin hosted in the 
Jenkins GH Org, we can make use of the Jenkins Project Infrastructure - also it 
would be very strange to have a Jenkins project to need Travis to build there 
PRs…
The Repository Connector seem not yet integrated into this env, but I think we 
should aim for this solution. Most probably the only thing missing is the 
“Jenkinsfile”: 
https://github.com/jenkinsci/config-file-provider-plugin/blob/master/Jenkinsfile
 

Here is an example of an other plugin of mine: 
https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fconfig-file-provider-plugin/activity
 

 
In terms of the future… I think the first would be to upgrade the parent pom to 
 org.jenkins-ci.plugins:plugin this would ease a lot of things and should keep 
us up to date with the latest requirements when it comes to plugin maintenance.
Other things:
- pipeline support, I did not have the time to check 
https://github.com/jenkinsci/repository-connector-plugin/pull/21 

- upgrade/replace of aether, aether is no longer an active project and is now 
(as far as I understand) replaced by https://maven.apache.org/resolver/ 


PRs: unfortunate I’m very limited in terms of time right now - but I fully 
trust you and you can move things forward! If you want me to have a look to, 
just mention me in the PR comments (@imod) and I will do my best.
Releases: the same rule as with PRs: I trust you! If you think a release is 
ready, go for it or ask me to do one. The only thing I ask you for here, is 
that you try to update the release notes on the wiki too - as a user, I hate 
releases where I have no idea what changed.

…in general: I trust you and I think that we only can move forward if we both 
do so.

Regards Domi



> On 22 Jan 2018, at 22:19, Jae Gangemi  wrote:
> 
> 
>   would it be possible to get admin access to this repo? i'd like to set up 
> travis to build pull requests but i don't currently have access.
> 
>   i have cc-ed domi here. i tried reaching out to touch base and discuss this 
> last week but i have not heard back and wanted to cover my bases.
> 
>   thanks!!
> 
> 
> On Sun, Jan 14, 2018 at 1:21 PM, Baptiste Mathus  > wrote:
> Thanks for your patience. 
> Just added you as a committer Jae. 
> 
> Obviously you will want to go through PRs for changes, and leave some time to 
> Domi to review it as much as possible.
> 
> When/if you wish to release, you'll need to file a PR against the permissions 
> repo, but that's probably not needed yet at that point. 
> 
> Cheers and welcome!
> 
> 2018-01-10 16:38 GMT+01:00 Jae Gangemi  >:
> 
>   awesome!
> 
>   jenkins: jgangemi (jgangemi at gmail)
>   github: jgangemi
> 
> On Tuesday, January 9, 2018 at 11:39:56 PM UTC-7, domi wrote:
> Hi Jae,
> 
> I’m more then happy if you want to help out with the repository-connector!
> The reason why I did not answer to your first mail is, that my subscription 
> to the jerkins-dev googlegroup does not work anymore - I’m fighting with it 
> since months and have no idea why it does not work…
> /Domi
> 
>> On 10 Jan 2018, at 00:22, Jae Gangemi > wrote:
>> 
>> 
>>   thanks! 
>> 
>>   adding original maintainers (as listed in wiki page) to cc list.
>> 
>> On Tue, Jan 9, 2018 at 2:36 PM, Baptiste Mathus > wrote:
>> Hello!
>> 
>> Thank you for your interest! We've documented the process on this page: 
>> https://wiki.jenkins.io/display/JENKINS/Adopt+a+Plugin 
>> 
>> 
>> To sum up, you want to put them in CC (hint: use git history, there should 
>> be a bunch of emails there in commits) here, and either they answer, or we 
>> have a typical 2 weeks timeout before giving you the necessary permissions 
>> to take over.
>> 
>> Thanks again
>> 
>> 2018-01-08 18:59 GMT+01:00 Jae Gangemi >:
>> i'm trying to reach the maintainers of the repostitory-connector plugin to 
>> see if they are still interested in maintaining it and if not, what steps i 
>> need to do in order to take over and provide support.
>> 
>> thanks!!
>> 
>> --
>> -jae
>> 
>> -- 
>> 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-de...@googlegroups.com <>.
>> To view this discussion on the web visit 
>>

Re: repository-connector plugin maintainence

2018-01-23 Thread domi 

Hey Jae,

I don’t know why my last email did not reach you, but I did answer you a few 
days ago…
Here is a copy:


Hi Jae,

There is no need to enable travis, as every Jenkins Plugin hosted in the 
Jenkins GH Org, we can make use of the Jenkins Project Infrastructure - also it 
would be very strange to have a Jenkins project to need Travis to build there 
PRs…
The Repository Connector seem not yet integrated into this env, but I think we 
should aim for this solution. Most probably the only thing missing is the 
“Jenkinsfile”: 
https://github.com/jenkinsci/config-file-provider-plugin/blob/master/Jenkinsfile
 

Here is an example of an other plugin of mine: 
https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fconfig-file-provider-plugin/activity
 

 
In terms of the future… I think the first would be to upgrade the parent pom to 
 org.jenkins-ci.plugins:plugin this would ease a lot of things and should keep 
us up to date with the latest requirements when it comes to plugin maintenance.
Other things:
- pipeline support, I did not have the time to check 
https://github.com/jenkinsci/repository-connector-plugin/pull/21 

- upgrade/replace of aether, aether is no longer an active project and is now 
(as far as I understand) replaced by https://maven.apache.org/resolver/ 


PRs: unfortunate I’m very limited in terms of time right now - but I fully 
trust you and you can move things forward! If you want me to have a look to, 
just mention me in the PR comments (@imod) and I will do my best.
Releases: the same rule as with PRs: I trust you! If you think a release is 
ready, go for it or ask me to do one. The only thing I ask you for here, is 
that you try to update the release notes on the wiki too - as a user, I hate 
releases where I have no idea what changed.

…in general: I trust you and I think that we only can move forward if we both 
do so.

Regards Domi


> On 23 Jan 2018, at 00:07, Daniel Beck  wrote:
> 
> 
>> On 22. Jan 2018, at 22:19, Jae Gangemi  wrote:
>> 
>>  would it be possible to get admin access to this repo? i'd like to set up 
>> travis to build pull requests but i don't currently have access.
> 
> I changed the accurev-plugin Developers team to admin access.
> 

-- 
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 
https://groups.google.com/d/msgid/jenkinsci-dev/8F25043B-4151-435A-BA45-4B2CD82CE31D%40fortysix.ch.
For more options, visit https://groups.google.com/d/optout.

Re: repository-connector plugin maintainence

2018-01-23 Thread Daniel Beck 

> On 23. Jan 2018, at 00:54, Jae Gangemi  wrote:
> 
>   right - but how is the context that is required indicating the build was 
> successful set?
> 
>   oh wait...is that handled by some special internal magic by whatever plugin 
> is being used to do the builds vs having to call some step/publisher in the 
> Jenkinsfile itself to set the context? 

That's built in to GitHub Branch Source Plugin. Docs here:
https://go.cloudbees.com/docs/cloudbees-documentation/cje-user-guide/index.html#_github_pull_requests

Look at any plugin repo that has a Jenkinsfile and you're going to see plenty 
of commit statuses, linking back to ci.jenkins.io.

-- 
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 
https://groups.google.com/d/msgid/jenkinsci-dev/985D4CEB-71A5-437A-863D-567668C32401%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.