Plugin Hosting

[slide]

Hi All,

Hope you are all doing well! There are currently 6 plugin hosting requests 
that I am not able to move along. At this point, they are waiting for code 
reviews looking for common security issues and so forth. Does anyone have 
any time they could put in to doing some of these reviews?

https://issues.jenkins.io/projects/HOSTING/issues/HOSTING-?filter=allopenissues

Thanks,

Alex

-- 
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/6885ba62-1a94-4645-a36e-99074982293cn%40googlegroups.com.

Re: Open Source Maintainer Week, Jun 7-11. Do we want to organize something?

[Oleg Nenashev]

Hello,

Taking the lack of reaponses, I think we'll skip the event. I was about
doing a workshop on Friday + a few broadcasts, but I was unable to confirm
time from other contributors. I have many thing in progress + Jenkins
contributor summitnin a few weeks. Will focus on that instead of starting
new initiatives.

Added this event to my calendar for the next year.

BR, Oleg

BR, Oleg

On Tue, Jun 8, 2021, 07:55 Oleg Nenashev  wrote:

> Hi Rick,
>
> Could you please vote for the timeslots when you are available?
>
> Best regards,
> Oleg
>
> On Tuesday, June 8, 2021 at 2:44:45 AM UTC+2 Xiaojie Zhao wrote:
>
>> Hi Oleg,
>>
>> I’d happy to help with this.
>>
>> Best,
>> Rick
>>
>>
>>
>>
>> On 06/8/2021 01:03，Oleg Nenashev wrote：
>>
>> Bump, Bump. Anyone interested?
>> I am planning to organize something anyway, but it would be great to have
>> a co-host at least
>>
>>
>> On Fri, Jun 4, 2021 at 4:07 PM Oleg Nenashev  wrote:
>>
>>> Hi all,
>>>
>>> Next week there will be maintainer week on Jun 7-11. There are multiple
>>> events being organized by communities.
>>> https://github.com/github/maintainerweek
>>>
>>>- Jun 07, Upstream OSS https://upstream.live/
>>>- Jun 08-09 - Global Maintainer Summit,
>>>https://globalmaintainersummit.github.com/
>>>- Jun 11 - FundOSS Launch Party: https://fundoss.org/
>>>- Jun 08,10 - Automated Tester livestreams:
>>>https://twitch.tv/automatedtester
>>>- Jun 10 -The Changelog: Maintainer Spotlight Podcast,
>>>https://changelog.com/podcast
>>>
>>> I would propose to organize a few events next week (Jun 10..12):
>>>
>>>- Introduction to Jenkins plugin maintenance: Overview of the
>>>community, tooling, plugin adoption process, etc.
>>>- Jenkins Governance process overview. It has been recently
>>>requested by the Ortelius team, and I think this is a good time to do the
>>>overview
>>>- Small hackfest focused on improving maintainer tools in Jenkins?
>>>Various tools, CI, bots, GitHub actions, etc.
>>>- // Something else? Please comment!
>>>
>>> If anyone wants to be a co-host of the events, I will be happy to
>>> organize them and prepare slides.More contributors and talk ideas are
>>> welcome! I started a Doodle here for the slots, please vote if you are
>>> interested to join the event as a presenter or a speaker:
>>> https://doodle.com/poll/rrt2dz2rg3m26hxh
>>>
>>> Best regards,
>>> Oleg Nenashev
>>> Acting Jenkins Events Officer
>>>
>>> --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Advocacy and Outreach SIG" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jenkins-advocacy-and-o...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkins-advocacy-and-outreach-sig/CAPfivLDdJOhG2xV1G_iWfhzeUiPtEF_CdwGEr-CRBmaSSmXcAQ%40mail.gmail.com
>> 
>> .
>>
>> --
> 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/tPV7YzP3HWE/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/920ae9df-17e0-41af-9c81-72b05c09da74n%40googlegroups.com
> 
> .
>

-- 
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/CAPfivLBq8g-Zx3EBTBfeOxq0YBo-Jhqazu%2Bbo-re5CvTT3DLaQ%40mail.gmail.com.

Re: HELP NEEDED - Jenkins contributor summit on Jun 25

[Oleg Nenashev]

Hi Kara,

Thanks for the feedback and for helping with the Cloud Native SIG! I
understand the timezones are imperfect. Apart from moving a meeting to an
earlier slot, we have an option to do the Cloud Native SIG meeting on
Saturday, Jun 26.

I can host meetings if they are after 4AM UTC. Maybe Rick or Himandri would
be also available.

BR, Oleg


On Wed, Jun 9, 2021, 21:50 Kara de la Marck 
wrote:

> Hi all,
>
> Thank you for organizing the Contributor Summit and its schedule, Oleg and
> Olivier.
>
> I'm very happy to lead on the Cloud Native track to ensure that we have a
> speaker to summarize recent highlights in the Cloud Native SIG; ideally,
> this would be an active community member.
>
> Please note that the time as currently scheduled will be too late for our
> Cloud Native SIG participants and contributors in India (and APAC
> generally).
>
>
>
> On Wed, Jun 9, 2021 at 11:48 AM 'Olblak' via Jenkins Developers <
> jenkinsci-dev@googlegroups.com> wrote:
>
>> Thanks, Oleg for driving this.
>>
>> Yesterday, Mark suggested to me to move the contributor track as early as
>> possible to have as many people from AMER and EMEA in an interactive
>> session.
>> This an idea that I like very much and I would like to discuss it
>> tomorrow.
>> So we would have "project update", "contributor track", "SIG update",
>> "CDF project collaboration" as I am suggesting in the google sheet.
>>
>>
>>
>> On Wed, Jun 9, 2021, at 6:45 AM, Oleg Nenashev wrote:
>>
>> Thanks to Olivier for the contributions and willing to help! Based on the
>> feedback in the voting poll, I created a meeting on Thursday, 1PM UTC. At
>> this meeting we will agree on the agenda and split the
>> organization/moderation tasks. Everyone is welcome to participate, and I
>> will also try to record this meeting.
>>
>> Links:
>>
>> * [Calendar Link](
>> https://calendar.google.com/event?action=TEMPLATE=NzJqczZjZjY1ZDBrYnU1dTk3amowdjEycHMgNHNzMTJmMG1xcjN0YnAxdDJmZTM2OXNsZjRAZw=4ss12f0mqr3tbp1t2fe369slf4%40group.calendar.google.com
>> )
>> * Zoom: [
>> https://zoom.us/j/92075127451](https://www.google.com/url?q=https://zoom.us/j/92075127451=D=calendar=2=AOvVaw0vmVjHpVhjIfQltFhxiNL8)
>> * [Coordination doc](
>> https://www.google.com/url?q=https://docs.google.com/document/d/1JVbWudREipEF5UJn-bBRU5QIjKf8mzFP9iFdwWbgFB0/edit?usp%3Dsharing=D=calendar=2=AOvVaw1CixKPCaFPv2WOYUWlY14h
>> )
>> * [Contributor Summit Schedule](
>> https://www.google.com/url?q=https://docs.google.com/spreadsheets/d/1k2xvtJVMwOTZjzCFlqaQpHlxJkiwS67VjNtnJN0ynXs/edit?usp%3Dsharing=D=calendar=2=AOvVaw2OIj6N3yj8cCjKP5YpNUSC
>> )
>> * [Event landing page](
>> https://www.google.com/url?q=https://www.jenkins.io/events/contributor-summit/=D=calendar=2=AOvVaw3INLbGY58ZLcGoCUXTX7iy
>> )
>>
>> On Mon, Jun 7, 2021 at 10:48 AM 'Olblak' via Jenkins Developers <
>> jenkinsci-dev@googlegroups.com> wrote:
>>
>>
>> Hi Everybody,
>>
>> I started a draft for the Contributor summit schedule.
>>
>> https://docs.google.com/spreadsheets/d/1k2xvtJVMwOTZjzCFlqaQpHlxJkiwS67VjNtnJN0ynXs/edit#gid=0
>>
>> Feel free to comment if
>> - A specific session should or should not be present.
>> - A timeslot allocated to a specific session is too long or too short
>> - You know a good person of contact for each session
>> - Anything that you may think of :)
>>
>>
>>
>> On Mon, Jun 7, 2021, at 9:06 AM, 'Olblak' via Jenkins Developers wrote:
>>
>> Lemme work on that. I could create a GitHub repo with issues for picking
>> up.
>> It can be a quite good way for onboarding of new event contributors. What
>> do you think?
>>
>>
>> I wouldn't bother with that.
>> CDcon is in three weeks so we have two weeks to prepare for the
>> contributor summit.
>> Let stick to the google document and maybe create a google sheet to work
>> on the schedule.
>>
>> I think at this stage the best way to help is to either propose topics
>> that should be covered and identify the correct person to lead those
>> topics.
>> I would be interested to know from RedHat and VirtusLab their vision on
>> the Jenkins operator.
>> I would be interested to know how to prepare next Jenkins (online)
>> meetup. What people learned about running online event, etc...
>> I would be interested to have a session on "howto" contribute to Jenkins,
>> targeting new contributors and that would also be a good opportunity to
>> have interactive session.
>>
>> I started a Doodle for the first coordination call, please vote for the
>> slots here:
>> https://doodle.com/poll/wsrfhzhm79xcgi2y?utm_source=poll_medium=link
>>
>> Thank you for the poll, you were faster than me :D
>>
>>
>> Yes, we need to build the schedule and to confirm the timeslots. Will
>> start a Google Sheet or a Google Calendar for it.
>>
>> Let me handle that, and I'll put a link to the google document
>>
>>
>> On Sun, Jun 6, 2021, at 6:49 PM, Oleg Nenashev wrote:
>>
>> Hi all, thanks for the interest and feedback! Any contributions will be
>> appreciated. I started a Doodle for the first coordination 

Re: Jenkins Public Relations

[Oleg Nenashev]

Hello Tracy,

I am not a native speaker, and maybe my statements came across wrongly. I
wrote  "to the Continuous Delivery Foundation *or* to any other entity
outside the Jenkins community". I do not consider the CDF an entity
external to the Jenkins community. The Jenkins project is a part of the
CDF, and I consider the CDF community and "extended family" of the Jenkins
community. As you say there has been productive collaboration on so many
topics. I neither say nor think that the CDF is external or "them" in your
response. My opinion on this topic has been public on so many occasions,
including the Jenkins at CDF graduation announcements. My opinion has not
changed.

It remains my recommendation that the Jenkins community should take up the
> offer to have CDF manage the PR
>

We have an open governance process in the community, and we will vote on
this matter. If the majority votes to accept the CDF's offer, I will accept
this decision and contribute to its implementation. I am providing my
feeedback, not making decisions for the community. Everyone is welcome to
vote and comment in this thread.

If I have given the impression that this means a PR firm steamrolls things
> then this is certainly not the case, everything is done in conjunction with
> governance board & maintainers.
>
Sure. Whatever is decided, the PR should be a collaboration between the
Jenkins community and the CDF. A third-party PR firm should be also able to
take part of these communications, as well as any other individual and
company contributor.

...  at the very least make it clear in the processes how any organization
> or part of the community can co-ordinate an announcement in an effective
> manner.
>

I agree, the current Press page must be rewritten to capture the process.
If you share contacts you'd like to be included in the loop of PR
communications, I will add all these contacts to my proposal draft.

Best regards,
Oleg Nenasherv

On Wed, Jun 9, 2021 at 11:05 PM Tracy Miranda 
wrote:

> I find it curious that you refer to 'Continuous Delivery Foundationor to
> any other entity outside the Jenkins community' like it is an 'us' vs
> 'them' situation. CDF already provides a bunch of services to help grow the
> community e.g. marketing & events support to attract 900+ folks to
> contributor summit, support for gsoc admin, not to mention other aspects
> with infra, legal & training. I see PR very much as another service in this
> vein, which if done with a professional approach can greatly enhance
> community growth and perception.
> If I have given the impression that this means a PR firm steamrolls things
> then this is certainly not the case, everything is done in conjunction with
> governance board & maintainers. It remains my recommendation that the
> Jenkins community should take up the offer to have CDF manage the PR, but
> certainly at the very least make it clear in the processes how any
> organization or part of the community can co-ordinate an announcement in an
> effective manner.
>
> Tracy
>
> On Fri, Jun 4, 2021 at 5:46 PM Oleg Nenashev 
> wrote:
>
>> I would be happy to have any kind of collaboration with the CDF Press
>> team. We do not have many contributors in this area, and having a extra
>> professional contributors would help the community a lot. At the same time
>> I am *-1* for just delegating press management to the Continuous
>> Delivery Foundation or to any other entity outside the Jenkins community.
>> It may happen on a case by case basis, but IMHO in must not be a default
>> behavior.
>>
>> We have 5 governance board members who represent the community. We also
>> have 5 officers who represent the community within the area of their
>> responsibility. Any component maintainer can represent a sub-community of
>> that component. This is how the community represented, and I see no reason
>> to change that. The https://www.jenkins.io/press/#press-contacts page
>> referenced by Tracy is indeed dated and needs to be updated.
>>
>> My counter-proposal is to work closely with the CDF and other interested
>> parties under the umbrella of the Advocacy SIG.
>>
>>- Advocacy SIG coordinates PR for Jenkins, all interested
>>individual and institutional contributors are welcome to join it.
>>- The SIG provides a venue for coordination of the PR events and
>>initiatives via its mailing list and regular meetings. Discourse might be
>>also used once established.
>>- If needed, we establish new dedicated channels for press
>>communications where we have interested contributors, the CDF team, and
>>other parties who want to join.
>>- Private communications and NDAs, if needed for the PR activities,
>>should be confirmed according to the standard Jenkins governance process.
>>
>> > In 2020 CDF started taking on some of this e.g. fielding questions from
>> reporters during DevOps World
>>
>> I have a lot to say about these particular events, but this has nothing
>> to do with the 

Re: Jenkins Public Relations

[Tracy Miranda]

I find it curious that you refer to 'Continuous Delivery Foundationor to
any other entity outside the Jenkins community' like it is an 'us' vs
'them' situation. CDF already provides a bunch of services to help grow the
community e.g. marketing & events support to attract 900+ folks to
contributor summit, support for gsoc admin, not to mention other aspects
with infra, legal & training. I see PR very much as another service in this
vein, which if done with a professional approach can greatly enhance
community growth and perception.
If I have given the impression that this means a PR firm steamrolls things
then this is certainly not the case, everything is done in conjunction with
governance board & maintainers. It remains my recommendation that the
Jenkins community should take up the offer to have CDF manage the PR, but
certainly at the very least make it clear in the processes how any
organization or part of the community can co-ordinate an announcement in an
effective manner.

Tracy

On Fri, Jun 4, 2021 at 5:46 PM Oleg Nenashev  wrote:

> I would be happy to have any kind of collaboration with the CDF Press
> team. We do not have many contributors in this area, and having a extra
> professional contributors would help the community a lot. At the same time
> I am *-1* for just delegating press management to the Continuous Delivery
> Foundation or to any other entity outside the Jenkins community. It may
> happen on a case by case basis, but IMHO in must not be a default behavior.
>
> We have 5 governance board members who represent the community. We also
> have 5 officers who represent the community within the area of their
> responsibility. Any component maintainer can represent a sub-community of
> that component. This is how the community represented, and I see no reason
> to change that. The https://www.jenkins.io/press/#press-contacts page
> referenced by Tracy is indeed dated and needs to be updated.
>
> My counter-proposal is to work closely with the CDF and other interested
> parties under the umbrella of the Advocacy SIG.
>
>- Advocacy SIG coordinates PR for Jenkins, all interested
>individual and institutional contributors are welcome to join it.
>- The SIG provides a venue for coordination of the PR events and
>initiatives via its mailing list and regular meetings. Discourse might be
>also used once established.
>- If needed, we establish new dedicated channels for press
>communications where we have interested contributors, the CDF team, and
>other parties who want to join.
>- Private communications and NDAs, if needed for the PR activities,
>should be confirmed according to the standard Jenkins governance process.
>
> > In 2020 CDF started taking on some of this e.g. fielding questions from
> reporters during DevOps World
>
> I have a lot to say about these particular events, but this has nothing to
> do with the Jenkins community. DevOps World communications are managed by
> CloudBees, and in the particular case the company made a decision to
> channel questions to the CDF instead of letting some of its employees speak
> to reporters. No further comments, unrelated to the matter IMO.
>
> Best regards,
> Oleg Nenashev
> Jenkins Governance Board Member
>
> On Friday, June 4, 2021 at 8:30:52 PM UTC+2 Alyssa wrote:
>
>> +1 for CDF to handle Jenkins press releases. Having an experienced,
>> dedicated resource on this is a valuable benefit, imo.
>>
>> On Wed, Jun 2, 2021 at 10:43 AM Tracy Miranda <
>> tmir...@linuxfoundation.org> wrote:
>>
>>> Hi all,
>>>
>>> The Continuous Delivery Foundation (CDF) offers public relations (PR)
>>> services to all CDF projects e.g we co-ordinated the Jenkins Graduation
>>> 
>>> announcement.
>>>
>>> *Note:* PR = public relations (not pull request) for this email
>>>
>>> *TL;DR* I'd like to propose updates to https://www.jenkins.io/press/
>>> and processes around PR announcements & related activities to formalize CDF
>>> providing PR support for Jenkins.
>>>
>>> Background:
>>> Jenkins PR has been previously handled by Kohsuke, volunteer press
>>> contacts & the CloudBees PR team e.g Jenkins & AWS
>>> 
>>> , Jenkins & Docker
>>> 
>>>  In
>>> 2020 CDF started taking on some of this e.g. fielding questions from
>>> reporters during DevOp World
>>>
>>> While at the simplest level blog posts can serve as community
>>> announcements (and should continue to do so) PR offers that next level of
>>> support and services typically include:
>>> - building relationships with relevant reporters in the space
>>> - pitching newsworthy announcements to reporters
>>> - co-ordinating announcements when 

Re: Discourse as the default communication channel?

[Oleg Nenashev]

FTR there is similar discussion about Discourse and YAGNI in 
https://community.jenkins.io/t/goal-and-purpose-of-community-jenkins-io-regarding-other-communication-tools-in-jenkins-community/70
 
. Feel free to participate!

On Wednesday, June 2, 2021 at 8:22:17 PM UTC+2 Oleg Nenashev wrote:

> https://community.jenkins.io/ looks really good so far. Thanks all!
>
> On Friday, May 28, 2021 at 4:25:05 PM UTC+2 Oleg Nenashev wrote:
>
>> experiment with language community channels 
>>
>> Creating sub-categories, e.g. for francophone, Spanish speaking or 
>> Russian speaking communities
>>
>> > experiment user outreach tools
>>> Do you have something in mind? 
>>>
>> I would start from a call for topic proposals for the Jenkins Contributor 
>> Summit.
>> Later we can move many GSoC and Hacktoberfest discussions there
>>  
>>
>> On Fri, May 28, 2021, 16:09 'Olblak' via Jenkins Developers <
>> jenkin...@googlegroups.com> wrote:
>>
>>> After additional testing, I decided to allow user registration, on 
>>> community.jenkins.io.
>>> I needed it to test the Github integration.
>>> We can still revert that decision if needed
>>>
>>>
>>>
>>> On Fri, May 28, 2021, at 1:57 PM, 'Olblak' via Jenkins Developers wrote:
>>>
>>> Hi Oleg, 
>>>
>>> Could you elaborate 
>>> > experiment with language community channels
>>>
>>> > experiment user outreach tools
>>> Do you have something in mind? 
>>>
>>> On Fri, May 28, 2021, at 1:00 PM, Oleg Nenashev wrote:
>>>
>>> I would be interested to particupate as the Events officer. I would like 
>>> to experiment with language community channels and user outreach tools.
>>>
>>> Thanks to everyone for driving this!
>>>
>>>
>>> On Fri, May 28, 2021, 11:52 'Olblak' via Jenkins Developers <
>>> jenkin...@googlegroups.com> wrote:
>>>
>>>
>>> I would like to highlight the discussion about the different possible 
>>> authentication with an option to vote
>>> -> https://community.jenkins.io/t/authentication-method-used/36
>>>
>>> I understand not everybody at this point will be able to vote directly 
>>> from Discourse so feel free to either request access to be part of the 
>>> evaluation process or just provide feedback here.
>>>
>>> At this stage, Bruce, Gavin, Tim and I have admin access and can send 
>>> invites.
>>> Once further in the process, we'll reevaluate admin access.
>>>
>>> Cheers
>>>
>>>
>>> On Thu, May 27, 2021, at 11:06 PM, Mark Waite wrote:
>>>
>>> I'd like to be part of the test.
>>>
>>> On Thu, May 27, 2021 at 2:28 PM 'Gavin Mogan' via Jenkins Developers <
>>> jenkin...@googlegroups.com> wrote:
>>>
>>> The tech it uses can give you pretty live updates, but its designed as a 
>>> forum.
>>>
>>> I've sent you a DM on IRC with an invite link for now.
>>>
>>>
>>>
>>> On Thu, May 27, 2021 at 1:08 PM Slide  wrote:
>>>
>>> I would like access please. Just a question, as I am very unfamiliar 
>>> with Discourse. Is it a real time communication medium, a la IRC, or 
>>> something more akin to a forum? 
>>>
>>> On Thu, May 27, 2021 at 11:57 AM 'Olblak' via Jenkins Developers <
>>> jenkin...@googlegroups.com> wrote:
>>>
>>> For whoever is interested to participate to the Discourse project, 
>>> we started discussing over there as a way to test it and get more 
>>> familiar with the tool.
>>> -> https://community.jenkins.io/t/discussion-about-categories/27/12
>>>
>>> Feel free to request an access as I didn't have the time yet to really 
>>> investigate the consequences of the different authentication methods.
>>>
>>> On Tue, May 25, 2021, at 8:46 PM, 'Olblak' via Jenkins Developers wrote:
>>> > Hi Bruce, 
>>> > 
>>> > Thank you for stepping up, you already provided a lot of information 
>>> > here.
>>> > And let's not assume we all know everything about discourse as we 
>>> > definitely don't.
>>> > As you are interested to help with this project, I'll send you an 
>>> > invite to "community.jenkins.io".
>>> > 
>>> > As long as we don't have an agreement on the authentication mechanism, 
>>> > I'll work on invite-only.
>>> > 
>>> > Regarding identifying what we expected from Discourse, Bruce made a 
>>> > good statement that discourse is what we want it to be, so here what I 
>>> > would like it to solve.
>>> > I would like to easily identify and participate in discussion about 
>>> > topics that interested me across different sub-project. So as an 
>>> > initial step, Oleg suggestion seems right to me.
>>> >  
>>> > On my side, I'll investigate the different authentication options. 
>>> > Today during the infrastructure Oleg made a good remark,  we would 
>>> like 
>>> > to ideally move away from maintaining our Ldap service and we would 
>>> > like to offer more alternatives than just using a Github account so 
>>> > maybe using Linux foundation accounts would be better.
>>> > 
>>> > 
>>> > On Tue, May 25, 2021, at 7:16 PM, Matt Sicker wrote:
>>> > > Ha, so I was. Oops!
>>> > > 
>>> > > On Tue, 25 May 2021 at 10:32, 'Gavin Mogan' via Jenkins Developers
>>> > >  wrote:
>>> > > >
>>> 

Re: HELP NEEDED - Jenkins contributor summit on Jun 25

[Kara de la Marck]

Hi all,

Thank you for organizing the Contributor Summit and its schedule, Oleg and
Olivier.

I'm very happy to lead on the Cloud Native track to ensure that we have a
speaker to summarize recent highlights in the Cloud Native SIG; ideally,
this would be an active community member.

Please note that the time as currently scheduled will be too late for our
Cloud Native SIG participants and contributors in India (and APAC
generally).



On Wed, Jun 9, 2021 at 11:48 AM 'Olblak' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:

> Thanks, Oleg for driving this.
>
> Yesterday, Mark suggested to me to move the contributor track as early as
> possible to have as many people from AMER and EMEA in an interactive
> session.
> This an idea that I like very much and I would like to discuss it
> tomorrow.
> So we would have "project update", "contributor track", "SIG update", "CDF
> project collaboration" as I am suggesting in the google sheet.
>
>
>
> On Wed, Jun 9, 2021, at 6:45 AM, Oleg Nenashev wrote:
>
> Thanks to Olivier for the contributions and willing to help! Based on the
> feedback in the voting poll, I created a meeting on Thursday, 1PM UTC. At
> this meeting we will agree on the agenda and split the
> organization/moderation tasks. Everyone is welcome to participate, and I
> will also try to record this meeting.
>
> Links:
>
> * [Calendar Link](
> https://calendar.google.com/event?action=TEMPLATE=NzJqczZjZjY1ZDBrYnU1dTk3amowdjEycHMgNHNzMTJmMG1xcjN0YnAxdDJmZTM2OXNsZjRAZw=4ss12f0mqr3tbp1t2fe369slf4%40group.calendar.google.com
> )
> * Zoom: [
> https://zoom.us/j/92075127451](https://www.google.com/url?q=https://zoom.us/j/92075127451=D=calendar=2=AOvVaw0vmVjHpVhjIfQltFhxiNL8)
> * [Coordination doc](
> https://www.google.com/url?q=https://docs.google.com/document/d/1JVbWudREipEF5UJn-bBRU5QIjKf8mzFP9iFdwWbgFB0/edit?usp%3Dsharing=D=calendar=2=AOvVaw1CixKPCaFPv2WOYUWlY14h
> )
> * [Contributor Summit Schedule](
> https://www.google.com/url?q=https://docs.google.com/spreadsheets/d/1k2xvtJVMwOTZjzCFlqaQpHlxJkiwS67VjNtnJN0ynXs/edit?usp%3Dsharing=D=calendar=2=AOvVaw2OIj6N3yj8cCjKP5YpNUSC
> )
> * [Event landing page](
> https://www.google.com/url?q=https://www.jenkins.io/events/contributor-summit/=D=calendar=2=AOvVaw3INLbGY58ZLcGoCUXTX7iy
> )
>
> On Mon, Jun 7, 2021 at 10:48 AM 'Olblak' via Jenkins Developers <
> jenkinsci-dev@googlegroups.com> wrote:
>
>
> Hi Everybody,
>
> I started a draft for the Contributor summit schedule.
>
> https://docs.google.com/spreadsheets/d/1k2xvtJVMwOTZjzCFlqaQpHlxJkiwS67VjNtnJN0ynXs/edit#gid=0
>
> Feel free to comment if
> - A specific session should or should not be present.
> - A timeslot allocated to a specific session is too long or too short
> - You know a good person of contact for each session
> - Anything that you may think of :)
>
>
>
> On Mon, Jun 7, 2021, at 9:06 AM, 'Olblak' via Jenkins Developers wrote:
>
> Lemme work on that. I could create a GitHub repo with issues for picking
> up.
> It can be a quite good way for onboarding of new event contributors. What
> do you think?
>
>
> I wouldn't bother with that.
> CDcon is in three weeks so we have two weeks to prepare for the
> contributor summit.
> Let stick to the google document and maybe create a google sheet to work
> on the schedule.
>
> I think at this stage the best way to help is to either propose topics
> that should be covered and identify the correct person to lead those
> topics.
> I would be interested to know from RedHat and VirtusLab their vision on
> the Jenkins operator.
> I would be interested to know how to prepare next Jenkins (online) meetup.
> What people learned about running online event, etc...
> I would be interested to have a session on "howto" contribute to Jenkins,
> targeting new contributors and that would also be a good opportunity to
> have interactive session.
>
> I started a Doodle for the first coordination call, please vote for the
> slots here:
> https://doodle.com/poll/wsrfhzhm79xcgi2y?utm_source=poll_medium=link
>
> Thank you for the poll, you were faster than me :D
>
>
> Yes, we need to build the schedule and to confirm the timeslots. Will
> start a Google Sheet or a Google Calendar for it.
>
> Let me handle that, and I'll put a link to the google document
>
>
> On Sun, Jun 6, 2021, at 6:49 PM, Oleg Nenashev wrote:
>
> Hi all, thanks for the interest and feedback! Any contributions will be
> appreciated. I started a Doodle for the first coordination call, please
> vote for the slots here:
> https://doodle.com/poll/wsrfhzhm79xcgi2y?utm_source=poll_medium=link
>
> Answers below:
>
> > I would like to help as, how do I can get started?
> > I could help with some stuff before, during, and after the event, simply
> let me know what to do.
>
> Lemme work on that. I could create a GitHub repo with issues for picking
> up.
> It can be a quite good way for onboarding of new event contributors. What
> do you think?
>
> > My understanding is, we need validation from the different 

Re: Restart ci.jenkins.io Run

[Bryan Stopp]

I'm still not seeing what you are seeing.

Yes, if i look at a failed PR run 
I
 
see that i can re-run that job.

But if i click on the X next to my master commit, click on the Details for 
any step in the run, it takes me to the Run page 
. 
But on the left all that is listed are a bunch of "cd on: check_run" 
builds, which are successful. I am not able to navigate from that page to 
anywhere that allows me to Re-run the Jenkins CI that failed.

If i go to the Actions page directly, the only workflows that are listed 
are the CD configured ones. Nothing about the Jenkins CI builds.

(This wouldn't be much of an issue if my builds didn't constantly fail due 
to the CI server not being able to download dependencies)

-Stopp

On Sunday, June 6, 2021 at 11:43:12 AM UTC-5 timja...@gmail.com wrote:

> There’s a button on the actions page once you click on CD for re-run all 
> jobs 
>
> On Sun, 6 Jun 2021 at 15:56, Bryan Stopp  wrote:
>
>> Tried this. There is no re-run option on for me on the failed Continuous 
>> Delivery job. And it is only showing the CD Jenkins job. Not the  
>> post-master merge build which is required to pass for the CD Workflow to 
>> perform its release.
>>
>> I can re-run PR Merge checks. But not the post-PR merge build.
>>
>> Project in question: 
>> https://github.com/jenkinsci/adobe-cloud-manager-plugin
>>
>>
>> -Stopp
>>
>> On Sunday, June 6, 2021 at 1:20:42 AM UTC-5 timja...@gmail.com wrote:
>>
>>> From the GitHub repo click on the x next to the commit, then click on 
>>> Jenkins.
>>>
>>> That will take you to the GitHub checks page
>>> People with write access can click re-run from there
>>>
>>> On Sun, 6 Jun 2021 at 04:22, Bryan Stopp  wrote:
>>>

 How does one restart a build on the Jenkins CI system? I have been 
 getting failures due to the build being unable to download artifacts from 
 the Jenkins repo. 

 Specifically one of my CD release builds failed this way and i have no 
 idea how to boot it again without doing another push to the main branch.

 Thanks again everyone!

 -Stopp


 -- 
 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/80090907-4ba7-4e8d-ab6c-4abc4920fd0bn%40googlegroups.com
  
 
 .

>>> -- 
>> 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/27c4a2f4-f901-4e94-87c6-fdf82d8b4e6dn%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
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/ae77d96a-833b-45ba-bfb9-620dd2b9d4d6n%40googlegroups.com.

Re: Request for access to Zoom +YT account

[Damien Duportal]

Thanks, credentials for Zoom received, and working as expected.

I now need help from someone with access to the YT channel to help me to 
upload the recording (I've NEVER uploaded a video on YT of my life so 
help/guidelines are more than welcome)

Damien

Le mercredi 9 juin 2021 à 11:42:01 UTC+2, timja...@gmail.com a écrit :

> I've sent Damien the zoom account details
>
> Someone else will need to set him up on YouTube I think? (not sure if I 
> have access)
>
> On Tue, 8 Jun 2021 at 15:14, Mark Waite  wrote:
>
>> +1 from me
>>
>> On Tue, Jun 8, 2021 at 7:59 AM Tim Jacomb  wrote:
>>
>>> +1 from me
>>>
>>> On Tue, 8 Jun 2021 at 14:53, Oleg Nenashev  wrote:
>>>
 +1 from me

 On Tuesday, June 8, 2021 at 3:41:39 PM UTC+2 damien@gmail.com 
 wrote:

>
> As per https://groups.google.com/g/jenkinsci-dev/c/K0wqZpL5a88 , Mark 
> is having limited bandwidth and I've volunteered to drive the next UX SIG 
> meeting until everything goes back to normal.
>
> Therefore I'm asking the authorization to be granted access to the 
> Zoom account (to allow me to start the meeting and record it), and to the 
> Youtube account/channel (to upload the recording in the channel)?
>
> Cheers,
>
> Damien DUPORTAL
> damien@gmail.com
>
 -- 
 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/078ff174-45e2-4980-aabd-6635784b52a2n%40googlegroups.com
  
 
 .

>>> -- 
>>> 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/CAH-3BidL0khnq3NeMnwcwbe6kz2cGFqOaR5heMXOqv7_X%2BjTyQ%40mail.gmail.com
>>>  
>>> 
>>> .
>>>
>> -- 
>> 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/CAO49JtELR0fdpA3NdSwey%3DU3-%2BMvCm8oCJmVLSWpzr8WYKfGzg%40mail.gmail.com
>>  
>> 
>> .
>>
>

-- 
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/3df8ce86-1d45-4b0a-ab1b-6a730c5faf8dn%40googlegroups.com.

Re: Plugin Adoption Request: Scriptler

[Michael Tughan]

RPU PR: 
https://github.com/jenkins-infra/repository-permissions-updater/pull/1984

On Tuesday, June 8, 2021 at 2:45:14 p.m. UTC-4 Michael Tughan wrote:

>
> Hello,
>
> I would like to adopt the Scriptler plugin and make sure that it continues 
> to work with the newest Jenkins versions. I see the plugin is already up 
> for adoption, so I believe this should be relatively simple.
>
> Plugin URL: https://github.com/jenkinsci/scriptler-plugin and 
> https://plugins.jenkins.io/scriptler/
> Pull requests: primarily 
> https://github.com/jenkinsci/scriptler-plugin/pull/41, but 
> https://github.com/jenkinsci/scriptler-plugin/pull/42 and 
> https://github.com/jenkinsci/scriptler-plugin/pull/42 also look important
> GitHub username: mtughan (https://github.com/mtughan/)
> Jenkins infrastructure username: mtughan
>
> Thanks in advance,
> Michael Tughan
>

-- 
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/82177308-3d63-40e4-9b43-f95072ff99f6n%40googlegroups.com.

Re: ANN - Jenkins project infrastructure was affected by Fastly outage on Jun 08, 2021

[Damien Duportal]

Hello all,

This email is an update about yesterday's Fastly outage.

The post-mortem document is available for 7 days at the following link: 
https://hackmd.io/@jenkins-infra/S1uvhbR5O . Any feedback/comment/question 
is welcome as usual either in the document or by email.

Please note that the scope of the outage is less important as initially 
stated, because we reacted in the "heat of the Pager Dutty  alarms". 

Cheers,

Damien DUPORTAL

PS: ci.jenkins.io also had an outage on this time window, upcoming email 
thread on this thread.

Le mardi 8 juin 2021 à 13:25:40 UTC+2, Oleg Nenashev a écrit :

> Dear all,
>
> As you may know, there was a major Fastly outage that led to many outages 
> around the web. Fastly is a worldwide Content Delivery Network (CDN) 
> service used by many sites and services (website ). 
> Fastly sponsors the Jenkins project, and we use it for many services, and 
> we have been a happy user of it for more than one year by now. Many Jenkins 
> services were affected.
>
> Examples of affected services: Jenkins website (jenkins.io 
> ), documentation site, plugins site (
> plugins.jenkins.io/), update centers, and even the status page (
> status.jenkins.io). These services are used by many Jenkins instances, 
> and also by many Jenkins developers, adopters and vendors. There might have 
> been lasting impact on user instances, including but not limited to: plugin 
> update failures, documentation access issues, monitoring alerts, etc. 
>
> The Jenkins infrastructure team is aware of the situation. We are working 
> on the resolution where possible, and we wait for the resolution of the 
> root cause on Fastly’s side. If you want to participate in the resolution, 
> join our #jenkins-infra channel on libera.chat 
> . We will also do a 
> public retrospective later, stay tuned for the follow-ups.
>
> Thanks for your patience, and #HugOps to the Fastly team.
>
> Best regards,
>
> Oleg Nenashev
>
> Jenkins Infra Team
>

-- 
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/9b5ac29b-0904-492f-bf00-03716ca5aaf4n%40googlegroups.com.

Re: HELP NEEDED - Jenkins contributor summit on Jun 25

['Olblak' via Jenkins Developers]

Thanks, Oleg for driving this. 

Yesterday, Mark suggested to me to move the contributor track as early as 
possible to have as many people from AMER and EMEA in an interactive session.
This an idea that I like very much and I would like to discuss it tomorrow. 
So we would have "project update", "contributor track", "SIG update", "CDF 
project collaboration" as I am suggesting in the google sheet.



On Wed, Jun 9, 2021, at 6:45 AM, Oleg Nenashev wrote:
> Thanks to Olivier for the contributions and willing to help! Based on the 
> feedback in the voting poll, I created a meeting on Thursday, 1PM UTC. At 
> this meeting we will agree on the agenda and split the 
> organization/moderation tasks. Everyone is welcome to participate, and I will 
> also try to record this meeting.
> 
> Links:
> 
> * [Calendar 
> Link](https://calendar.google.com/event?action=TEMPLATE=NzJqczZjZjY1ZDBrYnU1dTk3amowdjEycHMgNHNzMTJmMG1xcjN0YnAxdDJmZTM2OXNsZjRAZw=4ss12f0mqr3tbp1t2fe369slf4%40group.calendar.google.com)
> * Zoom: 
> [https://zoom.us/j/92075127451](https://www.google.com/url?q=https://zoom.us/j/92075127451=D=calendar=2=AOvVaw0vmVjHpVhjIfQltFhxiNL8)
> * [Coordination 
> doc](https://www.google.com/url?q=https://docs.google.com/document/d/1JVbWudREipEF5UJn-bBRU5QIjKf8mzFP9iFdwWbgFB0/edit?usp%3Dsharing=D=calendar=2=AOvVaw1CixKPCaFPv2WOYUWlY14h)
> * [Contributor Summit 
> Schedule](https://www.google.com/url?q=https://docs.google.com/spreadsheets/d/1k2xvtJVMwOTZjzCFlqaQpHlxJkiwS67VjNtnJN0ynXs/edit?usp%3Dsharing=D=calendar=2=AOvVaw2OIj6N3yj8cCjKP5YpNUSC)
> * [Event landing 
> page](https://www.google.com/url?q=https://www.jenkins.io/events/contributor-summit/=D=calendar=2=AOvVaw3INLbGY58ZLcGoCUXTX7iy)
> 
> On Mon, Jun 7, 2021 at 10:48 AM 'Olblak' via Jenkins Developers 
>  wrote:
>> __
>> Hi Everybody, 
>> 
>> I started a draft for the Contributor summit schedule.
>> https://docs.google.com/spreadsheets/d/1k2xvtJVMwOTZjzCFlqaQpHlxJkiwS67VjNtnJN0ynXs/edit#gid=0
>> 
>> Feel free to comment if
>> - A specific session should or should not be present.
>> - A timeslot allocated to a specific session is too long or too short
>> - You know a good person of contact for each session
>> - Anything that you may think of :)
>> 
>> 
>> 
>> On Mon, Jun 7, 2021, at 9:06 AM, 'Olblak' via Jenkins Developers wrote:
 Lemme work on that. I could create a GitHub repo with issues for picking 
 up.
 It can be a quite good way for onboarding of new event contributors. What 
 do you think?
>>> 
>>> I wouldn't bother with that.
>>> CDcon is in three weeks so we have two weeks to prepare for the contributor 
>>> summit.
>>> Let stick to the google document and maybe create a google sheet to work on 
>>> the schedule.
>>> 
>>> I think at this stage the best way to help is to either propose topics that 
>>> should be covered and identify the correct person to lead those topics. 
>>> I would be interested to know from RedHat and VirtusLab their vision on the 
>>> Jenkins operator.
>>> I would be interested to know how to prepare next Jenkins (online) meetup. 
>>> What people learned about running online event, etc...
>>> I would be interested to have a session on "howto" contribute to Jenkins, 
>>> targeting new contributors and that would also be a good opportunity to 
>>> have interactive session.  
>>> 
 I started a Doodle for the first coordination call, please vote for the 
 slots here: 
 https://doodle.com/poll/wsrfhzhm79xcgi2y?utm_source=poll_medium=link
>>> Thank you for the poll, you were faster than me :D 
>>> 
>>> 
 Yes, we need to build the schedule and to confirm the timeslots. Will 
 start a Google Sheet or a Google Calendar for it.
>>> Let me handle that, and I'll put a link to the google document
>>> 
>>> 
>>> On Sun, Jun 6, 2021, at 6:49 PM, Oleg Nenashev wrote:
 Hi all, thanks for the interest and feedback! Any contributions will be 
 appreciated. I started a Doodle for the first coordination call, please 
 vote for the slots here: 
 https://doodle.com/poll/wsrfhzhm79xcgi2y?utm_source=poll_medium=link
 
 Answers below:
 
 > I would like to help as, how do I can get started?
 > I could help with some stuff before, during, and after the event, simply 
 > let me know what to do.
 
 Lemme work on that. I could create a GitHub repo with issues for picking 
 up.
 It can be a quite good way for onboarding of new event contributors. What 
 do you think?
 
 > My understanding is, we need validation from the different speakers 
 > (once we agree on the agenda). Is this right?
 
 Yes, we need to build the schedule and to confirm the timeslots. Will 
 start a Google Sheet or a Google Calendar for it.
 
 > If I understand correctly the big picture of the day would be something 
 > like...
 
 Yes. More fine grain plan is in the Google Doc
 
 > Regarding event capacity,  inside the document, It's mentioned 

Re: Request for access to Zoom +YT account

[Tim Jacomb]

I've sent Damien the zoom account details

Someone else will need to set him up on YouTube I think? (not sure if I
have access)

On Tue, 8 Jun 2021 at 15:14, Mark Waite  wrote:

> +1 from me
>
> On Tue, Jun 8, 2021 at 7:59 AM Tim Jacomb  wrote:
>
>> +1 from me
>>
>> On Tue, 8 Jun 2021 at 14:53, Oleg Nenashev 
>> wrote:
>>
>>> +1 from me
>>>
>>> On Tuesday, June 8, 2021 at 3:41:39 PM UTC+2 damien@gmail.com wrote:
>>>

 As per https://groups.google.com/g/jenkinsci-dev/c/K0wqZpL5a88 , Mark
 is having limited bandwidth and I've volunteered to drive the next UX SIG
 meeting until everything goes back to normal.

 Therefore I'm asking the authorization to be granted access to the Zoom
 account (to allow me to start the meeting and record it), and to the
 Youtube account/channel (to upload the recording in the channel)?

 Cheers,

 Damien DUPORTAL
 damien@gmail.com

>>> --
>>> 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/078ff174-45e2-4980-aabd-6635784b52a2n%40googlegroups.com
>>> 
>>> .
>>>
>> --
>> 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/CAH-3BidL0khnq3NeMnwcwbe6kz2cGFqOaR5heMXOqv7_X%2BjTyQ%40mail.gmail.com
>> 
>> .
>>
> --
> 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/CAO49JtELR0fdpA3NdSwey%3DU3-%2BMvCm8oCJmVLSWpzr8WYKfGzg%40mail.gmail.com
> 
> .
>

-- 
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/CAH-3BicB_pgnoU110u8mkuHeHZKB5q50cApchsdOdACvbbvu2A%40mail.gmail.com.