Re: [GSOC 2018] [Student Introduction & query] Simple Pull-Request Job Plugin

[Abhishek Gautam]

Hello Everyone,
@martinda, I have prepared my proposal for the project Simple Pull-Request 
Job Plugin and shared it on the official GSOC website.
The link to the project proposal: 
https://docs.google.com/document/d/1cuC0AvQG3e4GCjIoCwK3J0tcJVAz1eNDKV8d_zXxlO8/edit?usp=sharing

Please let me know if there is something that needs more clarification or 
if I have missed something.

Thank you.

-- 
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/be44fb36-633a-4ef8-ac86-ee9b68abce8e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [GSoC 2018] [Student Introduction] Cloud Features for External Work-space Manager Plugin

[martinda]

Hi,

I should also mention that there are videos that explain how the external 
workspace manager plugin works.
These provide good starting points for understanding from the user point of 
view.

1. Lightning talk (Jenkins World 
2016): https://www.youtube.com/watch?v=mZaCngHQaO4
2. GSoC 2016 final presentations (first presentation is the external 
workspace manager plugin): https://youtu.be/lo8sZJt2WhM?t=404

Martin

On Friday, March 16, 2018 at 10:16:10 PM UTC-4, martinda wrote:
>
> I forgot to mention that we have office hours and all students are invited 
> to participate and ask questions about GSoC.
> See https://jenkins.io/projects/gsoc/#office-hours for the times.
>
> Martin
>
> On Friday, March 16, 2018 at 9:50:28 PM UTC-4, martinda wrote:
>>
>> Hello Vineeth,
>>
>> Thank you for your interest.
>>
>> We have some student information, but it looks like you have already read 
>> it: https://jenkins.io/projects/gsoc/students/
>> If you find something is missing please let us know.
>>
>> If you have already studied the external workspace manager code base and 
>> know the extension points 
>> , 
>> then I recommend familiarizing yourself with cloud based storage, for 
>> example azure, amazon, google, etc. This should help you write your project 
>> proposal.
>>
>> Best Regards,
>> Martin d'Anjou
>>
>> On Friday, March 16, 2018 at 3:18:03 PM UTC-4, Vineeth Reddy wrote:
>>>
>>>
>>> I am a newbie in open source community but i feel i am capable enough to 
>>> understand and give back to community my best. 
>>>
>>> I am interested in working with "CLOUD FEATURES FOR EXTERNAL WORKSPACE 
>>> MANAGER PLUGIN. "
>>>
>>> I spent decent time on understanding project and would like to look into 
>>> it more detail.
>>>
>>> As application closes in 11 days. I am unable to contribute much in 
>>> prior but would like to make it this summer.
>>>
>>> Please guide with through additional info, resources on this project and 
>>> ways to selected for this project and in starting  the contribution right 
>>> away.
>>>
>>>

-- 
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/34c19ab7-b00f-4336-9d11-661b761f5cb4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [GSoC 2018] UPDATE for CODE Coverage API Plugin

[Oleg Nenashev]

Hi Abhishek,

Do you want to demo your project during common office hours?
Or do you want to setup a separate meeting for that?

Thanks in advance,
Oleg

On Thursday, March 15, 2018 at 11:56:46 PM UTC+1, Ullrich Hafner wrote:
>
> Your approach sounds very reasonable. The same approach is used by the 
> xunit plugin (converts different test results to JUnit format) and a 
> similar but slightly different approach is used by the warnings plugin 
> (converts different warning logs to an object model). I think that both of 
> these approaches make sense. With the former one you can reuse the UI 
> completely from the target format. The disadvantage is that there might be 
> some information loss when converting to another format (there is coverage 
> data *and* source code if I remember correctly: everything must be 
> supported by the target). With the latter approach you can define the model 
> on your own. However, you need to write the UI again (or adapt one of the 
> other ones). So I think the simpler solution would be your suggested 
> approach. Here you need to carefully select which of the tools (and which 
> Jenkins plugin) should be the target.
>
> Am 15.03.2018 um 08:41 schrieb Rajgure Abhishek Sanjay Abhishek Sanjay <
> iit20...@iiita.ac.in >:
>
>   
>Various plugins  are available  which currently implement code 
> coverage (jacoco,EclEmma,clover plugin, cobertura plugin, clover php 
> plugin, etc), Instead of having one plugin for each code coverage result 
> it would be best if we could merge them all into one plugin which will 
> handle code coverage.
> my approach
>
>1. develope intermediate converters for each code coverage reporting 
>tool which will convert its result into one format
>2. develope a jenkins plugin which is collection of this converters as 
>well as it has functionality of showing combined result
>
>In Past week i was able to convert jacoco results into cobertura 
>result,
>and converted jacoco files are recognized by cobertura plugin of 
>jenkins so i was able to see combined result of previous cobertura 
>result in addition to this converted result
>
>
> -- 
> 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 
> https://groups.google.com/d/msgid/jenkinsci-dev/cdf3a75a-3a0a-44b1-aa37-b24c64161350%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/850fe72f-5869-4496-adcf-96ccd6ab7839%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [GSOC 2018] EDA Plugin : Developing a Jenkins Plugin for one of the EDA tools viz FuseSOC

[Oleg Nenashev]

Hi Lakhan,

Yes, it would be great to extend Jenkins features for OSS EDA tools you 
mentioned. Regarding your query, it would be great to limit the scope of 
the project to few tools to that you could keep focused when you create a 
project proposal draft. Regarding FuseSoC, we also have active project 
maintainers who may be interested to co-mentor the project. All other tools 
in the list are also feasible.

We are also setting up a GSoC sync-up call between Jenkins and 
LibreCores/FOSSi community members to next week. Currently the slot is TBD, 
please add options possible to you: https://doodle.com/poll/w38ne6qekiyfrb9u

Best regards,
Oleg

On Saturday, March 17, 2018 at 3:15:18 AM UTC+1, martinda wrote:
>
> Hi Lakhan,
>
> Thank you for your interest in the GSoC project on EDA plugin for Jenkins.
>
> There are many things a Jenkins EDA plugin can do. It can run the EDA 
> tool, but that is rather trivial as anyone can shell out and call the tool 
> from the command line. But what get more interesting is interpreting and 
> reporting the results. Think of what is important when interpreting 
> hardware simulations and synthesis results, what users are interested in 
> knowing (simulation pass/fail criteria, log parsing, resource utilization, 
> timing, etc) and that should provide a lot of material for coding the 
> plugin. It is probably better to have one plugin for each EDA tool.
>
> Note that we are also in contact with the librecores community regarding 
> this plugin, so you should definitely join that community too (
> https://gitter.im/librecores/Lobby). A good approach would be to use one 
> of their open source projects and build it with the EDA plugin. Lastly we 
> have office hours (https://jenkins.io/projects/gsoc/#office-hours), all 
> students are invited to participate and ask questions.
>
> Best Regards,
> Martin d'Anjou
>
>
> On Friday, March 16, 2018 at 1:04:02 AM UTC-4, Lakhan Shiva wrote:
>>
>> Hi, 
>>
>> My name is Lakhan Shiva Kamireddy. I am a second year graduate student at 
>> University of Colorado Boulder. I am interested in developing a Jenkins 
>> Plugin for one of the EDA tools viz,
>> FuseSOC, Yosys, icetools, ArachnePnr, etc. It will help to report FPGA 
>> resource utilization per build, etc. 
>>
>> I am a user of Jenkins CI build platform while i was a backend web 
>> application developer for a multinational consulting corporation (Deloitte 
>> Consulting).
>>
>> Last year summer, I was an intern at Google, Sunnyvale office in 
>> Califronia,as a Hardware Engineering intern and developed a Formal 
>> Verification library (SystemVerilog and Perl)
>> which falls under RTL design and Verification domain. I think this would 
>> be a great project and would like to come up with a proposal for this. I 
>> would like to get as much details as possible 
>> for this project and also its potential to get accepted as a GSOC 2018 
>> project for Jenkins.
>>
>> I have pursued some graduate level courses like Logic Synthesis and 
>> Optimization, Computer Aided Verification(Formal Verification) at the 
>> University of Colorado Boulder in the past years. 
>>
>> Kindly contact me, to fuel this project as a potential GSOC 2018 
>> candidate.
>>
>> Thanks and Kind Regards, 
>> Lakhan Shiva Kamireddy
>>
>

-- 
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/044ca004-cf66-49aa-a915-4107a0610058%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [GSOC 2018] [Student Introduction & query] Simple Pull-Request Job Plugin

[Abhishek Gautam]

Hello Jesse,

Thank you for your reply. Can you please provide the link to the thread 
where you have discussed the thing you mentioned.

On Friday, March 16, 2018 at 8:47:02 PM UTC+5:30, Jesse Glick wrote:
>
> On Thu, Mar 15, 2018 at 10:22 PM, martinda  > wrote: 
> > there there is another model which is to have a job that handles all the 
> pull requests of a git repo to a given branch. For example say there is a 
> git repository called jupiter/juno.git (jupiter is the name of the github 
> org or of the bitbucket project). Then the pull requests destined to the 
> master branch of the juno git repository could have a correspondig job 
> called jupiter/juno/master. 
>
> Which is already a standard part of Jenkins 2, including GitHub and 
> Bitbucket support. The only thing distinct from the proposal as it 
> stands is that using the default set of plugins, the jobs are 
> configured from a `Jenkinsfile` whereas you are proposing some YAML 
> format—easily handled by an existing pair of extension points in 
> `workflow-multibranch`. I have discussed this is another thread. 
>

-- 
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/b73501a6-64d3-480a-9b32-a3eb36523dc8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.