Re: What resources is Cloudbees allocating to Blue Ocean maintenance/development?

[Kohsuke Kawaguchi]

Thanks for your positive words and the suggestions.

Speaking as myself, not necessarily representing CloudBees' collective
opinion, the idea of one person playing a leadership role is quite
consistent with what we've been generally doing lately in the Jenkins
project -- plugin maintainers, officers, SIG leaders, and JEP sponsors to
name a few. I think its effect of creating an information flow has been
useful. So I'm a big fan of that.


On Wed, Dec 26, 2018 at 9:30 PM Craig Rodrigues  wrote:

> Kohsuke,
>
> Thanks for your honest and open response about my query about Cloudbees
> resources allocated to Blue Ocean.
>
> I am very happy with Cloudbees' investment in Blue Ocean.  When I show the
> UI to co-workers
> and managers, they are impressed.  That in turn makes it easier to promote
> the use of Pipeline
> and other "modern" Jenkins technologies in organizations that are using
> Jenkins, but may not be on the latest stuff.
>
> In terms of Blue Ocean, I have seen initially a very active and engaging
> involvement from Cloudbees in terms
> of kicking off the project and carrying it along.  Unfortunately, the
> involvement from Cloudbees has become much
> more passive.  From what you have described, there are a few passionate
> and talented developers
> at Cloudbees who are holding the fort on Blue Ocean.  I am grateful for
> the enthusiasm, skill, and motivation
> of these developers.  It is always a pleasure to interact with Cloudbees
> developers.
>
> However, my concern is that if the current mode is "holding the fort",
> then the appearance from the
> outside is that Blue Ocean is being passionately supported by a few
> developers, but it is not
> a high priority from Cloudbees management, and the developers are not
> being actively supported or given a clear
> direction/roadmap to work on Blue Ocean.  In other companies, I have seen
> where this mode of operation
> can lead to burnout and frustration on behalf of developers.
>
> I understand that Cloudbees is focusing on a lot of technical areas which
> are very important for the
> future of the Jenkins ecosystem.  I'm glad to see this.  I also understand
> that resources are limited,
> and deciding what resources to allocate to what project can be tricky.
>
> Blue Ocean is a significant piece of technical work, and due to its
> complexity, I think Cloudbees
> should continue to have a leadership role in its ongoing
> maintenance/bugfixes, and evolution.
> There just are not enough developers in the open source Jenkins community
> who
> are versed enough in modern Javascript/NodeJS to make significant
> contributions to Blue Ocean.
>
> I would like to suggest the following:
>
> 1.  Cloudbees should select one person, either a developer or manager to
> "own" Blue Ocean.
> 2.  The owner of Blue Ocean should make regular appearances (maybe once
> week) in the Blue Ocean gitter channel:
> https://gitter.im/jenkinsci/blueocean-plugin
>  to get an idea what problems the community is having with Blue Ocean,
> and also
>  give periodic updates on future plans, roadmap, etc.
> 3.  All bugs in JIRA should be assigned to this owner of Blue Ocean.
> There should be no unassigned Blue Ocean bugs.
> Also, bugs assigned to previous owners, such as James Dumay, should be
> assigned to the active owner.
> 4.  This owner should triage bugs into separate piles: easy to fix, hard
> to fix, won't fix, etc.
> 5.  Cloudbees should assign 1 or 2 developers to officially work on Blue
> Ocean part-time, say 1 to 2 days a week, to
>  work on the Blue Ocean bug backlog.  If other Cloudbees developers
> pitch in and help out, that's awesome, but
>  there should be at least a few developers officially assigned to Blue
> Ocean, and aware of the roadmap.
> 6.  If possible, Cloudbees should assign a UI/UX person for maybe 1 day a
> week to oversee overall changes to Blue Ocean, and make sure
>  that any changes improve UI and usability, and don't become a new
> kitchen sink.
>
> In terms of the work that needs to be done on Blue Ocean, my gut feeling
> is that there are two categories:
>
> 1.  Maintenance/bugfixes and minor filling of "pot holes" to bring Blue
> Ocean to feature parity with the Classic UI.
> 2.  Major interface changes to the Blue Ocean UI.  For example, adding
> customized test reports to Blue Ocean test report viewer:
> https://issues.jenkins-ci.org/browse/JENKINS-50589
>
> If Cloudbees can at least allocate some resources to officially work on
> Category 1 at a low level of activity,
> that would be an improvement over the current situation.
>
> Thanks again for listening to my feedback.
>
> Feel free to contact me off the mailing lists for further feedback.
> I am also in the SF Bay Area, and can drop by the Cloudbees office to chat
> if you want.
> A few years ago, I dropped by the Cloudbees office to chat with Andrew
> Bayer about
> Pipeline.
>
> --
> Craig
>
>
> On Thu, Dec 20, 2018 at 5:41 PM Kohsuke Kawaguchi <
> 

Re: [Jenkins GSoC] - Budget status update for 2018 + swag delivery expenses discussion

[Oleg Nenashev]

Hi Kohsuke,

Yes, in GSoC we would be interested to have some budgeting freedom for such
small transactions.
There is a JEP-8  for
it. If you have some bandwidth, it would be great if you could review this
JEP or to assign a BDFL delegate there (likely somebody from the Board or
GSoC Org Admins).

This particular request has been approved at the today's governance meeting

BR, Oleg


On Thu, Jan 3, 2019 at 12:50 AM Kohsuke Kawaguchi  wrote:

> Thanks for the details, Oleg.
>
> As a board, my continued guidance is that the money the project has raised
> is doing no good sitting in SPI, so we should look for ways to use it to
> make positive impacts. If we find a great way to spend money and empties
> the balance, that's kind of great because we have a great reason to go
> raise more money from the community.
>
> As long as we are aligned with that goal, for the kind of dollar amount we
> are talking about (~500USD), I think you have a large degree of leeway
> here.
>
> On Thu, Dec 27, 2018 at 4:03 PM Oleg Nenashev 
> wrote:
>
>> Dear all,
>>
>> Please find the Jenkins GSoC budget status update for 2018. You can find
>> my previous report from July 18 here
>> .
>> Please note that these estimations are rather approximate ones. GSoC does
>> not have a separate budget in the Jenkins project until JEP-8
>>  is accepted.
>>
>>- Balance on 01.01.2018: *2387.34 USD*
>>- Income in 2018: *4200 USD* in September according to GSoC Org
>>Payments
>>
>>- Expenses in 2018: *~3750 USD*. Number is approximate (currency
>>rates, etc.), because we do not know exact numbers until SPI 2018 report 
>> is
>>published
>>- 1902.94 CHF: DevOps World - Jenkins World sponsorship for Pham Vu
>>   Tuan:
>>   - 951.26 CHF - GSoC Mentor Summit - Oleg Nenashev
>>   - 791.26 CAD - GSoC Mentor Summit - Martin d'Anjou:
>>   - 254.41 USD - GSoC Mentor Summit - Jeff Pearce: . The report has
>>   not been submitted to SPI yet
>>   - Estimated GSoC balance on 01.01.2019:
>> *2837.34 USD *
>>
>> So, finally we did not need extra budget as it was approved in July (
>> thread
>> ).
>> Reasons: 1 project was failed and did not get conference travel
>> sponsorship. For the third project we still have some money reserved should
>> the student decide to go to a Jenkins conference and present his work (up
>> to 1000 USD). Even with that, we have more than 1800 USD reserved for the
>> next year.
>>
>> I would like to spend some of that budget on sending swag to GSoC 2018
>> participants who have not yet received the swag at DevOps World - Jenkins
>> World and other events (~15 recipients). It was originally planned for GSoC
>> 2018, but unfortunately it was significantly delayed (my fault). It would
>> be also great to print some extra Jenkins GSoC stickers so that we could
>> use them for future events.
>>
>> My plan is to have a detailed budget calculation for swag by Monday so
>> that it could be discussed at the governance meeting. My rough estimation
>> is that it is going to be around 500USD, including printing and delivery
>> costs. I would appreciate feedback about feasibility of such expense. WDYT?
>>
>> Best regards,
>> Oleg Nenashev
>> Jenkins GSoC Org Admin
>>
>>
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "jenkinsci-gsoc-all-public" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jenkinsci-gsoc-all-public+unsubscr...@googlegroups.com.
>> To post to this group, send email to
>> jenkinsci-gsoc-all-pub...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-gsoc-all-public/CAPfivLC7d142-gpk6sk%3DGe1jZxDtY1sD3Afog5ZP%2B%3D_f%2B%3D%2Bswg%40mail.gmail.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> Kohsuke Kawaguchi
>

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

Re: [Jenkins GSoC] - Budget status update for 2018 + swag delivery expenses discussion

[Kohsuke Kawaguchi]

Thanks for the details, Oleg.

As a board, my continued guidance is that the money the project has raised
is doing no good sitting in SPI, so we should look for ways to use it to
make positive impacts. If we find a great way to spend money and empties
the balance, that's kind of great because we have a great reason to go
raise more money from the community.

As long as we are aligned with that goal, for the kind of dollar amount we
are talking about (~500USD), I think you have a large degree of leeway
here.

On Thu, Dec 27, 2018 at 4:03 PM Oleg Nenashev 
wrote:

> Dear all,
>
> Please find the Jenkins GSoC budget status update for 2018. You can find
> my previous report from July 18 here
> .
> Please note that these estimations are rather approximate ones. GSoC does
> not have a separate budget in the Jenkins project until JEP-8
>  is accepted.
>
>- Balance on 01.01.2018: *2387.34 USD*
>- Income in 2018: *4200 USD* in September according to GSoC Org
>Payments
>
>- Expenses in 2018: *~3750 USD*. Number is approximate (currency
>rates, etc.), because we do not know exact numbers until SPI 2018 report is
>published
>- 1902.94 CHF: DevOps World - Jenkins World sponsorship for Pham Vu
>   Tuan:
>   - 951.26 CHF - GSoC Mentor Summit - Oleg Nenashev
>   - 791.26 CAD - GSoC Mentor Summit - Martin d'Anjou:
>   - 254.41 USD - GSoC Mentor Summit - Jeff Pearce: . The report has
>   not been submitted to SPI yet
>   - Estimated GSoC balance on 01.01.2019:
> *2837.34 USD *
>
> So, finally we did not need extra budget as it was approved in July (
> thread ).
> Reasons: 1 project was failed and did not get conference travel
> sponsorship. For the third project we still have some money reserved should
> the student decide to go to a Jenkins conference and present his work (up
> to 1000 USD). Even with that, we have more than 1800 USD reserved for the
> next year.
>
> I would like to spend some of that budget on sending swag to GSoC 2018
> participants who have not yet received the swag at DevOps World - Jenkins
> World and other events (~15 recipients). It was originally planned for GSoC
> 2018, but unfortunately it was significantly delayed (my fault). It would
> be also great to print some extra Jenkins GSoC stickers so that we could
> use them for future events.
>
> My plan is to have a detailed budget calculation for swag by Monday so
> that it could be discussed at the governance meeting. My rough estimation
> is that it is going to be around 500USD, including printing and delivery
> costs. I would appreciate feedback about feasibility of such expense. WDYT?
>
> Best regards,
> Oleg Nenashev
> Jenkins GSoC Org Admin
>
>
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "jenkinsci-gsoc-all-public" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-gsoc-all-public+unsubscr...@googlegroups.com.
> To post to this group, send email to
> jenkinsci-gsoc-all-pub...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-gsoc-all-public/CAPfivLC7d142-gpk6sk%3DGe1jZxDtY1sD3Afog5ZP%2B%3D_f%2B%3D%2Bswg%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
-- 
Kohsuke Kawaguchi

-- 
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/CAN4CQ4w0sk8ZNFRaP9W4xfT314vvuP_%2Bx_RJ7PGpX0F%3DrBt7gw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: The future of LTS certification

[Sahil Khan]

Hello,
Last year in 2018 I applied for the similar GSoC Project for Improvement of 
ATH.Here is the link to my GSoC Proposal of 2018. 

I would like to start contributing to the project from now as it is nearly 
impossible to complete the whole project in GSoC timeline.
I would like to get some suggestons on like how to start the project and if 
going for container technology then which one would be the best. 

-- 
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/7eb4c77e-99ea-40f9-8c18-146b63921343%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Request to join organization

[Baptiste Mathus]

+1 from me.

Le jeu. 27 déc. 2018 à 12:14,  a écrit :

> Hi all,
>
> I am Francisco Javier Fernández González, currently engineer at CloudBees.
> During the last year I've been collaborating with some work of the
> community, becoming co-maintainer of the Jenkinsfile-runner project
>  with Oleg Nenashev
>  and Evaristo Gutiérrez
> , and maintainer of Folders plugin
> . I would like to
> continue collaborating in the maintenance of Jenkins and its ecosystem of
> plugins, and in terms of easing my collaborations and reviews, I would like
> to become a member of the organization getting the merge permissions for
> the core. Would it be possible?
>
> Just in case you're interested in knowing more from me:
>
>- My Jenkins JIRA user is *fcojfernandez
>*
>- My github user is *fcojfernandez *
>- My contributions to the jenkinsci organization:
>
> https://github.com/pulls?utf8=%E2%9C%93=is%3Apr+author%3Afcojfernandez+archived%3Afalse+user%3Ajenkinsci+
>   - Specific contributions to jenkins-core:
>   
> https://github.com/jenkinsci/jenkins/pulls?utf8=%E2%9C%93=is%3Apr+author%3Afcojfernandez+
>
>
> Best Regards!
>
> --
> 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/3a997e95-4d44-4933-bc9e-a92c1a574644%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/CANWgJS6mb7ztsLXZ4306XN%2B-%2BcOriAZqnZJ5-XdDoL-rs-cCMg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Be able to merge on core

[Baptiste Mathus]

I agree with this request.

Ramon has helped a lot also recently on ATH and a few other components
,
many reviewed and merged by Oliver. So I believe this request is reasonable.

Le mer. 2 janv. 2019 à 11:02, Manuel Ramón León Jiménez <
manuel.ramon.leon.jime...@gmail.com> a écrit :

>
> Hello guys, happy new year.
>
> I'm working at CloudBees on the open source size and due to the limited
> bandwith from Oleg and to gain more velocity in some developments,
> specially on *java11*, I believe it could be interesting that you allow
> me to have write permission on Jenkins core and jenkins infra github repos
> to be able to merge some PRs.
>
> If it helps:
>
> I've being contributing with some PRs already merged to the core as well
> as reviewed some other ones:
>
>- PRs merged into core:
>- https://github.com/jenkinsci/jenkins/pull/3816
>   - https://github.com/jenkinsci/jenkins/pull/3769
>   - https://github.com/jenkinsci/jenkins/pull/3768
>   - https://github.com/jenkinsci/jenkins/pull/3718
>   - https://github.com/jenkinsci/jenkins/pull/3695
>   - https://github.com/jenkinsci/jenkins/pull/3648
>- PRs reviewed in core:
>- https://github.com/jenkinsci/jenkins/pull/3786
>   - https://github.com/jenkinsci/jenkins/pull/3795
>   - https://github.com/jenkinsci/jenkins/pull/3797
>   - https://github.com/jenkinsci/jenkins/pull/3807
>   - https://github.com/jenkinsci/jenkins/pull/3804
>   - https://github.com/jenkinsci/jenkins/pull/3815
>   - https://github.com/jenkinsci/jenkins/pull/3818
>
>
> I'm also a maintainer of two plugins (
> plugin-apache-httpcomponents-client-4-api
> 
> and plugin-jdk-tool
> 
> ).
>
> My user id in all systems (github, jenkins jira, ...) is: *mramonleon*
>
> Thank you, kind regards.
>
> --
> 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/7fedc96c-5b22-4234-a2b5-b7afd5dc688a%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/CANWgJS7yLsQ3zYav%2BmktD-cu07_Q20Uu1ePAQogZxbmgkDzppw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Backporting for LTS 2.150.2 completed

[Oliver Gondža]

Backporting is complete and the RC will be published tomorrow unless 
there are objections on today's meeting.


Postponed:
JENKINS-48775   CriticalTue, 20 Nov 2018 
14:53:06 +
Proxy authentication error 407 even if 'check proxy' works
https://issues.jenkins-ci.org/browse/JENKINS-48775
Fixed:
JENKINS-16867   Major   Tue, 20 Nov 2018 14:52:44 +
Support killing child processes on AIX
https://issues.jenkins-ci.org/browse/JENKINS-16867

--
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/47aa58a3-c622-0662-aee8-8bf67aec31cf%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Jenkins GSoC] - Budget status update for 2018 + swag delivery expenses discussion

[Oleg Nenashev]

Hi, I was unable to finish the calculation due to some personal stuff.
Maybe we could start from approving 500USD so that we have some runway in 
the GSoC org admin team.
If we spend less, it will be even better

BR, Oleg

On Friday, December 28, 2018 at 11:08:18 PM UTC+1, Oleg Nenashev wrote:
>
> Hi Martin,
>
> No, I did not consider the banner to be within the requested budget.
> Preparing a banner requires significant production cost. It seems that 
> Jenkins does not have a table at FOSDEM so far (stands list 
> ), so probably it is not a time-pressing 
> matter. It will make sense to prepare it once the community booth plan for 
> DevOps World - Jenkins World is announced by Alyssa. My proposal would be 
> to revisit this topic in April or so.
>
> BR, Oleg
>
> On Fri, Dec 28, 2018 at 2:55 PM Martin d'Anjou  
> wrote:
>
>> Oleg,
>>
>> Thanks for preparing this budget.
>>
>> I think sending swag to GSoC participants is a great idea. We heard at 
>> the mentor summit that this was a great way to thank students and mentors.
>>
>> I have a question. There were some talks about making a GSoC banner to be 
>> displayed at the developers booth at various events, including DevOps World 
>> - JW. Is that part of the swag budget?
>>
>> Thanks,
>> Martin d'Anjou
>> Jenkins GSoC Org Admin
>>
>> On Thu, Dec 27, 2018 at 7:03 PM Oleg Nenashev  
>> wrote:
>>
>>> Dear all,
>>>
>>> Please find the Jenkins GSoC budget status update for 2018. You can find 
>>> my previous report from July 18 here 
>>> . 
>>> Please note that these estimations are rather approximate ones. GSoC does 
>>> not have a separate budget in the Jenkins project until JEP-8 
>>>  is accepted.
>>>
>>>- Balance on 01.01.2018: *2387.34 USD*
>>>- Income in 2018: *4200 USD* in September according to GSoC Org 
>>>Payments 
>>>
>>>- Expenses in 2018: *~3750 USD*. Number is approximate (currency 
>>>rates, etc.), because we do not know exact numbers until SPI 2018 report 
>>> is 
>>>published
>>>- 1902.94 CHF: DevOps World - Jenkins World sponsorship for Pham Vu 
>>>   Tuan: 
>>>   - 951.26 CHF - GSoC Mentor Summit - Oleg Nenashev
>>>   - 791.26 CAD - GSoC Mentor Summit - Martin d'Anjou: 
>>>   - 254.41 USD - GSoC Mentor Summit - Jeff Pearce: . The report has 
>>>   not been submitted to SPI yet
>>>   - Estimated GSoC balance on 01.01.2019: 
>>> *2837.34 USD *
>>>
>>> So, finally we did not need extra budget as it was approved in July (
>>> thread 
>>> ). 
>>> Reasons: 1 project was failed and did not get conference travel 
>>> sponsorship. For the third project we still have some money reserved should 
>>> the student decide to go to a Jenkins conference and present his work (up 
>>> to 1000 USD). Even with that, we have more than 1800 USD reserved for the 
>>> next year.
>>>
>>> I would like to spend some of that budget on sending swag to GSoC 2018 
>>> participants who have not yet received the swag at DevOps World - Jenkins 
>>> World and other events (~15 recipients). It was originally planned for GSoC 
>>> 2018, but unfortunately it was significantly delayed (my fault). It would 
>>> be also great to print some extra Jenkins GSoC stickers so that we could 
>>> use them for future events. 
>>>
>>> My plan is to have a detailed budget calculation for swag by Monday so 
>>> that it could be discussed at the governance meeting. My rough estimation 
>>> is that it is going to be around 500USD, including printing and delivery 
>>> costs. I would appreciate feedback about feasibility of such expense. WDYT?
>>>
>>> Best regards,
>>> Oleg Nenashev
>>> Jenkins GSoC Org Admin
>>>
>>>
>>>
>>>
>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "jenkins-gsoc-2019-org-admins" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to jenkins-gsoc-2019-org-admins+unsubscr...@googlegroups.com.
>>> To post to this group, send email to 
>>> jenkins-gsoc-2019-org-adm...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkins-gsoc-2019-org-admins/CAPfivLC7d142-gpk6sk%3DGe1jZxDtY1sD3Afog5ZP%2B%3D_f%2B%3D%2Bswg%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 

Re: The future of LTS certification

[Oliver Gondža]

On 22/12/2018 14.22, Ullrich Hafner wrote:

Lucie, thank you for your excellent summary of the current situation!

Since only Mark responded so far this is an indication that actually 
only a few Jenkins developers are using ATH right now. I also think, 
that using ATH in the current way makes not much sense anymore.


As you suggested, a valid option would be to split the two groups of 
tests (smoke tests and plugin specific tests) also physically. This 
would make much sense for me, too. Having the ATH tests for my plugins 
in my own plugin would improve my development cycle: The tests could be 
automatically started in our CI server as soon as I push some changes 
(or a PR has been submitted). Then I also would get feedback if I broke 
something in the UI (at least if I run these tests in travis). On the 
other hand, this would require that we must be more carefully when we 
refactor ATH core classes since now we won’t see compile errors (due to 
API changes) immediately. And if plugin authors do not really care about 
these test in their plugins then they can feel free to delete them.


However, this approach makes LTS testing more difficult. At least in 
theory - as far as I understood your post, in the current state ATH is 
not helpful in ATH testing anymore.


Thanks for your insights, Ullrich. This is very useful as you are/ware 
quite and active user and contributor. I hope the initiative we are 
starting here with Lucie will get more traction after the winter break 
so we will certainly get back to you.


--
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/9da690d8-663d-813b-a57d-cfc28b8ae8a2%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Be able to merge on core

[Manuel Ramón León Jiménez]

Hello guys, happy new year.

I'm working at CloudBees on the open source size and due to the limited 
bandwith from Oleg and to gain more velocity in some developments, 
specially on *java11*, I believe it could be interesting that you allow me 
to have write permission on Jenkins core and jenkins infra github repos to 
be able to merge some PRs. 

If it helps: 

I've being contributing with some PRs already merged to the core as well as 
reviewed some other ones:

   - PRs merged into core:
   - https://github.com/jenkinsci/jenkins/pull/3816
  - https://github.com/jenkinsci/jenkins/pull/3769
  - https://github.com/jenkinsci/jenkins/pull/3768
  - https://github.com/jenkinsci/jenkins/pull/3718
  - https://github.com/jenkinsci/jenkins/pull/3695
  - https://github.com/jenkinsci/jenkins/pull/3648
   - PRs reviewed in core:
   - https://github.com/jenkinsci/jenkins/pull/3786
  - https://github.com/jenkinsci/jenkins/pull/3795
  - https://github.com/jenkinsci/jenkins/pull/3797
  - https://github.com/jenkinsci/jenkins/pull/3807
  - https://github.com/jenkinsci/jenkins/pull/3804
  - https://github.com/jenkinsci/jenkins/pull/3815
  - https://github.com/jenkinsci/jenkins/pull/3818
  
  
I'm also a maintainer of two plugins (
plugin-apache-httpcomponents-client-4-api 

 
and plugin-jdk-tool 

).

My user id in all systems (github, jenkins jira, ...) is: *mramonleon*

Thank you, kind regards.

-- 
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/7fedc96c-5b22-4234-a2b5-b7afd5dc688a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.