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

[Michal Vala]

The project that sounds interesting to me is Simple Pull-Request Job Plugin.
I do not have many ideas about how to start, and I hope we can discuss some
starting points and get some advice.


What will this plugin do? Is it something like this 
https://plugins.jenkins.io/ghprb ?


--
Michal Vala
OpenJDK QE
Red Hat Czech

--
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/9bbb6a01-efa7-d69f-5292-c1b93b1c6b0a%40redhat.com.
For more options, visit https://groups.google.com/d/optout.

New LTS based on 2.107

[Oliver Gondža]

As greed on Governance meeting, the next LTS line will be based on 
latest weekly release. That means, there are no backports to be added 
for .1 provided we do not discover something urgent that would cause us 
to expedite some or reconsider our choice of baseline - which we do not 
anticipate.


Therefore, I would like to encourage all the folks that kindly help us 
test the RCs to use 2.107 weekly(!). Note formally we are still in a 
backportig period and testing is planned to start in two weeks, though 
with the bits already out, there is no reason not to start right away.


Cheers
--
oliver

--
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/682dedfd-56e0-0f5c-93f2-2cb1a515f736%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Draft JEP: Configuration as Code

[Ewelina Wilkosz]

Nice! good luck Eric, and if you need some clarification I can try to 
explain via mail or short online meeting
When is the meetup?

On Wednesday, February 14, 2018 at 9:54:04 PM UTC+1, Eric Smalling wrote:
>
> Sounds like I may need to be the first to try then! :) 
>
> On Wed, Feb 14, 2018 at 2:44 PM, nicolas de loof  > wrote:
>
>> This slides deck is indeed expected to be used for JAM presentations
>> unfortunately it hasn't been used for a recorded session yet
>>
>> 2018-02-14 21:30 GMT+01:00 eric.smalling via Jenkins Developers <
>> jenkin...@googlegroups.com >:
>>
>>> Saw all of the talk about this from the post-FOSDEM hackday work and I'm 
>>> very interested in presenting about it at the DFW JAM this month.   The 
>>> repo links to a slide deck presentation, are those slides up to date and 
>>> something I might use for a JAM presentation?   If so, is there a recording 
>>> of any talks they were used at that I could watch?
>>>
>>> Thanks,
>>> Eric S.
>>>
>>>
>>> On Tuesday, November 7, 2017 at 3:49:59 AM UTC-6, nicolas de loof wrote:

 Hi,

 Some of you who joined Contributor Summit at Jenkins World'17 already 
 know about the resurrecting effort to provide configuration-as-code for 
 Jenkins management (JENKINS-31094)

 Both Praqma and CloudBees have been investigating on this topic last 
 months, and have wrote prototypes to cover this need. As we learned about 
 each other effort we decided to join forces, and make this public as a JEP 
 proposal.

 Our joined prototype is here : 
 https://github.com/jenkinsci/configuration-as-code-plugin
 We also wrote a document to explain our goals and design decisions. We 
 used JEP template 
 
  so 
 we can now propose this for JEP acceptance (I guess this is the right 
 place 
 to do so)

 We'll be happy to hear from you about this.

>>> -- 
>>> 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/5335be02-ae53-4e01-bb87-0088d3351b42%40googlegroups.com
>>>  
>>> 
>>> .
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> -- 
>> 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/6TjlxEqHUEs/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/CANMVJznzO9maEP0_e1%3D%2BxxkaYF%2Bskte%3DxXZAUdq5ybNpONGgng%40mail.gmail.com
>>  
>> 
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> --
> Eric Smalling
> Solution Architect | Docker Inc.
> eric.s...@docker.com 
> 682.233.3742
> 
>@ericsmalling
>

-- 
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/b8050f0d-6e05-4883-97c1-02287ebe6c6c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Joseph P]

Hi Andrei 

A good place to start is by reading the plugin 
tutorial https://wiki.jenkins.io/display/JENKINS/Plugin+tutorial
Or by looking at Jenkins org at Github, here is a simple search for "job" 
https://github.com/search?q=org%3Ajenkinsci+language%3Ajava+job
To see similar job plugins

/Joseph

Den torsdag den 15. februar 2018 kl. 01.43.04 UTC+1 skrev Andrei Vînătoru:
>
> Hello Everyone,
>
> My name is Andrei Vinatoru, and I am currently in the 4th year at the 
> Faculty of Automatic Control and Computer Science, at Politehnica Univerity 
> of Bucharest, Romania. 
> My interests include Java, Continuous Integration, Automation, C, C++, 
> Operating Systems and Networking.
>
> I am familiar with Jenkins, because I worked with it during an internship 
> last summer, and I think this is a good opportunity for me to learn about 
> working on an open-source project and learn more about Jenkins.
> This is my github profile: https://github.com/hntr94 and this is my 
> LinkedIn profile: 
> https://www.linkedin.com/in/andrei-v%C3%AEn%C4%83toru-36b88363/.
>
> The project that sounds interesting to me is Simple Pull-Request Job 
> Plugin.
> I do not have many ideas about how to start, and I hope we can discuss 
> some starting points and get some advice.
>
> Thank you,
> Andrei Vinatoru
>

-- 
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/92a83b78-2bed-45c6-bcfd-b593bef52ea1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Joseph P]

https://jenkins.io/projects/gsoc/gsoc2018-project-ideas/#simple-pull-request-job-plugin
The idea is to create a YAML file similar to Travis' YAML file but it could 
properly be extending that plugin since the infrastructure for being a 
Github bot is already there :)

Den torsdag den 15. februar 2018 kl. 10.15.46 UTC+1 skrev mvala:
>
>
> > The project that sounds interesting to me is Simple Pull-Request Job 
> Plugin. 
> > I do not have many ideas about how to start, and I hope we can discuss 
> some 
> > starting points and get some advice. 
>
> What will this plugin do? Is it something like this 
> https://plugins.jenkins.io/ghprb ? 
>
> -- 
> Michal Vala 
> OpenJDK QE 
> Red Hat Czech 
>

-- 
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/f662eb6d-c82c-4c11-9b61-306b0b70ae33%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Asking for commiter access to amazon-ecs-plugin

[Carlos Sanchez]

Created https://issues.jenkins-ci.org/browse/INFRA-1501 to follow

On Thursday, January 4, 2018 at 6:51:18 PM UTC+1, Jordi Miguel wrote:
>
> Hi all,
>
> It's been more than one month since last message on this thread and we 
> still don't see any progress to unblock development. I'm sure Jan made a 
> good job while he was leading the plugin's development and we thank him for 
> it. Unfortunately he doesn't seem to be active anymore so, can we give 
> commit permissions to someone who's active? On previous messages looks like 
> Douglas Manley was happy to take over the role and I suspect he has not 
> changed his mind.
> I don't care much who ends up being the new maintainer but we're 
> approaching the year mark since the last commit that found its way to 
> master's branch and there are plenty of PR's waiting for a merge that 
> haven't succeed because we don't have anyone with write permissions in the 
> active community.
>
> I hope we can find a solution to this issue soon. If there is anything I 
> can do to help resolve problems please don't hesitate to ask.
>
>
> Thanks,
> Jordi
>
> El miércoles, 29 de noviembre de 2017, 21:39:40 (UTC+1), Yaramada Surya 
> tej escribió:
>>
>> Hi Mathus,
>>   It would be great if any one can change the maintainer 
>> of this plugin to Douglas as he is willing to took it so that we can 
>> utilize this plugin , many of us are waiting to get this pull request 
>> merged.
>>
>>
>> Thanks
>> Surya
>>
>> On Thursday, 7 September 2017 17:33:57 UTC-4, Baptiste Mathus wrote:
>>>
>>> Hello,
>>> Seems like Jan is not active either these days or anymore at all.
>>>
>>> So either you can see if you want to adopt this plugin (in that case 
>>> please follow the process described on the wiki), or this is likely to stay 
>>> this way until someone does I suspect.
>>>
>>> Baptiste
>>>
>>> Le 7 sept. 2017 17:22, "Surya yaramada`"  a écrit :
>>>
 Hi,
  I am sorry for interrupting again but can I please know if there 
 is a chance to merge the pull requests for AMAZON-ECS plugin.


 Thanks 
 Surya

 On Thursday, August 24, 2017 at 4:12:47 PM UTC-4, Daniel Beck wrote:
>
>
> > On 24. Aug 2017, at 22:09, Surya yaramada`  
> wrote: 
> > 
> >  Can I get any updates on this? 
> > 
>
> There's no need for multiple emails per day. Give him a week or so. 
> Jan may well be on vacation. 
>
> -- 
 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/4f569b34-cfb3-427f-adc3-40406f9c6b3e%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/f20148e3-4ce6-49b9-9acb-c432a50298d4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Michal Vala]

On 02/15/2018 10:33 AM, Joseph P wrote:

https://jenkins.io/projects/gsoc/gsoc2018-project-ideas/#simple-pull-request-job-plugin
The idea is to create a YAML file similar to Travis' YAML file but it could
properly be extending that plugin since the infrastructure for being a
Github bot is already there :)


Oh, I see. I didn't know about that page. Thanks



Den torsdag den 15. februar 2018 kl. 10.15.46 UTC+1 skrev mvala:




The project that sounds interesting to me is Simple Pull-Request Job

Plugin.

I do not have many ideas about how to start, and I hope we can discuss

some

starting points and get some advice.


What will this plugin do? Is it something like this
https://plugins.jenkins.io/ghprb ?

--
Michal Vala
OpenJDK QE
Red Hat Czech





--
Michal Vala
OpenJDK QE
Red Hat Czech

--
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/39cc09a8-ece1-f1e6-7d87-aa99d0bacf82%40redhat.com.
For more options, visit https://groups.google.com/d/optout.

[GSoC 2018] [Student Introduction] Code Coverage API Plugin

[Rajgure Abhishek Sanjay Abhishek Sanjay]

Hi
  
 I am Abhishek , currently i am working in SAP labs as a software 
developer intern and for development we use jenkins, gerrit etc. I am very 
familiar with the jenkins and also experienced unit testing using Junit . 
While working I also thought about merging the result of cobertura , jacoco 
etc .
I am thinking of developing a dashboard where all merged  result can be 
seen and analysis can be done there.
I am in final year of engineering and this my last chance for GSOC.

Thanks,
Abhishek  Rajgure

 my website 
 linkedin 
 github 


-- 
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/a5a1a933-7b58-461d-a5e6-d1e318eaf94c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[martinda]

Hello Andrei and al,

The simple pull-request plugin is described in more details in the link 
kindly posted by Joseph P (thank you Joseph). I have added some ideas to 
the detailed proposal 

.

Regarding student participation, you should read the information for 
students: https://jenkins.io/projects/gsoc/students/

It can help to look at existing plugins to learn how to write plugins. I 
will shamelessly points to a plugin I previously mentored as I think its 
code is well organized and it has lots of unit tests: the external 
workspace manager plugin 
. But I am 
sure there are other good plugins out there that I am not familiar with.

I am hoping the plugin can work with Bitbucket Server, Cloud and Github 
(all three). I am also proposing that certain report types be supported by 
convention. For example, if JUnit XML Reports exist in a conventional 
location, they should automatically be published.

The plugin is different than existing pull-request plugins in a couple of 
ways. My idea is that the Simple Pull-Request Plugin does not detect 
branches and does not create a job for each pull-request automatically. 
Instead, all the pull-requests destined to a given branch run in the same 
job. This way the job has a history of all the pull-requests destined to a 
given branch. So it is one job per destination branch. Also, the plugin 
does not automatically detect pull-requests (it does not poll). Instead 
jobs wait to be triggered externally. For example a build could be 
triggered from the command line (as rudimentary as curl), or it could be 
triggered from Bitbucket using the pull-request notifier 
.
 
I am not sure whether users should create the jobs themselves, or if there 
should be some kind automation when it comes to creating jobs. I see the 
operation of the build, and the jobs creation as two independent 
activities. The focus of the plugin as proposed so far is to implement the 
operation of the build.

Of course this proposal welcomes comments and suggestions from the 
community.

Best,
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/0f7ac3a7-0279-444c-88fb-dd2b7abb705d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Surya Gaddipati]

Hey I worked on something similar ( actually exactly the same thing looks 
like)

https://github.com/groupon/DotCi 

I would like if to help you if you need anything with your project 

On Wednesday, February 14, 2018 at 6:43:04 PM UTC-6, Andrei Vînătoru wrote:
>
> Hello Everyone,
>
> My name is Andrei Vinatoru, and I am currently in the 4th year at the 
> Faculty of Automatic Control and Computer Science, at Politehnica Univerity 
> of Bucharest, Romania. 
> My interests include Java, Continuous Integration, Automation, C, C++, 
> Operating Systems and Networking.
>
> I am familiar with Jenkins, because I worked with it during an internship 
> last summer, and I think this is a good opportunity for me to learn about 
> working on an open-source project and learn more about Jenkins.
> This is my github profile: https://github.com/hntr94 and this is my 
> LinkedIn profile: 
> https://www.linkedin.com/in/andrei-v%C3%AEn%C4%83toru-36b88363/.
>
> The project that sounds interesting to me is Simple Pull-Request Job 
> Plugin.
> I do not have many ideas about how to start, and I hope we can discuss 
> some starting points and get some advice.
>
> Thank you,
> Andrei Vinatoru
>

-- 
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/98db4178-3a17-43a2-bbb7-0f11198448f7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Request to become maintainer for docker-custom-build-environment-plugin

[Jesse Glick]

Posting here was correct. I was just adding a parenthetical comment
about extending a bug fix I had developed to work with this plugin as
well; you can disregard my message.

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

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

[Jesse Glick]

I posted a comment to the doc. The proposal suggests something far
more complex (and ultimately limited) than what you can already do
very easily with a minor extension to Pipeline.

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

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

[martinda]

Ah, I just saw Jesse's comment in the proposal doc. I need to do more 
research on multi-branch and organization folders. Last time I tried was 
already a few years ago.

On Thursday, February 15, 2018 at 9:55:57 AM UTC-5, Jesse Glick wrote:
>>
>> I posted a comment to the doc. The proposal suggests something far 
>> more complex (and ultimately limited) than what you can already do 
>> very easily with a minor extension to Pipeline. 
>>
>

-- 
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/41ae225b-a8dd-4e9d-bf21-c76a7e6315d2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Draft JEP: Configuration as Code

['Eric Smalling' via Jenkins Developers]

The next meetup is a week from today, not sure I can pull of researching enough 
on this to present on it that fast though.  Next month is already booked with 
A.Bayer coming in town so the next opportunity would be some time in mid-late 
April.


> On Feb 14, 2018, at 2:44 PM, nicolas de loof  wrote:
> 
> This slides deck is indeed expected to be used for JAM presentations
> unfortunately it hasn't been used for a recorded session yet
> 
> 2018-02-14 21:30 GMT+01:00 eric.smalling via Jenkins Developers 
> >:
> Saw all of the talk about this from the post-FOSDEM hackday work and I'm very 
> interested in presenting about it at the DFW JAM this month.   The repo links 
> to a slide deck presentation, are those slides up to date and something I 
> might use for a JAM presentation?   If so, is there a recording of any talks 
> they were used at that I could watch?
> 
> Thanks,
> Eric S.
> 
> 
> On Tuesday, November 7, 2017 at 3:49:59 AM UTC-6, nicolas de loof wrote:
> Hi,
> 
> Some of you who joined Contributor Summit at Jenkins World'17 already know 
> about the resurrecting effort to provide configuration-as-code for Jenkins 
> management (JENKINS-31094)
> 
> Both Praqma and CloudBees have been investigating on this topic last months, 
> and have wrote prototypes to cover this need. As we learned about each other 
> effort we decided to join forces, and make this public as a JEP proposal.
> 
> Our joined prototype is here : 
> https://github.com/jenkinsci/configuration-as-code-plugin 
> 
> We also wrote a document to explain our goals and design decisions. We used 
> JEP template 
> 
>  so we can now propose this for JEP acceptance (I guess this is the right 
> place to do so)
> 
> We'll be happy to hear from you about this.
> 
> -- 
> 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/5335be02-ae53-4e01-bb87-0088d3351b42%40googlegroups.com
>  
> .
> 
> For more options, visit https://groups.google.com/d/optout 
> .
> 
> 
> -- 
> 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/6TjlxEqHUEs/unsubscribe 
> .
> To unsubscribe from this group and all its topics, send an email to 
> jenkinsci-dev+unsubscr...@googlegroups.com 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/CANMVJznzO9maEP0_e1%3D%2BxxkaYF%2Bskte%3DxXZAUdq5ybNpONGgng%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/5E6C9341-41A0-40D5-B479-EF231AE900C0%40docker.com.
For more options, visit https://groups.google.com/d/optout.

Re: Evergreen packaging for Jenkins Essentials

[Carlos Sanchez]

yay! +1

I agree with previous comments that it is not ideal to run multiple
processes and that in a kubernetes world this would possibly be a Pod with
two containers, but I think it's important to get something out and
iteratively improve.
A decent user experience today means just one container and we can always
had a Pod definition for Kubernetes users if we find that useful in the
future.

Regarding different environment autodetection it would be nice, but having
a way to manually select it (system property, env var,...) would be good
enough for now



On Wed, Feb 7, 2018 at 10:28 PM, R. Tyler Croy  wrote:

> In the same vein as my previous email, I've written up a design document
> which
> outlines the current approach for packaging I intend to use for Jenkins
> Essentials:
>
> https://github.com/jenkinsci/jep/tree/master/jep/301
>
> I think it should be fairly straight-forward and understandable why I'm
> taking
> the approach described, but if there any ambiguity do let me know.
>
> Please take a look at the document and let me know what you think on this
> thread :)
>
>
>
> Cheers
> - R. Tyler Croy
>
> --
>  Code: 
>   Chatter: 
>  xmpp: rty...@jabber.org
>
>   % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F
> --
>
> --
> 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/ms
> gid/jenkinsci-dev/20180207212838.ndyahjf7psu5obk2%
> 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/CALHFn6OZTJSNnA3JZ1Er4XvpiEW55LpfR73Zz5D_x%3D9OSG5i5Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Accelerating Jenkins development with Jenkins Essentials

[Baptiste Mathus]

+1, very exciting to make Jenkins operatable by newcomers in a matter of
minutes. Having had very recently to drive a newbie to use Jenkins, even if
he was very motivated, I think this is a great initiative. The flexibility
of Jenkins is a great strength for advanced users, but a real difficulty
for newcomers.

Though I agree using a watchdog tool like supervisord is not the official
and best way to provide a Docker image, at the same time I agree this is a
powerful way to make the experience very easy OOTB. I did that in the past
for SonarQube, and it worked quite well for our usage.

About supervisord specifically though, mostly a NIT/request for
clarification: I wonder if the JEP should specify it? I read the reasoning
 and I
understand this can save time and so on to start that work, but for
instance if we discover a better alternative now or later, should a part of
that JEP which somehow looks like an implementation detail (we mainly need
to express we require a watchdog/restart tool don't we). Also/or this is
typically a component that could be replaced later if something better
surfaces or so?
Also, adding another language dependency (python) when you already plan to
have the evergreen client in nodejs might make the image bigger than it
could be. But well, back to my previous point, this is something that can
anyway be improved/changed over time.

Thanks!

2018-02-06 17:02 GMT+01:00 R. Tyler Croy :

>
> After pounding my head against my whiteboard for a couple months, I'm
> finally
> ready to talk about this idea which was first discussed at Jenkins World
> 2017
> in San Francisco.
>
> At the Contributor Summit we held, Kohsuke challenged us to make Jenkins
> easy
> enough for an end-user to go from "zero" (downloading Jenkins) to
> continuously
> delivering a project in under 5 clicks and under 5 minutes.
>
> Jenkins Essentials has this goal in mind, with an additional goal of making
> Jenkins development more efficient.
>
> I have proposed a draft of JEP-300 which outlines the problem domain and
> overview of Jenkins Essentials more thoroughly
>
> rendered: https://github.com/rtyler/jep/tree/essentials-overview-300/j
> ep/300
> pull request to jenkinsci/jep: https://github.com/jenkinsci/jep/pull/48
>
>
> To be successful with Jenkins Essentials, I'm endeavouring to improve
> pre-release verification as well as post-release monitoring. Some of the
> initial tasks that my colleague Raul and I are tackling can be found on
> this
> board: https://issues.jenkins-ci.org/secure/RapidBoard.jspa?rapidView=396
>
>
> I'm still sketching out the Developer Experience aspects of this in another
> thread once I have some thoughts written down.
>
>
> Please take a look at the document and let me know what you think on this
> thread :)
>
>
>
> Cheers
> - R. Tyler Croy
>
> --
>  Code: 
>   Chatter: 
>  xmpp: rty...@jabber.org
>
>   % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F
> --
>
> --
> 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/ms
> gid/jenkinsci-dev/20180206160253.dkz7whf7h74bda64%
> 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/CANWgJS7hNzusookSN%2Btyw_ySc-d-7O_i%2Br9P8TcNBy2kx4UgZA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: change assembly version plugin

[Baptiste Mathus]

+1 obviously. Thanks Alex!

2018-02-14 9:41 GMT+01:00 Oleg Nenashev :

> +1 from me.
> Let me know if you need any help with reviews.
>
> вторник, 13 февраля 2018 г., 22:12:06 UTC+1 пользователь slide написал:
>>
>> Hello,
>>
>> I would like to take over maintaining the change assembly version plugin
>> for Jenkins. I have CC'd lkobus who is the current maintainer to ask for
>> permission to take over the plugin. There are several PR's that people
>> would like merged and I am willing to take over and maintain the plugin and
>> review PR's and so forth. I maintain a few other plugins, so I have some
>> knowledge of doing.
>>
>> Thanks,
>>
>> Alex Earl
>>
>> --
> 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/8d92aaf7-6d99-4d8e-b87b-1a1cd72057ec%
> 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/CANWgJS4B2%3DfjWY5FfsFTostj7F1T2rQUKQcYrK30%3D7-josoz1w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Accelerating Jenkins development with Jenkins Essentials

[Baptiste Mathus]

Le 15 févr. 2018 21:29, "Baptiste Mathus"  a écrit :

+1, very exciting to make Jenkins operatable by newcomers in a matter of
minutes. Having had very recently to drive a newbie to use Jenkins, even if
he was very motivated, I think this is a great initiative. The flexibility
of Jenkins is a great strength for advanced users, but a real difficulty
for newcomers.

Though I agree using a watchdog tool like supervisord is not the official
and best way to provide a Docker image, at the same time I agree this is a
powerful way to make the experience very easy OOTB. I did that in the past
for SonarQube, and it worked quite well for our usage.

About supervisord specifically though, mostly a NIT/request for
clarification: I wonder if the JEP should specify it? I read the reasoning
 and I
understand this can save time and so on to start that work, but for
instance if we discover a better alternative now or later, should a part of
that JEP which somehow looks like an implementation detail (we mainly need
to express we require a watchdog/restart tool don't we). Also/or this is
typically a component that could be replaced later if something better
surfaces or so?
Also, adding another language dependency (python) when you already plan to
have the evergreen client in nodejs might make the image bigger than it
could be. But well, back to my previous point, this is something that can
anyway be improved/changed over time.


Please ignore that part about the python runtime dependency since it's
already been discussed/addressed in the other thread I hadn't read
thoroughly yet.


Thanks!

2018-02-06 17:02 GMT+01:00 R. Tyler Croy :

>
> After pounding my head against my whiteboard for a couple months, I'm
> finally
> ready to talk about this idea which was first discussed at Jenkins World
> 2017
> in San Francisco.
>
> At the Contributor Summit we held, Kohsuke challenged us to make Jenkins
> easy
> enough for an end-user to go from "zero" (downloading Jenkins) to
> continuously
> delivering a project in under 5 clicks and under 5 minutes.
>
> Jenkins Essentials has this goal in mind, with an additional goal of making
> Jenkins development more efficient.
>
> I have proposed a draft of JEP-300 which outlines the problem domain and
> overview of Jenkins Essentials more thoroughly
>
> rendered: https://github.com/rtyler/jep/tree/essentials-overview-300/j
> ep/300
> pull request to jenkinsci/jep: https://github.com/jenkinsci/jep/pull/48
>
>
> To be successful with Jenkins Essentials, I'm endeavouring to improve
> pre-release verification as well as post-release monitoring. Some of the
> initial tasks that my colleague Raul and I are tackling can be found on
> this
> board: https://issues.jenkins-ci.org/secure/RapidBoard.jspa?rapidView=396
>
>
> I'm still sketching out the Developer Experience aspects of this in another
> thread once I have some thoughts written down.
>
>
> Please take a look at the document and let me know what you think on this
> thread :)
>
>
>
> Cheers
> - R. Tyler Croy
>
> --
>  Code: 
>   Chatter: 
>  xmpp: rty...@jabber.org
>
>   % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F
> --
>
> --
> 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/ms
> gid/jenkinsci-dev/20180206160253.dkz7whf7h74bda64%40blackber
> ry.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/CANWgJS6mFmgu3CBiWGc0tja9tKt%2BOGtbt24EpSVFzWFi1CX0Eg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

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

[Jesse Glick]

On Thu, Feb 15, 2018 at 10:19 AM, martinda  wrote:
> My users will never write a Jenkinsfile, ever. But I
> was able to get them to specify a (very) small YAML file.
>
> Maybe you are suggesting that this should be implemented as an open-source
> Pipeline library and Jenkinsfile

You can of course do that, though then you still need to have some
kind of boilerplate:

---%<--- Jenkinsfile
library('github.com/whatever/jenkins-yaml-lib').run('jenkins.yaml')
--->%---

CloudBees users can eliminate the need for even that using

https://go.cloudbees.com/docs/cloudbees-documentation/cje-user-guide/index.html#pipeline-custom-factories

Or you can write a small plugin which implements the same
`AbstractWorkflowBranchProjectFactory` /
`AbstractWorkflowMultiBranchProjectFactory` extension points and bakes
in an opinionated file name and script.

I am not saying that is the only way to accomplish your goal, but it
is certainly the easiest. You would get support for GitHub & BitBucket
(including pull requests, webhooks, and organization folders) for
free, as well as visualization via Blue Ocean and so on. (I suppose
you could even build an analogue to
https://github.com/jenkinsci/blueocean-plugin/tree/master/blueocean-pipeline-editor
if you wanted, though I do not know much about that.)

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

Re: Evergreen packaging for Jenkins Essentials

[R. Tyler Croy]

(replies inline)

On Thu, 15 Feb 2018, Carlos Sanchez wrote:

> yay! +1
> 
> I agree with previous comments that it is not ideal to run multiple
> processes and that in a kubernetes world this would possibly be a Pod with
> two containers, but I think it's important to get something out and
> iteratively improve.
> A decent user experience today means just one container and we can always
> had a Pod definition for Kubernetes users if we find that useful in the
> future.
> 
> Regarding different environment autodetection it would be nice, but having
> a way to manually select it (system property, env var,...) would be good
> enough for now

Contemplating jglick's feedback further, I am more in agreement with his point
about providing disparate "flavors" to tailor the experience further for
user-success on cloud environments such as Azure or AWS. To that end I've
updated JEP-300: https://github.com/jenkinsci/jep/pull/58

The detail which makes this important is the suite of plugins necessary to
include "out of the box" to provide the Automatic Sane Defaults will change
depending on the environment. If we can detect AWS, then we can make sure we're
downloading the S3 plugin, for example, but on Azure we wouldn't want to bloat
the user's environment with it. Rather, Azure users should have the Azure VM
Agents and Azure Container Agents plugin included by default.


I will target AWS with the first "flavor" and then we can see where that takes
us.



Thanks for the feedback Carlos!



Cheers
- R. Tyler Croy

--
 Code: 
  Chatter: 
 xmpp: rty...@jabber.org

  % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F
--

-- 
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/20180215174522.ewqpuvbmjxchuj3j%40blackberry.coupleofllamas.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: PGP signature