Re: GSoC2016

[Ashish Ramtri]

Hi Baptiste,
 
Sorry for the inconvenience caused. Now, I have allowed access for 
commenting.

https://docs.google.com/document/d/1VmW8ECUCNgORLVAc5sZuH6mdwqmWYnm96f7qccnyWdA/edit?usp=sharing

On Thursday, March 24, 2016 at 8:53:18 PM UTC+5:30, Ashish Ramtri wrote:
>
> Sir/Madam,
>
> I am *Ashish Ramtri*, currently in the 3rd year pursuing *B.Tech* in* 
> Information 
> Technology from VIT University, Vellore.*
>
> *Interests:*
>
> Web App Development using Java
> HTML, CSS
> Java Server Pages(JSP)
>
> *Family Background:*
>
> My father is a Businessman and mother is a House-wife. I have an elder 
> brother as well.
>
> *Motivation letter:*
>
> I am a Java Coder and have a deep understanding of the language. I have 
> developed web apps using JSP and deployed them as well.I have also made 
> various other projects using Java. I am also familiar with JavaScript 
> technology.Because Jenkins basically focuses on the Java technology, that 
> is the first reason why I am interested in this project. Secondly, I think 
> my skills can turn out be a great asset for the Project.
> I am interested in improving the *WebUI* so as to make it more 
> interactive and user-friendly as well.
>
> *LinkedIn Profile :*
> https://in.linkedin.com/in/ashish-ramtri-77811588
>
> *Twitter:*
> https://twitter.com/ashish_22jan
>
> *Blog:*
> http://ashish22jan.blogspot.in/
>

-- 
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/c37554a6-b207-4bec-be81-bad219c239aa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: GSoC2016

[Baptiste Mathus]

You seem to have forgotten to open it to anybody for commenting.

2016-03-25 6:42 GMT+01:00 Ashish Ramtri :

> *Project Proposal:*
>
>
> https://docs.google.com/document/d/1VmW8ECUCNgORLVAc5sZuH6mdwqmWYnm96f7qccnyWdA/edit#
>
> On Thursday, March 24, 2016 at 8:53:18 PM UTC+5:30, Ashish Ramtri wrote:
>>
>> Sir/Madam,
>>
>> I am *Ashish Ramtri*, currently in the 3rd year pursuing *B.Tech* in* 
>> Information
>> Technology from VIT University, Vellore.*
>>
>> *Interests:*
>>
>> Web App Development using Java
>> HTML, CSS
>> Java Server Pages(JSP)
>>
>> *Family Background:*
>>
>> My father is a Businessman and mother is a House-wife. I have an elder
>> brother as well.
>>
>> *Motivation letter:*
>>
>> I am a Java Coder and have a deep understanding of the language. I have
>> developed web apps using JSP and deployed them as well.I have also made
>> various other projects using Java. I am also familiar with JavaScript
>> technology.Because Jenkins basically focuses on the Java technology, that
>> is the first reason why I am interested in this project. Secondly, I think
>> my skills can turn out be a great asset for the Project.
>> I am interested in improving the *WebUI* so as to make it more
>> interactive and user-friendly as well.
>>
>> *LinkedIn Profile :*
>> https://in.linkedin.com/in/ashish-ramtri-77811588
>>
>> *Twitter:*
>> https://twitter.com/ashish_22jan
>>
>> *Blog:*
>> http://ashish22jan.blogspot.in/
>>
> --
> 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/8ea6251a-05b2-43e3-a908-4c95edf35379%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/CANWgJS7m3UX1qw0778B4oOB0BsEO2id01NQQH85CEm%3DdDg_y3Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: GSoC2016

[Ashish Ramtri]

*Project Proposal:*

https://docs.google.com/document/d/1VmW8ECUCNgORLVAc5sZuH6mdwqmWYnm96f7qccnyWdA/edit#

On Thursday, March 24, 2016 at 8:53:18 PM UTC+5:30, Ashish Ramtri wrote:
>
> Sir/Madam,
>
> I am *Ashish Ramtri*, currently in the 3rd year pursuing *B.Tech* in* 
> Information 
> Technology from VIT University, Vellore.*
>
> *Interests:*
>
> Web App Development using Java
> HTML, CSS
> Java Server Pages(JSP)
>
> *Family Background:*
>
> My father is a Businessman and mother is a House-wife. I have an elder 
> brother as well.
>
> *Motivation letter:*
>
> I am a Java Coder and have a deep understanding of the language. I have 
> developed web apps using JSP and deployed them as well.I have also made 
> various other projects using Java. I am also familiar with JavaScript 
> technology.Because Jenkins basically focuses on the Java technology, that 
> is the first reason why I am interested in this project. Secondly, I think 
> my skills can turn out be a great asset for the Project.
> I am interested in improving the *WebUI* so as to make it more 
> interactive and user-friendly as well.
>
> *LinkedIn Profile :*
> https://in.linkedin.com/in/ashish-ramtri-77811588
>
> *Twitter:*
> https://twitter.com/ashish_22jan
>
> *Blog:*
> http://ashish22jan.blogspot.in/
>

-- 
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/8ea6251a-05b2-43e3-a908-4c95edf35379%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins Maven repository server supports multiple upstream projects?

[Hez]

I'm sorry, I realized that I should have post this question to users group.

Please ignore this.



On Friday, March 25, 2016 at 11:51:17 AM UTC+8, Hez wrote:
>
> Hi
>
> It looks like the Maven repository server only allow us to configure one 
> upstream project.
>
> Imagine that I have a project C, which has dependency to project A and B.
>
> How can configure the Maven repository server to take the last successful 
> build from project A and B?
>
>

-- 
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/d0006703-53eb-4aa3-88c2-c2bf70dcaa7a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Jenkins Maven repository server supports multiple upstream projects?

[Hez]

Hi

It looks like the Maven repository server only allow us to configure one 
upstream project.

Imagine that I have a project C, which has dependency to project A and B.

How can configure the Maven repository server to take the last successful 
build from project A and B?

-- 
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/3c2b4640-584a-4cad-9717-c23187d09199%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [GSOC 2016]External Workspace Manager

[Johnson Li]

Thanks for your remind, I have completed the process

Best regards,
Johnson

On Fri, Mar 25, 2016 at 6:34 AM, martinda < martin.danjo...@gmail.com 
[martin.danjo...@gmail.com] > wrote:
Johnson,

Please submit your final proposal as per the Google process. Google has a firm 
deadline, and I was told that their site can be slow to respond as the deadline 
approaches.

Thanks,
Martin

On Tuesday, March 22, 2016 at 8:40:44 AM UTC-4, Johnson Li wrote: Sorry about 
that, I have changed the permission

On Tuesday, March 22, 2016 at 8:36:04 PM UTC+8, Oleg Nenashev wrote: I have no 
permission to make comments in the document :(
Could you adjust permissions to let every interested person to comment there?

вторник, 22 марта 2016 г., 13:24:34 UTC+1 пользователь martinda написал: Thank 
you for drafting a proposal. You also need to enter your application directly 
with Google and answer the student application template questions.
The link is: https://summerofcode.withgoogle.com/ 
[https://summerofcode.withgoogle.com/]

Best Regards,
Martin

On Tuesday, March 22, 2016 at 4:56:01 AM UTC-4, Johnson Li wrote: My proposal 
drift is posted here 
[https://docs.google.com/document/d/1YplUAGfS6bIwcl8RjHxfT5Rf-uwGY1ByAyZzOmoMijA/edit?usp=sharing]
 , please give me your advice to help me improve my work.



--
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/N_DHZqCH71M/unsubscribe 
[https://groups.google.com/d/topic/jenkinsci-dev/N_DHZqCH71M/unsubscribe] .
To unsubscribe from this group and all its topics, send an email to 
jenkinsci-dev+unsubscr...@googlegroups.com 
[jenkinsci-dev+unsubscr...@googlegroups.com] .
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/e69f6c53-9977-4041-b5a7-66f045feb2b7%40googlegroups.com
 
[https://groups.google.com/d/msgid/jenkinsci-dev/e69f6c53-9977-4041-b5a7-66f045feb2b7%40googlegroups.com?utm_medium=email_source=footer]
 .
For more options, visit https://groups.google.com/d/optout 
[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/1458867103430-d4ae5271-f0755a7e-fef5c815%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [GSoC2016] External Workspace Manager plugin development

[somai . alexandru]

I have uploaded my final proposal version.

Thank you all for your support and good advices!

Kind Regards,
Alex

On Friday, March 25, 2016 at 12:54:11 AM UTC+2, martinda wrote:
>
> Alex,
>
> Forgot to CC you. Please submit your final proposal as per the Google 
> process. Google has a firm deadline, and I was told that their site can be 
> slow to respond as the deadline approaches.
>
> Best Regards,
> Martin d'Anjou
>
> On Thursday, March 24, 2016 at 6:32:22 PM UTC-4, martinda wrote:
>>
>> Alex,
>>
>> Please submit your final proposal as per the Google process. Google has a 
>> firm deadline, and I was told that their site can be slow to respond as the 
>> deadline approaches.
>>
>> Thanks,
>> Martin
>>
>> On Thursday, March 24, 2016 at 3:32:02 AM UTC-4, somai.a...@gmail.com 
>> wrote:
>>>
>>> Oleg, Martin,
>>>
>>> Can you please have one final look over my project proposal 
>>> 
>>>  
>>> before I will submit it?
>>>
>>> Thank you,
>>> Alex
>>>
>>> On Monday, March 21, 2016 at 5:01:31 PM UTC+2, martinda wrote:

 Hello Alex,

 On Sunday, March 20, 2016 at 6:09:38 PM UTC-4, somai.a...@gmail.com 
 wrote:
>
>
> Related to the unit testing examples, the sooner you share them the 
> better. I can look over them early to get accustomed to.
>
>
 Basic test example:

 https://github.com/martinda/workflow-migration-demo/blob/master/src/test/java/org/jenkins/plugins/demo/Demo1Test.java

 The most recent way of writing the pom.xml that I use is in this 
 project (also incudes some basic test examples - roundtrip and global 
 config access from plugin test):

 https://github.com/martinda/jenkins-plugin-globalconfig-demo1/blob/master/src/test/java/org/jenkins/plugins/demo/Demo1Test.java

 More elaborate test examples:

 https://github.com/martinda/http-request-plugin/tree/feature/workflow-integration/src/test/java/jenkins/plugins/http_request

 Martin

>>>

-- 
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/0f2ab240-f984-4925-aa01-523ad1baa47e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[GSoC2016] Support core plugin improvements

[Ігор Яценко]

Hi all,

I am 5rd year undergraduate student in Software Engineering of Kharkiv 
University of Radio Electronics, Ukraine.
I have 2+ years experience in Java programming and software engineering.

I have worked with Jenkins on a few projects, and I think it's "must have" 
tool for any team.
I like Jenkins, because it's very simple but also very power, and with 
additional plugins I can build project ecosystem around git+jenkins.

I am really want to participate in GSOC 2016 and really interested in above 
projects,

I know, I writing it, so late, but I hope "to catch the last train out of 
town":) 

Please, give me advice about proposal. What should I add?


My Linkedin page: https://ua.linkedin.com/in/ihor-yatsenko-31709267
Thanks. Ihor

-- 
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/95d77f9b-70cb-4e0e-995c-45a74d31a332%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [GSoC2016] External Workspace Manager plugin development

[martinda]

Alex,

Forgot to CC you. Please submit your final proposal as per the Google 
process. Google has a firm deadline, and I was told that their site can be 
slow to respond as the deadline approaches.

Best Regards,
Martin d'Anjou

On Thursday, March 24, 2016 at 6:32:22 PM UTC-4, martinda wrote:
>
> Alex,
>
> Please submit your final proposal as per the Google process. Google has a 
> firm deadline, and I was told that their site can be slow to respond as the 
> deadline approaches.
>
> Thanks,
> Martin
>
> On Thursday, March 24, 2016 at 3:32:02 AM UTC-4, somai.a...@gmail.com 
> wrote:
>>
>> Oleg, Martin,
>>
>> Can you please have one final look over my project proposal 
>> 
>>  
>> before I will submit it?
>>
>> Thank you,
>> Alex
>>
>> On Monday, March 21, 2016 at 5:01:31 PM UTC+2, martinda wrote:
>>>
>>> Hello Alex,
>>>
>>> On Sunday, March 20, 2016 at 6:09:38 PM UTC-4, somai.a...@gmail.com 
>>> wrote:


 Related to the unit testing examples, the sooner you share them the 
 better. I can look over them early to get accustomed to.


>>> Basic test example:
>>>
>>> https://github.com/martinda/workflow-migration-demo/blob/master/src/test/java/org/jenkins/plugins/demo/Demo1Test.java
>>>
>>> The most recent way of writing the pom.xml that I use is in this project 
>>> (also incudes some basic test examples - roundtrip and global config access 
>>> from plugin test):
>>>
>>> https://github.com/martinda/jenkins-plugin-globalconfig-demo1/blob/master/src/test/java/org/jenkins/plugins/demo/Demo1Test.java
>>>
>>> More elaborate test examples:
>>>
>>> https://github.com/martinda/http-request-plugin/tree/feature/workflow-integration/src/test/java/jenkins/plugins/http_request
>>>
>>> Martin
>>>
>>

-- 
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/65a1db8a-b233-491d-b8c6-592874fdb084%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [GSOC 2016]External Workspace Manager

[martinda]

Johnson,

Please submit your final proposal as per the Google process. Google has a 
firm deadline, and I was told that their site can be slow to respond as the 
deadline approaches.

Thanks,
Martin

On Tuesday, March 22, 2016 at 8:40:44 AM UTC-4, Johnson Li wrote:
>
> Sorry about that, I have changed the permission
>
> On Tuesday, March 22, 2016 at 8:36:04 PM UTC+8, Oleg Nenashev wrote:
>>
>> I have no permission to make comments in the document :(
>> Could you adjust permissions to let every interested person to comment 
>> there?
>>
>> вторник, 22 марта 2016 г., 13:24:34 UTC+1 пользователь martinda написал:
>>>
>>> Thank you for drafting a proposal. You also need to enter your 
>>> application directly with Google and answer the student application 
>>> template questions.
>>> The link is: https://summerofcode.withgoogle.com/
>>>
>>> Best Regards,
>>> Martin
>>>
>>> On Tuesday, March 22, 2016 at 4:56:01 AM UTC-4, Johnson Li wrote:

 My proposal drift is posted here 
 ,
  
 please give me your advice to help me improve my work.



-- 
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/e69f6c53-9977-4041-b5a7-66f045feb2b7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [GSoC2016] External Workspace Manager plugin development

[martinda]

Alex,

Please submit your final proposal as per the Google process. Google has a 
firm deadline, and I was told that their site can be slow to respond as the 
deadline approaches.

Thanks,
Martin

On Thursday, March 24, 2016 at 3:32:02 AM UTC-4, somai.a...@gmail.com wrote:
>
> Oleg, Martin,
>
> Can you please have one final look over my project proposal 
> 
>  
> before I will submit it?
>
> Thank you,
> Alex
>
> On Monday, March 21, 2016 at 5:01:31 PM UTC+2, martinda wrote:
>>
>> Hello Alex,
>>
>> On Sunday, March 20, 2016 at 6:09:38 PM UTC-4, somai.a...@gmail.com 
>> wrote:
>>>
>>>
>>> Related to the unit testing examples, the sooner you share them the 
>>> better. I can look over them early to get accustomed to.
>>>
>>>
>> Basic test example:
>>
>> https://github.com/martinda/workflow-migration-demo/blob/master/src/test/java/org/jenkins/plugins/demo/Demo1Test.java
>>
>> The most recent way of writing the pom.xml that I use is in this project 
>> (also incudes some basic test examples - roundtrip and global config access 
>> from plugin test):
>>
>> https://github.com/martinda/jenkins-plugin-globalconfig-demo1/blob/master/src/test/java/org/jenkins/plugins/demo/Demo1Test.java
>>
>> More elaborate test examples:
>>
>> https://github.com/martinda/http-request-plugin/tree/feature/workflow-integration/src/test/java/jenkins/plugins/http_request
>>
>> Martin
>>
>

-- 
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/55f8eef7-4515-47e4-9fea-15d1ed6f7679%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: GSoC2016

[Oleg Nenashev]

It is possible to get project ideas from the previous discussions in 
mailing lists.
Of course, it's highly recommended to try Jenkins and to propose some 
personal ideas, but I doubt you can do it in time. We are also do not plan 
new Office hours with mentors before the deadline.

Maybe Michael would help since he has a good TZ overlap

четверг, 24 марта 2016 г., 20:56:34 UTC+1 пользователь Baptiste Mathus 
написал:
>
> Welcome Ashish,
>
> Though it's not *too* late yet, beware that the deadline is in less than 
> 24 hours (25 March 19:00 UTC). (see 
> https://developers.google.com/open-source/gsoc/timeline)
>
> If you wish to go forward, you still have to write a proposal, and submit 
> it on the GSoC website before that deadline.
>
> If you post your proposal here, we may be able to review it, though 
> there's less and less guaranty for that since time is running out.
>
>
> Cheers!
>
> 2016-03-24 16:23 GMT+01:00 Ashish Ramtri 
> :
>
>> Sir/Madam,
>>
>> I am *Ashish Ramtri*, currently in the 3rd year pursuing *B.Tech* in* 
>> Information 
>> Technology from VIT University, Vellore.*
>>
>> *Interests:*
>>
>> Web App Development using Java
>> HTML, CSS
>> Java Server Pages(JSP)
>>
>> *Family Background:*
>>
>> My father is a Businessman and mother is a House-wife. I have an elder 
>> brother as well.
>>
>> *Motivation letter:*
>>
>> I am a Java Coder and have a deep understanding of the language. I have 
>> developed web apps using JSP and deployed them as well.I have also made 
>> various other projects using Java. I am also familiar with JavaScript 
>> technology.Because Jenkins basically focuses on the Java technology, that 
>> is the first reason why I am interested in this project. Secondly, I think 
>> my skills can turn out be a great asset for the Project.
>> I am interested in improving the *WebUI* so as to make it more 
>> interactive and user-friendly as well.
>>
>> *LinkedIn Profile :*
>> https://in.linkedin.com/in/ashish-ramtri-77811588
>>
>> *Twitter:*
>> https://twitter.com/ashish_22jan
>>
>> *Blog:*
>> http://ashish22jan.blogspot.in/
>>
>> -- 
>> 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/CAKzVO0VOxkfKCjeEh4AAeXWf9dmTG_Gsciqp8H-PvoXCbSzCLg%40mail.gmail.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/5fe59fd2-ee66-44c5-a3fb-02ac85f359f8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: custom-tools plugin: adding support for 7z-files

[Oleg Nenashev]

>
> If this 7zip-installer is added to ExtraToolInstallers, where in custom 
> tools plugin do you think I should call the 7zip-installer? 
>

In the case of ToolInstaller you don't need to modify Custom Tools at all.
When Custom Tool plugin requests a tool home directory, all the 
installation happens automagically. It happens here 

.

BR, Oleg

четверг, 24 марта 2016 г., 14:24:03 UTC+1 пользователь Vincent Daburon 
написал:
>
> Hi,
> In the javadoc, you could see :
>
> https://commons.apache.org/proper/commons-compress/apidocs/index.html?org/apache/commons/compress/archivers/sevenz/package-tree.html
>
> "The format is very Windows/Intel specific, so it uses little-endian byte 
> order, doesn't store user/group or permission bits, and represents times 
> using NTFS timestamps (100 nanosecond units since 1 January 1601). Hence 
> the official tools *recommend against using it for backup purposes on 
> *nix*, and recommend .tar.7z or .tar.lzma or .tar.xz instead."
>
> Not sure, it will be a good feature for *nix OS.
>
> Regards.
> Vincent D.
>
> On Thursday, March 24, 2016 at 1:30:06 PM UTC+1, Martin Hjelmqvist wrote:
>>
>> I have code for a simple 7z-extractor using Apache's SevenZ classes, but 
>> 7-Zip-JBinding might be better to use instead.
>> I'll have a closer look at it later. Thanks for the tip. :)
>>
>> Den torsdag 24 mars 2016 kl. 13:12:12 UTC+1 skrev Boris Brodski:
>>>
>>> Sorry for interfering. Can 7-Zip-JBinding be helpful in some way here?
>>>
>>> http://sevenzipjbind.sourceforge.net/
>>>
>>

-- 
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/d13de68d-6cc0-4f6c-8178-831cc7a4be28%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: GSoC2016

[Baptiste Mathus]

Welcome Ashish,

Though it's not *too* late yet, beware that the deadline is in less than 24
hours (25 March 19:00 UTC). (see
https://developers.google.com/open-source/gsoc/timeline)

If you wish to go forward, you still have to write a proposal, and submit
it on the GSoC website before that deadline.

If you post your proposal here, we may be able to review it, though there's
less and less guaranty for that since time is running out.


Cheers!

2016-03-24 16:23 GMT+01:00 Ashish Ramtri :

> Sir/Madam,
>
> I am *Ashish Ramtri*, currently in the 3rd year pursuing *B.Tech* in* 
> Information
> Technology from VIT University, Vellore.*
>
> *Interests:*
>
> Web App Development using Java
> HTML, CSS
> Java Server Pages(JSP)
>
> *Family Background:*
>
> My father is a Businessman and mother is a House-wife. I have an elder
> brother as well.
>
> *Motivation letter:*
>
> I am a Java Coder and have a deep understanding of the language. I have
> developed web apps using JSP and deployed them as well.I have also made
> various other projects using Java. I am also familiar with JavaScript
> technology.Because Jenkins basically focuses on the Java technology, that
> is the first reason why I am interested in this project. Secondly, I think
> my skills can turn out be a great asset for the Project.
> I am interested in improving the *WebUI* so as to make it more
> interactive and user-friendly as well.
>
> *LinkedIn Profile :*
> https://in.linkedin.com/in/ashish-ramtri-77811588
>
> *Twitter:*
> https://twitter.com/ashish_22jan
>
> *Blog:*
> http://ashish22jan.blogspot.in/
>
> --
> 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/CAKzVO0VOxkfKCjeEh4AAeXWf9dmTG_Gsciqp8H-PvoXCbSzCLg%40mail.gmail.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/CANWgJS5%3Dv3zGkYDsJYUdP1fRzkWZ_eWqa%3D-TWYnt8J2tterwPw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Best Practice for Resolving User Supplied Build Parameters Used in Plugin Textboxes

[Jimmy Ray]

So, I am writing a build step plugin that has several textbox fields for 
configuration.  I need to let users create entries in these textbox fields 
that come from build parameters when this plugin is used in a Parameterized 
Build.  So, I would have jobs configured with ${...} values embedded in the 
textbox field strings.  What is the best practice for accessing/parsing 
these build parameters from within the perform() method of my plugin?  For 
example, I can access the build parameters via 
the build.getBuildVariableResolver().resolve(...) method.  Is that the best 
way?  Should I parse the string from between the ${...} braces, or are 
there helpers or extension points that are already built for this purpose?

-Jimmy

-- 
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/996c6e04-896a-4aa3-bb76-ed96137bfba6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Meet jenkins.io

[Thomas Fürer]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

+1

really cool

tom

Am 24.03.2016 um 07:02 schrieb R. Tyler Croy:
> I finished up the final work for migration from https://jenkins-ci.org
 to
> https://jenkins.io today. The final step of the switchover was to redi
rect
> non-mapped URLs from jenkins-ci.org over to jenkins.io.
> 
> 
> This project has been a tremendous amount of work with Gus Reiber, Bap
tiste
> Mathaus, James Dumay, Daniel Beck, Oleg Nenashev  and a number of othe
r
> contributors filling in the new website with CSS, Haml, and most impor
tantly
> AsciiDoc (for documentation!)
> 
> 
> Some of the features of jenkins.io that are important to me, I'd like 
to share:
> 
>  * Visual priority given to the LTS release line (yay)
>  * Built-in support for three layers of documentation: solution pages,
 getting
>started guides and the "handbook".
>  * Visual elements to highlight upcoming events
>  * Certificates automated via letsencrypt.org (this is my favorite ;))
> 
> The site is statically generated and contributions are welcome here:
> 
> 
> 
> As I mentioned in our last project meeting, migration of other propert
ies such
> as wiki.jenkins-ci.org to the jenkins.io domain will take a bit more t
ime. This
> is an important first step however!
> 
> 
> 
> Cheers
> - R. Tyler Croy
> 
> --
>  Code: 
>   Chatter: 
> 
>   % gpg --keyserver keys.gnupg.net --recv-key 3F51E16F
> --
> 
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJW9C8cAAoJEMcwZAIehXs1l1IP/1jN8RFnHPUcGSjKtkDjdgl3
wy0LnvO15LR0LdMTmHNynMxuRX3kd3ngOhAHD8WL/gxAI6+3N7OkpOVU0Gl97Jkn
oWmCDV/OaUOUZMgtXfngmaS80lBqGqcan0M/77GzuIuBmdBRBJaF7WVPApXydZSp
Jt1MW8queIHnC3i27L7brjvdAw8SW+r4u92m57ghjyJnmWCUMde3TycDPolMCvZ4
spFYNIJhBCgcw1rRDy2FFh11Y6kcPlvEM5ZixgIHG3SlRh+3s1OmVXfVP8Em681B
oTlGen8QcWe4j6rQts0ExEOYg1K/hyIDECXmrkSIum5RpDxU3wvmgilOt2pJ7b2/
pA6GjhYGMbpSj1/cmK4KP8LC4HvjYnnXLu8pIUx7Qowa5BgkN76GeGHWzRE7+PhN
EkhquUe0zis1qvmUjbjONi76iRCrqQo06oW2LOrV79ly0+9P2LZwd9oAJ5g6X2Gc
0c4682v9Vs6Wa3afgFcxaf4/KUsHr7+3mFtvWLI4mfe86Jkg1N40RpHEjgsUqtUO
CKdaQ/JU7GFlNsgRE20flMyrlBYgT3xqbXfVnnNh+nDWKdeTzedzd3rXUkfgy8Bk
iEO3GbVA+r3GdqxJuBJJYaUzgdwxcRqUhenAL67+Qlw22A2pQKOJeEbxA8LMo6l7
avLLaGPi7PwOJCeBZApL
=zBwG
-END PGP SIGNATURE-

-- 
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/56F42F22.2080802%40googlemail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [GSOC 2016] Support core plugin improvements

[Minudika Malshan]

Hi all,

I submitted my final proposal to google. Thanks a lot for your guidance and
support.
Hopefully looking forward to work on this project.

Thanks again.
Best  regards

On Thu, Mar 24, 2016 at 8:23 PM, Oleg Nenashev 
wrote:

> IMHO it's ready to go.
> Thanks for polishing it!
>
> четверг, 24 марта 2016 г., 8:18:48 UTC+1 пользователь Arnaud Héritier
> написал:
>>
>> Perfect. Thanks a lot.
>>
>>
>> Le jeudi 24 mars 2016, Minudika Malshan  a écrit :
>>
>>> Hi all,
>>>
>>> Thanks a lot for your feedback.
>>> @Arnaud : Yes I followed those guide lines when creating my proposal.
>>>
>>> I will go through the whole proposal one more time, finalize it and
>>> submit the final proposal by tonight.
>>>
>>> Best Regards
>>>
>>> On Thu, Mar 24, 2016 at 12:12 PM, Arnaud Héritier 
>>> wrote:
>>>
 Minudika

 For me it seems that your proposal is conform to
 http://write.flossmanuals.net/gsocstudentguide/writing-a-proposal/

 I think you are ready to submit it

 On Thu, Mar 24, 2016 at 4:35 AM, Steve Christou 
 wrote:

> Hello Minudika,
>
> I like the proposal! I have no more feedback from my side.
>
> Thanks,
> Steve.
>
> On Wed, Mar 23, 2016 at 6:03 PM Arnaud Héritier 
> wrote:
>
>> Hi Minudika
>>
>>   I have no more feedbacks on my side. I let the others challenge the
>> proposal (especially Steven who is an active maintainer of the plugin).
>>
>> Thanks guys
>>
>> On Wed, Mar 23, 2016 at 9:07 PM, Steve Christou <
>> schristo...@gmail.com> wrote:
>>
>>> Hello Minudika,
>>>
>>> Thank you for creating this proposal document! I will be reading
>>> over this tonight and providing my comments.
>>>
>>> On Wed, Mar 23, 2016 at 2:59 PM Minudika Malshan <
>>> minudika...@gmail.com> wrote:
>>>
 Thanks a lot for  your kind help.. :)

 BR

 On Thu, Mar 24, 2016 at 12:09 AM, Oleg Nenashev <
 o.v.nenas...@gmail.com> wrote:

> I'll try to take a look before the office hours today.
> Arnaud is busy with BreizhCamp, but maybe we will get Steve online.
>
> BR, Oleg
>
> 2016-03-23 17:59 GMT+01:00 Minudika Malshan  >:
>
>> Hi all,
>>
>> Sorry for spamming. Since the time is running fast I am in a bit
>> of hurry. Could you please let me know if there's any more changes 
>> to be
>> made on my proposal.
>> Then I can make them and submit the finalized proposal to google.
>>
>> Thanks and  regards.
>>
>> On Tue, Mar 22, 2016 at 7:05 PM, Minudika Malshan <
>> minudika...@gmail.com> wrote:
>>
>>> Hi,
>>>
>>> Thanks a lot Oleg and Arnaud for your valuable comments.
>>> I made changes according to your comments. Please have a look
>>> and let me know if there's anything more to be improved or changed.
>>>
>>> Best regards
>>>
>>> On Tue, Mar 22, 2016 at 1:34 PM, Oleg Nenashev <
>>> o.v.nenas...@gmail.com> wrote:
>>>
 The proposal look good, thanks for preparing it!
 I've added several comments to it

 вторник, 22 марта 2016 г., 0:24:25 UTC+1 пользователь Arnaud
 Héritier написал:
>
> Thanks a lot Minudika.
>
> @all please have a look at it and review/comment
>
> cheers
>
> On Tue, Mar 22, 2016 at 12:22 AM, Minudika Malshan <
> minud...@gmail.com> wrote:
>
> Hi all,
>
> Here is the first draft of my proposal [1] . I submitted it
> also to the google's site.
> Please review it and let me know if there's any possible
> improvements to be made on it.
>
> [1]
> https://docs.google.com/document/d/1052sUGFxcDfUHNZFNeQ1FAR61ZB4tJb-GxdW1L3FSC8/edit?usp=sharing
>
> Your comments would be much appreciated.
>
> Thanks a lot.
>
> On Tue, Mar 22, 2016 at 4:05 AM, Arnaud Héritier <
> aher...@gmail.com> wrote:
>
> Really good job Minudika.
> For now I don't see anything to improve.
> I let you officially share it on the dev mailing list to have
> more feedbacks.
> thanks again for the hard work
>
> On Mon, Mar 21, 2016 at 11:01 PM, Minudika Malshan <
> minud...@gmail.com> wrote:
>
> Hi Arnaud,
>
> I created a proposal [1] and published as a draft in 

Re: Git branch handling leading up to 2.0 release and the end of the Jenkins 1.x line

[Daniel Beck]

On 24.03.2016, at 16:32, James Nord  wrote:

> So where do fixes to the 2.0 go?

If they are intended to make it into 2.0, the '2.0' branch. If they are 
intended for 2.1, 'master' from next Wednesday on. (Or maybe build on top of 
2.0, file against master now, and link to the 'real' diff without all of 2.0 in 
the PR description.)

> I'm not sure why this is being treated differently from an LTS - which I 
> would guess 2.0 would be - otherwise why does it need stabilization - it's 
> similar yet different...  If it's not a LTS version (as the next LTS version 
> has been choses and it wasn' t 2.0 why is this extra needed - how is this 
> different from weeklies?)

Because there's a whole bunch of unusually large changes and a lot of attention 
on the final version. So I'd prefer we don't mess this up.

>  Is this a new process going forward

No. We're going back to regular weeklies after the 2.0 release. (And I really 
hope this is the last release like this for a long time, another 11 years would 
be fine with me.)

It will also not disrupt the LTS schedule: We're scheduled to choose a baseline 
in July. It is very likely to be a 2.x, but that's just because by then the 
releases of the previous ~10 weeks will have been 2.x.

> IIRC it was also stated that there was going to be a code review of 2.0 
> before - I guess this is the initial merge 2.0 branch to master - is that no 
> longer planned/ being swept under the carpet?

I don't see how this is remotely practical given the scope of changes that went 
into the 2.0 branch. So if you held off reviewing things and filing issues 
until now, please do so now.

> - otherwise I would have probably been a lot more diligent / rigorous on code 
> reviewing all the changes going in.

There are some known issues with some of the changes in the 2.0 branch that 
need to be fixed before 2.0 RC. Those have been filed in Jira. But other than 
that, everyone had plenty of time to comment on the the PRs.

-- 
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/66F876F7-AAB0-4015-A34E-07903D3409C2%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

GSoC2016

[Ashish Ramtri]

Sir/Madam,

I am *Ashish Ramtri*, currently in the 3rd year pursuing *B.Tech* in*
Information
Technology from VIT University, Vellore.*

*Interests:*

Web App Development using Java
HTML, CSS
Java Server Pages(JSP)

*Family Background:*

My father is a Businessman and mother is a House-wife. I have an elder
brother as well.

*Motivation letter:*

I am a Java Coder and have a deep understanding of the language. I have
developed web apps using JSP and deployed them as well.I have also made
various other projects using Java. I am also familiar with JavaScript
technology.Because Jenkins basically focuses on the Java technology, that
is the first reason why I am interested in this project. Secondly, I think
my skills can turn out be a great asset for the Project.
I am interested in improving the *WebUI* so as to make it more interactive
and user-friendly as well.

*LinkedIn Profile :*
https://in.linkedin.com/in/ashish-ramtri-77811588

*Twitter:*
https://twitter.com/ashish_22jan

*Blog:*
http://ashish22jan.blogspot.in/

-- 
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/CAKzVO0VOxkfKCjeEh4AAeXWf9dmTG_Gsciqp8H-PvoXCbSzCLg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: test failures

[James Nord]

This is the tests failing not maven and the amount of memory they are given 
is different to MAVEN_OPTS.

2.0 branch has some leaks somewhere that need to be fixed :(

Until the leak is found try tweaking this line 

 and 
adding -Xmx1256

/James

On Tuesday, March 22, 2016 at 7:02:09 AM UTC, Michael Neale wrote:
>
> Error: 
>
> Caused by: java.lang.OutOfMemoryError: Java heap space
>
>
> If you give maven more memory, or, use Java 8 to build (resultant code will 
> run with java7 I believe, but building with java8 can be faster and usually 
> less memory hassles)
>
>
> export MAVEN_OPTS ="-Xmx2048m"
>
>
> or something like that to give it enough space. Or perhaps your machine 
> doesn't have enough room to build it? 
>
>
> On Tuesday, March 22, 2016 at 5:43:38 PM UTC+11, Arshad Khan wrote:
>>
>> Hello,
>>
>> I am getting some errors while running tests on jenkins ver 2.0 alpha-3. 
>> I have attached the log. Please help!
>>
>> Best Regards,
>> Arshad
>>
>

-- 
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/a0dd0c7b-9a77-4d9b-a087-061fefeaa708%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Git branch handling leading up to 2.0 release and the end of the Jenkins 1.x line

[James Nord]

So where do fixes to the 2.0 go?  Master and cherry-picked or 2.0 and 
merged down.

I'm not sure why this is being treated differently from an LTS - which I 
would guess 2.0 would be - otherwise why does it need stabilization - it's 
similar yet different...  If it's not a LTS version (as the next LTS 
version has been choses and it wasn' t 2.0 why is this extra needed - how 
is this different from weeklies?)  Is this a new process going forward etc 
etc...

IIRC it was also stated that there was going to be a code review of 2.0 
before - I guess this is the initial merge 2.0 branch to master - is that 
no longer planned/ being swept under the carpet? - otherwise I would have 
probably been a lot more diligent / rigorous on code reviewing all the 
changes going in.


On Wednesday, March 23, 2016 at 10:07:49 PM UTC, Daniel Beck wrote:
>
> Hi everyone, 
>
> The following is my current plan and proposal how to handle the '2.0' and 
> 'master' branches leading up to 2.0 release. Please respond if I overlooked 
> something. You can find the current 2.0 release schedule here: 
>
>
> https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+2.0#Jenkins2.0-RoughTimeline
>  
> 
>  
>
>
> March 23: 
> We're aiming for the 2.0 beta release from the '2.0' branch later today. 
> 'master' has been merged into '2.0' earlier today. 
>
> --- 
>
> March 27(ish): Release of Jenkins 1.655 from 'master'. This will be the 
> last release of the 1.x line (see March 30). 
>
> --- 
>
> March 30: 
> In one week, 'master' will again be merged into '2.0'. This will be 
> released as 2.0 RC from the '2.0' branch. Ideally we're not going to merge 
> crazy stuff into 'master' between now and next Wednesday to keep the risk 
> of the 2.0 RC being terrible low. 
>
> Any unmerged pull requests against '2.0' will be closed, and '2.0' will be 
> merged into 'master'. This means that from that point on, anything 
> happening on the 'master' branch will be released as 2.1, as it makes no 
> sense to continue releasing 1.x weeklies while 2.0 code is frozen and we're 
> preparing the release. 
>
> Pull requests targeting 2.1 and beyond should be opened against 'master'. 
>
> --- 
>
> April 3: 
> This weekly release will be skipped. 
>
> --- 
>
> April 6: 
> Release 2.0 from the '2.0' branch (unless a critical bug is found in RC, 
> of course). Merge '2.0' into 'master'. 
>
> --- 
>
> April 10(ish): 
> Release 2.1 from the 'master' branch. 
>
>
>

-- 
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/6dad6d41-f182-4ddb-8a54-1ca5054dddfa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Meet jenkins.io

[Alyssa Tong]

Well done! Congrats to all involved! jenkins.io looks AWESOME!! 珞珞

On Thu, Mar 24, 2016 at 6:30 AM, Tom Fennelly 
wrote:

> Really nice. Thanks guys!!
>
> On Thursday, March 24, 2016 at 12:58:35 PM UTC, Manuel Recena Soto wrote:
>>
>> CONGRATULATIONS!
>>
>> 2016-03-24 11:38 GMT+01:00 Krishna Gundala :
>>
>>> Excellent Work.. Kudos folks...
>>> You rock Tyler..
>>> Very Nice Website..
>>>
>>> ---
>>>
>>>
>>> Mohan Krishna Gundala
>>> [image: https://]about.me/gmk.india
>>>
>>> 
>>>
>>>
>>>
>>> On Thu, Mar 24, 2016 at 2:31 PM, Baptiste Mathus 
>>> wrote:
>>>
 +1, congrats to everyone involved, and especially thanks to you Tyler.
 Really nice website.

 2016-03-24 6:23 GMT+00:00 domi :

> Really nice work!!!
> /Domi
>
> > On 24 Mar 2016, at 07:02, R. Tyler Croy  wrote:
> >
> > I finished up the final work for migration from
> https://jenkins-ci.org to
> > https://jenkins.io today. The final step of the switchover was to
> redirect
> > non-mapped URLs from jenkins-ci.org over to jenkins.io.
> >
> >
> > This project has been a tremendous amount of work with Gus Reiber,
> Baptiste
> > Mathaus, James Dumay, Daniel Beck, Oleg Nenashev  and a number of
> other
> > contributors filling in the new website with CSS, Haml, and most
> importantly
> > AsciiDoc (for documentation!)
> >
> >
> > Some of the features of jenkins.io that are important to me, I'd
> like to share:
> >
> > * Visual priority given to the LTS release line (yay)
> > * Built-in support for three layers of documentation: solution
> pages, getting
> >   started guides and the "handbook".
> > * Visual elements to highlight upcoming events
> > * Certificates automated via letsencrypt.org (this is my favorite
> ;))
> >
> > The site is statically generated and contributions are welcome here:
> >
> >
> >
> > As I mentioned in our last project meeting, migration of other
> properties such
> > as wiki.jenkins-ci.org to the jenkins.io domain will take a bit
> more time. This
> > is an important first step however!
> >
> >
> >
> > Cheers
> > - R. Tyler Croy
> >
> > --
> > Code: 
> >  Chatter: 
> >
> >  % gpg --keyserver keys.gnupg.net --recv-key 3F51E16F
> > --
> >
> > --
> > 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/20160324060209.GB15060%40blackberry.coupleofllamas.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-de...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/509BAC1C-7F4D-47B6-85BA-5964EF6695DE%40fortysix.ch
> .
> 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-de...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS7E9aiyFAHqpzSszv_sN%3DynoZE0Wt466t%2Bq%3DPN_8yNKZw%40mail.gmail.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-de...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-dev/CAMszB6yJ0aAZ94GaYke96rGmAXZvOdy3FLLBOgkNAF7iaxD27Q%40mail.gmail.com
>>> 

Re: [GSOC 2016] Support core plugin improvements

[Oleg Nenashev]

IMHO it's ready to go.
Thanks for polishing it!

четверг, 24 марта 2016 г., 8:18:48 UTC+1 пользователь Arnaud Héritier 
написал:
>
> Perfect. Thanks a lot. 
>
> Le jeudi 24 mars 2016, Minudika Malshan  
> a écrit :
>
>> Hi all,
>>
>> Thanks a lot for your feedback.
>> @Arnaud : Yes I followed those guide lines when creating my proposal.
>>
>> I will go through the whole proposal one more time, finalize it and 
>> submit the final proposal by tonight.
>>
>> Best Regards
>>
>> On Thu, Mar 24, 2016 at 12:12 PM, Arnaud Héritier  
>> wrote:
>>
>>> Minudika
>>>
>>> For me it seems that your proposal is conform to 
>>> http://write.flossmanuals.net/gsocstudentguide/writing-a-proposal/
>>>
>>> I think you are ready to submit it
>>>
>>> On Thu, Mar 24, 2016 at 4:35 AM, Steve Christou  
>>> wrote:
>>>
 Hello Minudika,

 I like the proposal! I have no more feedback from my side.

 Thanks,
 Steve.

 On Wed, Mar 23, 2016 at 6:03 PM Arnaud Héritier  
 wrote:

> Hi Minudika
>
>   I have no more feedbacks on my side. I let the others challenge the 
> proposal (especially Steven who is an active maintainer of the plugin).
>
> Thanks guys
>
> On Wed, Mar 23, 2016 at 9:07 PM, Steve Christou  > wrote:
>
>> Hello Minudika,
>>
>> Thank you for creating this proposal document! I will be reading over 
>> this tonight and providing my comments.
>>
>> On Wed, Mar 23, 2016 at 2:59 PM Minudika Malshan <
>> minudika...@gmail.com> wrote:
>>
>>> Thanks a lot for  your kind help.. :)
>>>
>>> BR
>>>
>>> On Thu, Mar 24, 2016 at 12:09 AM, Oleg Nenashev <
>>> o.v.nenas...@gmail.com> wrote:
>>>
 I'll try to take a look before the office hours today.
 Arnaud is busy with BreizhCamp, but maybe we will get Steve online.

 BR, Oleg

 2016-03-23 17:59 GMT+01:00 Minudika Malshan 
 :

> Hi all,
>
> Sorry for spamming. Since the time is running fast I am in a bit 
> of hurry. Could you please let me know if there's any more changes to 
> be 
> made on my proposal.
> Then I can make them and submit the finalized proposal to google.
>
> Thanks and  regards.
>
> On Tue, Mar 22, 2016 at 7:05 PM, Minudika Malshan <
> minudika...@gmail.com> wrote:
>
>> Hi,
>>
>> Thanks a lot Oleg and Arnaud for your valuable comments.
>> I made changes according to your comments. Please have a look and 
>> let me know if there's anything more to be improved or changed.
>>
>> Best regards
>>
>> On Tue, Mar 22, 2016 at 1:34 PM, Oleg Nenashev <
>> o.v.nenas...@gmail.com> wrote:
>>
>>> The proposal look good, thanks for preparing it!
>>> I've added several comments to it
>>>
>>> вторник, 22 марта 2016 г., 0:24:25 UTC+1 пользователь Arnaud 
>>> Héritier написал:

 Thanks a lot Minudika.

 @all please have a look at it and review/comment

 cheers

 On Tue, Mar 22, 2016 at 12:22 AM, Minudika Malshan <
 minud...@gmail.com> wrote:

 Hi all,

 Here is the first draft of my proposal [1] . I submitted it 
 also to the google's site.
 Please review it and let me know if there's any possible 
 improvements to be made on it.

 [1] 
 https://docs.google.com/document/d/1052sUGFxcDfUHNZFNeQ1FAR61ZB4tJb-GxdW1L3FSC8/edit?usp=sharing

 Your comments would be much appreciated.

 Thanks a lot.

 On Tue, Mar 22, 2016 at 4:05 AM, Arnaud Héritier <
 aher...@gmail.com> wrote:

 Really good job Minudika.
 For now I don't see anything to improve.
 I let you officially share it on the dev mailing list to have 
 more feedbacks.
 thanks again for the hard work

 On Mon, Mar 21, 2016 at 11:01 PM, Minudika Malshan <
 minud...@gmail.com> wrote:

 Hi Arnaud,

 I created a proposal [1] and published as a draft in the 
 google's site as well.
 Could you please review it and suggest improvements which 
 should be made.

 [1] 
 https://docs.google.com/document/d/1052sUGFxcDfUHNZFNeQ1FAR61ZB4tJb-GxdW1L3FSC8/edit?usp=sharing

 Thanks and regards,

 On Sun, Mar 20, 2016 at 11:07 

Re: Pipeline View Plugin

[Tom Fennelly]

Nice work Sergei.

On Monday, March 21, 2016 at 6:52:04 AM UTC, Sergei Egorov wrote:
>
> Hey everyone, 
>
> Yesterday I decided to publish sources for my pipeline visualization 
> plugin: https://github.com/bsideup/jenkins-pipeline-view
>
> 
>
>
> What's cool about it? 
> First of all, it *can handle any graph* provided by pipeline because it 
> uses very powerful *JS graph library* to position steps. 
> Also, it's a *React* application, written in *ES7* (not even ES6!), with 
> ImmutableJS and RxJS inside - so hipsters will be happy :D But in fact, it 
> means that it's damn easy to develop this plugin and provide more 
> functionality. 
> I use *Webpack* to bundle everything (JS, CSS, fonts, images, SVG icons) 
> in one single pipe.js file. *No Jenkins JS Modules*, no conflicts, no 
> impact on others. Even CSS will not conflict because of *CSS-modules* ( 
> http://glenmaddern.com/articles/css-modules )
> All icons are SVG ones and look good on any screen, retina or not, and any 
> zoom level.
>
> I use Jackson on the backend side to serialize FlowNodes and their 
> actions. *Why Jackson?* Because it was much easier to implement 
> serialization of selected (non-exposed) fields and class info included 
> compared to Stapler. I saw something were done about classinfo in Stapler, 
> but at the moment of creation of this plugin, it wasn't delivered to 
> Jenkins core yet. Also, *almost none of the Pipeline actions are 
> @Expose-d*.
>
> I use *gradle-jpi-plugin* instead of Maven because it's much easier to 
> describe some complex build process with Gradle, especially when frontend 
> build is involved. In fact, it's just one line:
>
> https://github.com/bsideup/jenkins-pipeline-view/blob/954b895b6574cdf34815ff94a4a8db3ad3811aeb/build.gradle#L61
>
>
> Future development
> Will I continue to develop it? Definitely! Here, *at ZeroTurnaround*, we 
> use Jenkins a lot, and eventually we will migrate to the pipelines, and 
> proper visualization of the process is a must for us. And feel free to 
> contribute as well, it's really a good chance to learn *modern JS stack* as 
> well :)
>
>
>
> Best regards,
> Sergei Egorov
>

-- 
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/dc12f555-426d-4fdc-9361-95d5f34bb1e3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: custom-tools plugin: adding support for 7z-files

[Vincent Daburon]

Hi,
In the javadoc, you could see :
https://commons.apache.org/proper/commons-compress/apidocs/index.html?org/apache/commons/compress/archivers/sevenz/package-tree.html

"The format is very Windows/Intel specific, so it uses little-endian byte 
order, doesn't store user/group or permission bits, and represents times 
using NTFS timestamps (100 nanosecond units since 1 January 1601). Hence 
the official tools *recommend against using it for backup purposes on *nix*, 
and recommend .tar.7z or .tar.lzma or .tar.xz instead."

Not sure, it will be a good feature for *nix OS.

Regards.
Vincent D.

On Thursday, March 24, 2016 at 1:30:06 PM UTC+1, Martin Hjelmqvist wrote:
>
> I have code for a simple 7z-extractor using Apache's SevenZ classes, but 
> 7-Zip-JBinding might be better to use instead.
> I'll have a closer look at it later. Thanks for the tip. :)
>
> Den torsdag 24 mars 2016 kl. 13:12:12 UTC+1 skrev Boris Brodski:
>>
>> Sorry for interfering. Can 7-Zip-JBinding be helpful in some way here?
>>
>> http://sevenzipjbind.sourceforge.net/
>>
>

-- 
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/dc6ef6a0-2165-4c4a-a398-a767a81adcd4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Meet jenkins.io

[Tom Fennelly]

Really nice. Thanks guys!!

On Thursday, March 24, 2016 at 12:58:35 PM UTC, Manuel Recena Soto wrote:
>
> CONGRATULATIONS!
>
> 2016-03-24 11:38 GMT+01:00 Krishna Gundala  >:
>
>> Excellent Work.. Kudos folks...
>> You rock Tyler..
>> Very Nice Website..
>>
>> ---
>>  
>>
>> Mohan Krishna Gundala
>> [image: https://]about.me/gmk.india
>>
>> 
>>   
>>  
>>
>> On Thu, Mar 24, 2016 at 2:31 PM, Baptiste Mathus > > wrote:
>>
>>> +1, congrats to everyone involved, and especially thanks to you Tyler. 
>>> Really nice website.
>>>
>>> 2016-03-24 6:23 GMT+00:00 domi :
>>>
 Really nice work!!!
 /Domi

 > On 24 Mar 2016, at 07:02, R. Tyler Croy  wrote:
 >
 > I finished up the final work for migration from 
 https://jenkins-ci.org to
 > https://jenkins.io today. The final step of the switchover was to 
 redirect
 > non-mapped URLs from jenkins-ci.org over to jenkins.io.
 >
 >
 > This project has been a tremendous amount of work with Gus Reiber, 
 Baptiste
 > Mathaus, James Dumay, Daniel Beck, Oleg Nenashev  and a number of 
 other
 > contributors filling in the new website with CSS, Haml, and most 
 importantly
 > AsciiDoc (for documentation!)
 >
 >
 > Some of the features of jenkins.io that are important to me, I'd 
 like to share:
 >
 > * Visual priority given to the LTS release line (yay)
 > * Built-in support for three layers of documentation: solution pages, 
 getting
 >   started guides and the "handbook".
 > * Visual elements to highlight upcoming events
 > * Certificates automated via letsencrypt.org (this is my favorite ;))
 >
 > The site is statically generated and contributions are welcome here:
 >
 >
 >
 > As I mentioned in our last project meeting, migration of other 
 properties such
 > as wiki.jenkins-ci.org to the jenkins.io domain will take a bit more 
 time. This
 > is an important first step however!
 >
 >
 >
 > Cheers
 > - R. Tyler Croy
 >
 > --
 > Code: 
 >  Chatter: 
 >
 >  % gpg --keyserver keys.gnupg.net --recv-key 3F51E16F
 > --
 >
 > --
 > 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/20160324060209.GB15060%40blackberry.coupleofllamas.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-de...@googlegroups.com .
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/jenkinsci-dev/509BAC1C-7F4D-47B6-85BA-5964EF6695DE%40fortysix.ch
 .
 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-de...@googlegroups.com .
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS7E9aiyFAHqpzSszv_sN%3DynoZE0Wt466t%2Bq%3DPN_8yNKZw%40mail.gmail.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-de...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/CAMszB6yJ0aAZ94GaYke96rGmAXZvOdy3FLLBOgkNAF7iaxD27Q%40mail.gmail.com
>>  
>> 
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> Manuel Recena Soto
> * manuelrecena.com [/blog]
> * linkedin.com/in/recena
>

-- 
You received this message 

Re: Meet jenkins.io

[Manuel Jesús Recena Soto]

CONGRATULATIONS!

2016-03-24 11:38 GMT+01:00 Krishna Gundala :

> Excellent Work.. Kudos folks...
> You rock Tyler..
> Very Nice Website..
>
> ---
>
>
> Mohan Krishna Gundala
> [image: https://]about.me/gmk.india
>
> 
>
>
>
> On Thu, Mar 24, 2016 at 2:31 PM, Baptiste Mathus 
> wrote:
>
>> +1, congrats to everyone involved, and especially thanks to you Tyler.
>> Really nice website.
>>
>> 2016-03-24 6:23 GMT+00:00 domi :
>>
>>> Really nice work!!!
>>> /Domi
>>>
>>> > On 24 Mar 2016, at 07:02, R. Tyler Croy  wrote:
>>> >
>>> > I finished up the final work for migration from https://jenkins-ci.org
>>> to
>>> > https://jenkins.io today. The final step of the switchover was to
>>> redirect
>>> > non-mapped URLs from jenkins-ci.org over to jenkins.io.
>>> >
>>> >
>>> > This project has been a tremendous amount of work with Gus Reiber,
>>> Baptiste
>>> > Mathaus, James Dumay, Daniel Beck, Oleg Nenashev  and a number of other
>>> > contributors filling in the new website with CSS, Haml, and most
>>> importantly
>>> > AsciiDoc (for documentation!)
>>> >
>>> >
>>> > Some of the features of jenkins.io that are important to me, I'd like
>>> to share:
>>> >
>>> > * Visual priority given to the LTS release line (yay)
>>> > * Built-in support for three layers of documentation: solution pages,
>>> getting
>>> >   started guides and the "handbook".
>>> > * Visual elements to highlight upcoming events
>>> > * Certificates automated via letsencrypt.org (this is my favorite ;))
>>> >
>>> > The site is statically generated and contributions are welcome here:
>>> >
>>> >
>>> >
>>> > As I mentioned in our last project meeting, migration of other
>>> properties such
>>> > as wiki.jenkins-ci.org to the jenkins.io domain will take a bit more
>>> time. This
>>> > is an important first step however!
>>> >
>>> >
>>> >
>>> > Cheers
>>> > - R. Tyler Croy
>>> >
>>> > --
>>> > Code: 
>>> >  Chatter: 
>>> >
>>> >  % gpg --keyserver keys.gnupg.net --recv-key 3F51E16F
>>> > --
>>> >
>>> > --
>>> > 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/20160324060209.GB15060%40blackberry.coupleofllamas.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/509BAC1C-7F4D-47B6-85BA-5964EF6695DE%40fortysix.ch
>>> .
>>> 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/CANWgJS7E9aiyFAHqpzSszv_sN%3DynoZE0Wt466t%2Bq%3DPN_8yNKZw%40mail.gmail.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/CAMszB6yJ0aAZ94GaYke96rGmAXZvOdy3FLLBOgkNAF7iaxD27Q%40mail.gmail.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Manuel Recena Soto
* manuelrecena.com [/blog]
* linkedin.com/in/recena

-- 
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 

Re: Display Git changelog as a list of Atlassian Stash (Bitbucket Server) pull requests

[Nickolay Rumyantsev]

Thanks Mark!
Now I have to find the time to study all that stuff :)

Regards,
Nick

On Wednesday, March 23, 2016 at 10:29:20 PM UTC+3, Mark Waite wrote:
>
> There is another build chooser implementation at 
> https://github.com/phemmer/jenkins-git-chooser-build-branches if you'd 
> like to see another example of a plugin that uses the BuildChooser 
> extension point.
>
> Mark Waite
>
> On Wed, Mar 23, 2016 at 1:26 PM Mark Waite  > wrote:
>
>> I believe you're correct that there is not an extension point in the git 
>> plugin for GitChangeSet.  
>>
>> There are extension points for BuildChooser 
>> (hudson.plugins.git.util.BuildChooser) and Listener 
>> (hudson.plugins.git.GitStatus.Listener).  The BuildChooser extension point 
>> has been used to create an additional plugin, the Git Chooser Alternative 
>> plugin (
>> https://wiki.jenkins-ci.org/display/JENKINS/Git+Chooser+Alternative+Plugin) 
>> .  
>>
>> You might be able to model your proposed changes to the git plugin after 
>> BuildChooser and you might be able to use the Git Chooser Alternative as a 
>> reference implementation of someone using an extension point to create a 
>> new plugin which extends another plugin.
>>
>> Mark Waite
>>
>> On Tue, Mar 22, 2016 at 9:00 AM Nickolay Rumyantsev > > wrote:
>>
>>> Hi,
>>>
>>> In my company we use Atlassian Stash (now Bitbucket Server) to serve our 
>>> sources. We use pull requests to merge our features to master branch.
>>> I want to extend the Jenkins Git plugin making it able to display the 
>>> changelog as a list of Pull Requests with a fallback to usual commits (some 
>>> automatic direct commits happen).
>>> I took a look in the Git plugin sources I found that the GitChangeSet is 
>>> a result of parsing of 'git log' command which is stored in plain text in 
>>> the build dir.
>>> Changelog might be re-parsed every time the build object is collected.
>>> An ideal solution is to create a plugin with a new git scm extension 
>>> that can decorate the changelog parsing process. As far as I understand the 
>>> interface of GitSCMExtension doesn't seem to provide the proper entry 
>>> point. If my guess is not correct could you please suggest the right point 
>>> to extend? Otherwise, should I create a new extension point somehow?
>>>
>>> Thanks,
>>> Nick
>>>
>>> -- 
>>> 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/5d3bd90c-3cc3-4950-8f06-26e246a32db5%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/373cd4bc-f00b-4523-af7a-2f85ff7bf95c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: custom-tools plugin: adding support for 7z-files

[Martin Hjelmqvist]

I have code for a simple 7z-extractor using Apache's SevenZ classes, but 
7-Zip-JBinding might be better to use instead.
I'll have a closer look at it later. Thanks for the tip. :)

Den torsdag 24 mars 2016 kl. 13:12:12 UTC+1 skrev Boris Brodski:
>
> Sorry for interfering. Can 7-Zip-JBinding be helpful in some way here?
>
> http://sevenzipjbind.sourceforge.net/
>

-- 
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/0e09d3bf-3ea7-4670-8c0a-339f4d4214e1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: custom-tools plugin: adding support for 7z-files

[Boris Brodski]

Sorry for interfering. Can 7-Zip-JBinding be helpful in some way here?

http://sevenzipjbind.sourceforge.net/

-- 
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/76c005d6-da66-4b5b-ab5d-882d58c9a7bb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Looking for a plugin: "show git tag tree" or "run groovy script and show results on a project page"

[Boris Brodski]

Dear Jenkins-Team,


My goal is to show on a Job main page (or on some Job special page) a Git 
"tree of tags", similar to

  $ gitk --tags --simplify-by-decoration


Put it simply: I would like to show all tags in a repository as a tree.

I thought about following two solutions:

1) Find/Write a Jenkins-plugin, that allows me to write a Groovy script and 
output the result HTML to the Job main page (e.g. as a project description) 
or output the result HTML on some new project-hosted page. Then implement 
the functionality in Groovy.

2) Find/Write a Jenkins-plugin, that solves the task directly without any 
Groovy.

Any suggestions on this?

Thank you!


Cheers,
Boris Brodski

-- 
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/76f773c2-9dd1-4c71-aba1-5824c86b1033%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: custom-tools plugin: adding support for 7z-files

[Martin Hjelmqvist]

Hello again, Oleg

I could use some more advice about how to integrate this feature.
If this 7zip-installer is added to ExtraToolInstallers, where in custom 
tools plugin do you think I should call the 7zip-installer? 
So far the tracks lead me to hudson.tools.FilePath where an if statement 
checks whether the archive ends with zip or tar.gz.
Source (line 821 and 847): 
https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/FilePath.java

Should I do any changes there as well or is there any other way to do this?

Sincerely,
Martin Hjelmqvist 

Den tisdag 22 mars 2016 kl. 13:19:51 UTC+1 skrev Oleg Nenashev:
>
> Hi Martin,
>
> Yes, GSoC is definitely not an option for this year bachelor thesis.
>
> Are you proposing that I add this feature in the Extra Tool Installers 
>> Plugin that extends AbstractExtraToolInstaller (which in turn extends 
>> ToolInstaller)? By extension points, you mean like BatchCommandInstaller 
>> and SharedDirectoryInstaller? 
>
>
> Something like that. Generic Tool installers definitely do not belong to 
> Custom Tools Plugin from my PoV.
>
> Just a note on the terminology:
>
>- Extention Point - ToolInstaller (it extends the ExtensionPoint 
>interface)
>- Extension Point implementation - BatchCommandInstaller, 
> SharedDirectoryInstaller, 
>etc.
>
> BR, Oleg
>
> 2016-03-22 12:41 GMT+01:00 Martin Hjelmqvist  >:
>
>> Hi Oleg!
>>
>> Good to hear! This project is planned to be finished by the end of May 
>> this year though. 
>>
>> Aha, I need to approach this in another way then. Are you proposing that 
>> I add this feature in the Extra Tool Installers Plugin that extends 
>> AbstractExtraToolInstaller (which in turn extends ToolInstaller)? By 
>> extension points, you mean like BatchCommandInstaller and 
>> SharedDirectoryInstaller? Trying to get a picture of the structure. :)
>>
>> Sincerely,
>> Martin Hjelmqvist
>>
>> Den tisdag 22 mars 2016 kl. 11:08:54 UTC+1 skrev Oleg Nenashev:
>>>
>>> Hi Martin,
>>>
>>> Great to hear that you're working on this plugin. I'm it's maintainer, 
>>> so I will try to help where I can. If you consider a long-term project ("if 
>>> you graduate on the next year"), maybe you would be interested to make a 
>>> proposal for Google Summer Of Code 
>>> . 
>>> I think we can find mentors for this project
>>>
>>> Regarding your question...
>>>
>>> Actually, "ToolInstallation 
>>> " and 
>>> "ToolInstaller 
>>> " are 
>>> different entities in Jenkins. Custom Tools Plugin provides the 
>>> ToolInstallation implementation, but it uses standard ToolInstallers being 
>>> provided by other Jenkins plugins.
>>>
>>> If you want to add a 7zip ToolInstaller, I think Extra Tool Installers 
>>> Plugin 
>>>  
>>> is the best destination for such feature. You can find examples of 
>>> extension point implementations there.
>>>
>>> Best regards,
>>> Oleg Nenashev
>>>
>>> вторник, 22 марта 2016 г., 10:50:10 UTC+1 пользователь Martin Hjelmqvist 
>>> написал:

 Hello,

 I'm currently working on my bachelor thesis; Improve the Jenkins custom 
 tools installer. There is a need for a file format able to contain up to 
 100GB of installation files, since tar.gz and zip has a size limit of ~8GB 
 and ~4GB size limit respectively. The idea is to add support for the file 
 format 7z which currently has a size limit of 16 exabytes and also is 
 faster to unpack than a zip file.

 Anything I should keep in mind when integrating the extension for this 
 plugin? So far I have developed code for unpacking a 7z-file through a 
 string file path, but not sure that will work in the end.
 Any thoughts?

 Sincerely,
 Martin Hjelmqvist
 Bachelor Thesis at HMS Industrial Networks, Sweden

>>> -- 
>> 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/74aZNSlm3Yg/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> jenkinsci-de...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/15de6fd5-4403-40ce-9140-8b5b3b13b071%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 

executors.jelly - I cant see progress bar

[justine . maxellon]

hello
In my plugin I'm creating new suppage like http://(...)/jenkins/my-page. I 
want to present there, among other things, list of nodes in slightly 
changed form.
By now I copied file executors.jelly (I will be changing it later) to my 
project and in index.jelly page I put code:






I see running build, it's name and I can get URL adress, but I don't see 
its progress bar. Does anyone have an idea why? Please help me.
p.s. If "include page" is outside ajax I see "Unknown Task" instead of 
build name/link

-- 
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/4bc3d015-ab3e-426a-abed-7369d7d10295%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Meet jenkins.io

[Krishna Gundala]

Excellent Work.. Kudos folks...
You rock Tyler..
Very Nice Website..

---


Mohan Krishna Gundala
[image: https://]about.me/gmk.india




On Thu, Mar 24, 2016 at 2:31 PM, Baptiste Mathus  wrote:

> +1, congrats to everyone involved, and especially thanks to you Tyler.
> Really nice website.
>
> 2016-03-24 6:23 GMT+00:00 domi :
>
>> Really nice work!!!
>> /Domi
>>
>> > On 24 Mar 2016, at 07:02, R. Tyler Croy  wrote:
>> >
>> > I finished up the final work for migration from https://jenkins-ci.org
>> to
>> > https://jenkins.io today. The final step of the switchover was to
>> redirect
>> > non-mapped URLs from jenkins-ci.org over to jenkins.io.
>> >
>> >
>> > This project has been a tremendous amount of work with Gus Reiber,
>> Baptiste
>> > Mathaus, James Dumay, Daniel Beck, Oleg Nenashev  and a number of other
>> > contributors filling in the new website with CSS, Haml, and most
>> importantly
>> > AsciiDoc (for documentation!)
>> >
>> >
>> > Some of the features of jenkins.io that are important to me, I'd like
>> to share:
>> >
>> > * Visual priority given to the LTS release line (yay)
>> > * Built-in support for three layers of documentation: solution pages,
>> getting
>> >   started guides and the "handbook".
>> > * Visual elements to highlight upcoming events
>> > * Certificates automated via letsencrypt.org (this is my favorite ;))
>> >
>> > The site is statically generated and contributions are welcome here:
>> >
>> >
>> >
>> > As I mentioned in our last project meeting, migration of other
>> properties such
>> > as wiki.jenkins-ci.org to the jenkins.io domain will take a bit more
>> time. This
>> > is an important first step however!
>> >
>> >
>> >
>> > Cheers
>> > - R. Tyler Croy
>> >
>> > --
>> > Code: 
>> >  Chatter: 
>> >
>> >  % gpg --keyserver keys.gnupg.net --recv-key 3F51E16F
>> > --
>> >
>> > --
>> > 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/20160324060209.GB15060%40blackberry.coupleofllamas.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/509BAC1C-7F4D-47B6-85BA-5964EF6695DE%40fortysix.ch
>> .
>> 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/CANWgJS7E9aiyFAHqpzSszv_sN%3DynoZE0Wt466t%2Bq%3DPN_8yNKZw%40mail.gmail.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/CAMszB6yJ0aAZ94GaYke96rGmAXZvOdy3FLLBOgkNAF7iaxD27Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Meet jenkins.io

[Baptiste Mathus]

+1, congrats to everyone involved, and especially thanks to you Tyler.
Really nice website.

2016-03-24 6:23 GMT+00:00 domi :

> Really nice work!!!
> /Domi
>
> > On 24 Mar 2016, at 07:02, R. Tyler Croy  wrote:
> >
> > I finished up the final work for migration from https://jenkins-ci.org
> to
> > https://jenkins.io today. The final step of the switchover was to
> redirect
> > non-mapped URLs from jenkins-ci.org over to jenkins.io.
> >
> >
> > This project has been a tremendous amount of work with Gus Reiber,
> Baptiste
> > Mathaus, James Dumay, Daniel Beck, Oleg Nenashev  and a number of other
> > contributors filling in the new website with CSS, Haml, and most
> importantly
> > AsciiDoc (for documentation!)
> >
> >
> > Some of the features of jenkins.io that are important to me, I'd like
> to share:
> >
> > * Visual priority given to the LTS release line (yay)
> > * Built-in support for three layers of documentation: solution pages,
> getting
> >   started guides and the "handbook".
> > * Visual elements to highlight upcoming events
> > * Certificates automated via letsencrypt.org (this is my favorite ;))
> >
> > The site is statically generated and contributions are welcome here:
> >
> >
> >
> > As I mentioned in our last project meeting, migration of other
> properties such
> > as wiki.jenkins-ci.org to the jenkins.io domain will take a bit more
> time. This
> > is an important first step however!
> >
> >
> >
> > Cheers
> > - R. Tyler Croy
> >
> > --
> > Code: 
> >  Chatter: 
> >
> >  % gpg --keyserver keys.gnupg.net --recv-key 3F51E16F
> > --
> >
> > --
> > 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/20160324060209.GB15060%40blackberry.coupleofllamas.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/509BAC1C-7F4D-47B6-85BA-5964EF6695DE%40fortysix.ch
> .
> 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/CANWgJS7E9aiyFAHqpzSszv_sN%3DynoZE0Wt466t%2Bq%3DPN_8yNKZw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [GSoC2016] External Workspace Manager plugin development

[somai . alexandru]

Oleg, Martin,

Can you please have one final look over my project proposal 

 
before I will submit it?

Thank you,
Alex

On Monday, March 21, 2016 at 5:01:31 PM UTC+2, martinda wrote:
>
> Hello Alex,
>
> On Sunday, March 20, 2016 at 6:09:38 PM UTC-4, somai.a...@gmail.com wrote:
>>
>>
>> Related to the unit testing examples, the sooner you share them the 
>> better. I can look over them early to get accustomed to.
>>
>>
> Basic test example:
>
> https://github.com/martinda/workflow-migration-demo/blob/master/src/test/java/org/jenkins/plugins/demo/Demo1Test.java
>
> The most recent way of writing the pom.xml that I use is in this project 
> (also incudes some basic test examples - roundtrip and global config access 
> from plugin test):
>
> https://github.com/martinda/jenkins-plugin-globalconfig-demo1/blob/master/src/test/java/org/jenkins/plugins/demo/Demo1Test.java
>
> More elaborate test examples:
>
> https://github.com/martinda/http-request-plugin/tree/feature/workflow-integration/src/test/java/jenkins/plugins/http_request
>
> Martin
>

-- 
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/e8101124-bce3-42cb-ae47-02a0eaea0756%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [GSOC 2016] Support core plugin improvements

[Arnaud Héritier]

Perfect. Thanks a lot.

Le jeudi 24 mars 2016, Minudika Malshan  a écrit :

> Hi all,
>
> Thanks a lot for your feedback.
> @Arnaud : Yes I followed those guide lines when creating my proposal.
>
> I will go through the whole proposal one more time, finalize it and submit
> the final proposal by tonight.
>
> Best Regards
>
> On Thu, Mar 24, 2016 at 12:12 PM, Arnaud Héritier  > wrote:
>
>> Minudika
>>
>> For me it seems that your proposal is conform to
>> http://write.flossmanuals.net/gsocstudentguide/writing-a-proposal/
>>
>> I think you are ready to submit it
>>
>> On Thu, Mar 24, 2016 at 4:35 AM, Steve Christou > > wrote:
>>
>>> Hello Minudika,
>>>
>>> I like the proposal! I have no more feedback from my side.
>>>
>>> Thanks,
>>> Steve.
>>>
>>> On Wed, Mar 23, 2016 at 6:03 PM Arnaud Héritier >> > wrote:
>>>
 Hi Minudika

   I have no more feedbacks on my side. I let the others challenge the
 proposal (especially Steven who is an active maintainer of the plugin).

 Thanks guys

 On Wed, Mar 23, 2016 at 9:07 PM, Steve Christou > wrote:

> Hello Minudika,
>
> Thank you for creating this proposal document! I will be reading over
> this tonight and providing my comments.
>
> On Wed, Mar 23, 2016 at 2:59 PM Minudika Malshan <
> minudika...@gmail.com
> > wrote:
>
>> Thanks a lot for  your kind help.. :)
>>
>> BR
>>
>> On Thu, Mar 24, 2016 at 12:09 AM, Oleg Nenashev <
>> o.v.nenas...@gmail.com
>> > wrote:
>>
>>> I'll try to take a look before the office hours today.
>>> Arnaud is busy with BreizhCamp, but maybe we will get Steve online.
>>>
>>> BR, Oleg
>>>
>>> 2016-03-23 17:59 GMT+01:00 Minudika Malshan >> >:
>>>
 Hi all,

 Sorry for spamming. Since the time is running fast I am in a bit of
 hurry. Could you please let me know if there's any more changes to be 
 made
 on my proposal.
 Then I can make them and submit the finalized proposal to google.

 Thanks and  regards.

 On Tue, Mar 22, 2016 at 7:05 PM, Minudika Malshan <
 minudika...@gmail.com
 > wrote:

> Hi,
>
> Thanks a lot Oleg and Arnaud for your valuable comments.
> I made changes according to your comments. Please have a look and
> let me know if there's anything more to be improved or changed.
>
> Best regards
>
> On Tue, Mar 22, 2016 at 1:34 PM, Oleg Nenashev <
> o.v.nenas...@gmail.com
> > wrote:
>
>> The proposal look good, thanks for preparing it!
>> I've added several comments to it
>>
>> вторник, 22 марта 2016 г., 0:24:25 UTC+1 пользователь Arnaud
>> Héritier написал:
>>>
>>> Thanks a lot Minudika.
>>>
>>> @all please have a look at it and review/comment
>>>
>>> cheers
>>>
>>> On Tue, Mar 22, 2016 at 12:22 AM, Minudika Malshan <
>>> minud...@gmail.com> wrote:
>>>
>>> Hi all,
>>>
>>> Here is the first draft of my proposal [1] . I submitted it also
>>> to the google's site.
>>> Please review it and let me know if there's any possible
>>> improvements to be made on it.
>>>
>>> [1]
>>> https://docs.google.com/document/d/1052sUGFxcDfUHNZFNeQ1FAR61ZB4tJb-GxdW1L3FSC8/edit?usp=sharing
>>>
>>> Your comments would be much appreciated.
>>>
>>> Thanks a lot.
>>>
>>> On Tue, Mar 22, 2016 at 4:05 AM, Arnaud Héritier <
>>> aher...@gmail.com> wrote:
>>>
>>> Really good job Minudika.
>>> For now I don't see anything to improve.
>>> I let you officially share it on the dev mailing list to have
>>> more feedbacks.
>>> thanks again for the hard work
>>>
>>> On Mon, Mar 21, 2016 at 11:01 PM, Minudika Malshan <
>>> minud...@gmail.com> wrote:
>>>
>>> Hi Arnaud,
>>>
>>> I created a proposal [1] and published as a draft in the
>>> google's site as well.
>>> Could you please review it and suggest improvements which should
>>> be made.

Re: [GSOC 2016] Support core plugin improvements

[Minudika Malshan]

Hi all,

Thanks a lot for your feedback.
@Arnaud : Yes I followed those guide lines when creating my proposal.

I will go through the whole proposal one more time, finalize it and submit
the final proposal by tonight.

Best Regards

On Thu, Mar 24, 2016 at 12:12 PM, Arnaud Héritier 
wrote:

> Minudika
>
> For me it seems that your proposal is conform to
> http://write.flossmanuals.net/gsocstudentguide/writing-a-proposal/
>
> I think you are ready to submit it
>
> On Thu, Mar 24, 2016 at 4:35 AM, Steve Christou 
> wrote:
>
>> Hello Minudika,
>>
>> I like the proposal! I have no more feedback from my side.
>>
>> Thanks,
>> Steve.
>>
>> On Wed, Mar 23, 2016 at 6:03 PM Arnaud Héritier 
>> wrote:
>>
>>> Hi Minudika
>>>
>>>   I have no more feedbacks on my side. I let the others challenge the
>>> proposal (especially Steven who is an active maintainer of the plugin).
>>>
>>> Thanks guys
>>>
>>> On Wed, Mar 23, 2016 at 9:07 PM, Steve Christou 
>>> wrote:
>>>
 Hello Minudika,

 Thank you for creating this proposal document! I will be reading over
 this tonight and providing my comments.

 On Wed, Mar 23, 2016 at 2:59 PM Minudika Malshan 
 wrote:

> Thanks a lot for  your kind help.. :)
>
> BR
>
> On Thu, Mar 24, 2016 at 12:09 AM, Oleg Nenashev <
> o.v.nenas...@gmail.com> wrote:
>
>> I'll try to take a look before the office hours today.
>> Arnaud is busy with BreizhCamp, but maybe we will get Steve online.
>>
>> BR, Oleg
>>
>> 2016-03-23 17:59 GMT+01:00 Minudika Malshan :
>>
>>> Hi all,
>>>
>>> Sorry for spamming. Since the time is running fast I am in a bit of
>>> hurry. Could you please let me know if there's any more changes to be 
>>> made
>>> on my proposal.
>>> Then I can make them and submit the finalized proposal to google.
>>>
>>> Thanks and  regards.
>>>
>>> On Tue, Mar 22, 2016 at 7:05 PM, Minudika Malshan <
>>> minudika...@gmail.com> wrote:
>>>
 Hi,

 Thanks a lot Oleg and Arnaud for your valuable comments.
 I made changes according to your comments. Please have a look and
 let me know if there's anything more to be improved or changed.

 Best regards

 On Tue, Mar 22, 2016 at 1:34 PM, Oleg Nenashev <
 o.v.nenas...@gmail.com> wrote:

> The proposal look good, thanks for preparing it!
> I've added several comments to it
>
> вторник, 22 марта 2016 г., 0:24:25 UTC+1 пользователь Arnaud
> Héritier написал:
>>
>> Thanks a lot Minudika.
>>
>> @all please have a look at it and review/comment
>>
>> cheers
>>
>> On Tue, Mar 22, 2016 at 12:22 AM, Minudika Malshan <
>> minud...@gmail.com> wrote:
>>
>> Hi all,
>>
>> Here is the first draft of my proposal [1] . I submitted it also
>> to the google's site.
>> Please review it and let me know if there's any possible
>> improvements to be made on it.
>>
>> [1]
>> https://docs.google.com/document/d/1052sUGFxcDfUHNZFNeQ1FAR61ZB4tJb-GxdW1L3FSC8/edit?usp=sharing
>>
>> Your comments would be much appreciated.
>>
>> Thanks a lot.
>>
>> On Tue, Mar 22, 2016 at 4:05 AM, Arnaud Héritier <
>> aher...@gmail.com> wrote:
>>
>> Really good job Minudika.
>> For now I don't see anything to improve.
>> I let you officially share it on the dev mailing list to have
>> more feedbacks.
>> thanks again for the hard work
>>
>> On Mon, Mar 21, 2016 at 11:01 PM, Minudika Malshan <
>> minud...@gmail.com> wrote:
>>
>> Hi Arnaud,
>>
>> I created a proposal [1] and published as a draft in the google's
>> site as well.
>> Could you please review it and suggest improvements which should
>> be made.
>>
>> [1]
>> https://docs.google.com/document/d/1052sUGFxcDfUHNZFNeQ1FAR61ZB4tJb-GxdW1L3FSC8/edit?usp=sharing
>>
>> Thanks and regards,
>>
>> On Sun, Mar 20, 2016 at 11:07 PM, Arnaud Héritier <
>> aher...@gmail.com> wrote:
>>
>> Yes the goal is to allow to automatically create the ticket in
>> jira and attach the generated bundle.
>>
>>
>> Le dimanche 20 mars 2016, Minudika Malshan 
>> a écrit :
>>
>> Hi,
>>
>> Please give more details about the issue *JENKINS-33091
>> .*
>>
>> It states that *"**We want to simplify the ability to 

Re: [GSOC 2016] Support core plugin improvements

[Arnaud Héritier]

Minudika

For me it seems that your proposal is conform to
http://write.flossmanuals.net/gsocstudentguide/writing-a-proposal/

I think you are ready to submit it

On Thu, Mar 24, 2016 at 4:35 AM, Steve Christou 
wrote:

> Hello Minudika,
>
> I like the proposal! I have no more feedback from my side.
>
> Thanks,
> Steve.
>
> On Wed, Mar 23, 2016 at 6:03 PM Arnaud Héritier 
> wrote:
>
>> Hi Minudika
>>
>>   I have no more feedbacks on my side. I let the others challenge the
>> proposal (especially Steven who is an active maintainer of the plugin).
>>
>> Thanks guys
>>
>> On Wed, Mar 23, 2016 at 9:07 PM, Steve Christou 
>> wrote:
>>
>>> Hello Minudika,
>>>
>>> Thank you for creating this proposal document! I will be reading over
>>> this tonight and providing my comments.
>>>
>>> On Wed, Mar 23, 2016 at 2:59 PM Minudika Malshan 
>>> wrote:
>>>
 Thanks a lot for  your kind help.. :)

 BR

 On Thu, Mar 24, 2016 at 12:09 AM, Oleg Nenashev  wrote:

> I'll try to take a look before the office hours today.
> Arnaud is busy with BreizhCamp, but maybe we will get Steve online.
>
> BR, Oleg
>
> 2016-03-23 17:59 GMT+01:00 Minudika Malshan :
>
>> Hi all,
>>
>> Sorry for spamming. Since the time is running fast I am in a bit of
>> hurry. Could you please let me know if there's any more changes to be 
>> made
>> on my proposal.
>> Then I can make them and submit the finalized proposal to google.
>>
>> Thanks and  regards.
>>
>> On Tue, Mar 22, 2016 at 7:05 PM, Minudika Malshan <
>> minudika...@gmail.com> wrote:
>>
>>> Hi,
>>>
>>> Thanks a lot Oleg and Arnaud for your valuable comments.
>>> I made changes according to your comments. Please have a look and
>>> let me know if there's anything more to be improved or changed.
>>>
>>> Best regards
>>>
>>> On Tue, Mar 22, 2016 at 1:34 PM, Oleg Nenashev <
>>> o.v.nenas...@gmail.com> wrote:
>>>
 The proposal look good, thanks for preparing it!
 I've added several comments to it

 вторник, 22 марта 2016 г., 0:24:25 UTC+1 пользователь Arnaud
 Héritier написал:
>
> Thanks a lot Minudika.
>
> @all please have a look at it and review/comment
>
> cheers
>
> On Tue, Mar 22, 2016 at 12:22 AM, Minudika Malshan <
> minud...@gmail.com> wrote:
>
> Hi all,
>
> Here is the first draft of my proposal [1] . I submitted it also
> to the google's site.
> Please review it and let me know if there's any possible
> improvements to be made on it.
>
> [1]
> https://docs.google.com/document/d/1052sUGFxcDfUHNZFNeQ1FAR61ZB4tJb-GxdW1L3FSC8/edit?usp=sharing
>
> Your comments would be much appreciated.
>
> Thanks a lot.
>
> On Tue, Mar 22, 2016 at 4:05 AM, Arnaud Héritier <
> aher...@gmail.com> wrote:
>
> Really good job Minudika.
> For now I don't see anything to improve.
> I let you officially share it on the dev mailing list to have more
> feedbacks.
> thanks again for the hard work
>
> On Mon, Mar 21, 2016 at 11:01 PM, Minudika Malshan <
> minud...@gmail.com> wrote:
>
> Hi Arnaud,
>
> I created a proposal [1] and published as a draft in the google's
> site as well.
> Could you please review it and suggest improvements which should
> be made.
>
> [1]
> https://docs.google.com/document/d/1052sUGFxcDfUHNZFNeQ1FAR61ZB4tJb-GxdW1L3FSC8/edit?usp=sharing
>
> Thanks and regards,
>
> On Sun, Mar 20, 2016 at 11:07 PM, Arnaud Héritier <
> aher...@gmail.com> wrote:
>
> Yes the goal is to allow to automatically create the ticket in
> jira and attach the generated bundle.
>
>
> Le dimanche 20 mars 2016, Minudika Malshan  a
> écrit :
>
> Hi,
>
> Please give more details about the issue *JENKINS-33091
> .*
>
> It states that *"**We want to simplify the ability to create in
> the OSS tracker. For that the user gives a subject/description of the
> problem, its Jira credentials (or maybe we could use SSO ?) and the 
> options
> to generate a bundle."*
>
> For this, should we implement a feature on support plugin which
> allows user to create tickets in issue tracker remotely?
> If not, how to invoke the support plugin to generate bundle
> remotely from the 

Re: Meet jenkins.io

[domi]

Really nice work!!!
/Domi

> On 24 Mar 2016, at 07:02, R. Tyler Croy  wrote:
> 
> I finished up the final work for migration from https://jenkins-ci.org to
> https://jenkins.io today. The final step of the switchover was to redirect
> non-mapped URLs from jenkins-ci.org over to jenkins.io.
> 
> 
> This project has been a tremendous amount of work with Gus Reiber, Baptiste
> Mathaus, James Dumay, Daniel Beck, Oleg Nenashev  and a number of other
> contributors filling in the new website with CSS, Haml, and most importantly
> AsciiDoc (for documentation!)
> 
> 
> Some of the features of jenkins.io that are important to me, I'd like to 
> share:
> 
> * Visual priority given to the LTS release line (yay)
> * Built-in support for three layers of documentation: solution pages, getting
>   started guides and the "handbook".
> * Visual elements to highlight upcoming events
> * Certificates automated via letsencrypt.org (this is my favorite ;))
> 
> The site is statically generated and contributions are welcome here:
>
> 
> 
> As I mentioned in our last project meeting, migration of other properties such
> as wiki.jenkins-ci.org to the jenkins.io domain will take a bit more time. 
> This
> is an important first step however!
> 
> 
> 
> Cheers
> - R. Tyler Croy
> 
> --
> Code: 
>  Chatter: 
> 
>  % gpg --keyserver keys.gnupg.net --recv-key 3F51E16F
> --
> 
> -- 
> 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/20160324060209.GB15060%40blackberry.coupleofllamas.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/509BAC1C-7F4D-47B6-85BA-5964EF6695DE%40fortysix.ch.
For more options, visit https://groups.google.com/d/optout.

Re: svn.jenkins-ci.org will be SHUT DOWN on March 31

[Torsten Stolpmann]

If this is possible, please do so. My GitHub id is stolp. Please let me 
know how I can support this by adding information or executing 
additional actions.


Regards,

Torsten

On 18.03.2016 17:43, R. Tyler Croy wrote:

(replies inline)

On Fri, 18 Mar 2016, Torsten Stolpmann wrote:


Hi Daniel,

thanks for taking care of us plugin developers, this is much appreciated.

Speaking for the Klaros-Testmanagement Plugin, which is still under active
development, can anybody please tell me what the preferred way of migrating
the plugin away from svn would be?

I am aware of https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins
but I think there must be better ways to achieve this without starting from
zero.




This (https://help.github.com/articles/importing-from-subversion/) might be
something Daniel, or I, could do as jenkinsci github organization
administrators.



On 18.03.2016 09:08, Daniel Beck wrote:


On 17.03.2016, at 17:10, R. Tyler Croy  wrote:


At the end of the month, I will be shutting down svn.jenkins-ci.org

 From the access logs it doesn't appear that there is any traffic going to
svn.jenkins-ci.org that originates from developers. If you are still using
svn.jenkins-ci.org we need to talk about moving your work over to GitHub


There are a few plugins still being developed in SVN with commits in the past 
1.5 years.

* https://wiki.jenkins-ci.org/display/JENKINS/Serenity+Plugin
* http://wiki.jenkins-ci.org/display/JENKINS/Klaros-Testmanagement+Plugin
* http://wiki.jenkins-ci.org/display/JENKINS/VncRecorder+Plugin
* https://wiki.jenkins-ci.org/display/JENKINS/VncViewer+Plugin
* http://wiki.jenkins-ci.org/display/JENKINS/ImageComparison+Plugin

CCing their developers.



--
Torsten Stolpmann
Managing Director

verit Informationssysteme GmbH
Europaallee 10
67657 Kaiserslautern
Germany

Email: stolpm...@verit.de
Phone: +49 631 520 840 00
Fax: +49 631 520 840 01
Web: http://www.verit.de/

--
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/56EBD396.40907%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


- R. Tyler Croy

--
  Code: 
   Chatter: 

   % gpg --keyserver keys.gnupg.net --recv-key 3F51E16F
--



--
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/56ED7A34.3040603%40gmail.com.
For more options, visit https://groups.google.com/d/optout.