Re: Jenkins Elections Process Question

[Oleg Nenashev]

It would make sense, though I am not sure how another email domain would
make a difference there. Sending emails to Google addresses is not blocked
in China from what I know. CDF might be able to set up an email for us, but
I am not sure about timing. If we want to start the sign-up process on Sep
24 as planned, it would be quite a challenge to get the email in time.

Any thoughts from others?

On Tue, Sep 22, 2020 at 8:12 PM 'Gavin Mogan' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:

> > jenkins-2020-elections@googlegroup
> > It will definitely help contributors in areas where Google services are
> blocked
>
> Wouldn't it make sense for the fallback email to be something other than
> google then?
>
> cd.foundation is using mailgun (according to MX records), so maybe they
> could setup jenkins-2020-elections@cd.foundation that forwards to
> google/the board, so there's no issues.
>
> Gavin
>
> On Tue, Sep 22, 2020 at 11:01 AM Oleg Nenashev 
> wrote:
>
>> As an additional mitigation, we can also add a "send a sign-up email to
>> jenkins-2020-elections@googlegroups" fallback process to the
>> announcement. It will definitely help contributors in areas where Google
>> services are blocked
>>
>> On Tue, Sep 22, 2020, 19:00 Mark Waite  wrote:
>>
>>>
>>>
>>> On Tue, Sep 22, 2020 at 4:28 AM Oleg Nenashev 
>>> wrote:
>>>
 >   it requires users to login to a Google account when using the
 Google Forms mechanism. It does allow us to reduce the possibility of
 duplicate voting.

 Apart from duplicate voting, it also prevents from submitting voting
 sign-up forms for other individuals. If we do not use a Google account or
 any other authentication service, anyone will be able to submit a form for
 anyone else, including doing submissions for participants who may not want
 their emails to be stored and who do not want to receive communications
 from the Jenkins project. It increases the risk of abuse for the voting
 sign-up system.

 We do not want to rely solely on Jenkins LDAP, but I think we need some
 kind of identity management. Google Auth could bridge the gap, as one of
 the options we can rollout quickly. We de-facto require it for many other
 contribution areas.


>>> I think we should use Google Auth to bridge the gap as you've suggested.
>>>
>>>
 Best regards,
 Oleg



 On Monday, September 21, 2020 at 10:15:23 PM UTC+2 Richard Bywater
 wrote:

> Personally I don't think we should be forcing people to sign up for
> third-party services just to be able to vote on Jenkins related matters.
> There may be good reasons that people have for not wanting to create a
> Google account.
>
> Richard.
>
> On Tue, 22 Sep 2020, 3:15 AM Slide,  wrote:
>
>> Hi Everyone,
>>
>> The Jenkins Governance Board Elections Committee is currently
>> implementing the process which has been defined for Governance Board and
>> Officer Elections. As part of this, we are creating the form that will be
>> used for signing up to participate in the elections. We need to collect
>> email addresses as part of the process. We are using a Google Form for 
>> the
>> sign-up and it provides a mechanism to collect email addresses, but it
>> requires users to login to a Google account when using the Google Forms
>> mechanism. It does allow us to reduce the possibility of duplicate 
>> voting.
>> We will not keep the data after the voting. Another option would be to 
>> just
>> have a short text input that accepts an email address and we would 
>> collect
>> it that way. We would like the opinions of those on this list to 
>> determine
>> whether this is acceptable or not. We need the email addresses in order 
>> to
>> communicate if there are issues in the contribution information as well 
>> as
>> to add the folks to the Condorcet vote.
>>
>> Please let us know ASAP your thoughts on this.
>>
>> Regards,
>>
>> Alex Earl
>>
>>
>> --
>> Website: http://earl-of-code.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/CAPiUgVer2x2iug%2BCFNoJkyQDmPoQt_BZyTukijGTnSjezJp2eA%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, 

Re: Jenkins 2020 Board and Officer elections - process changes discussion

[Ullrich Hafner]

+ from me

> Am 22.09.2020 um 18:58 schrieb Mark Waite :
> 
> +1 from me as well.  
> 
> On Tue, Sep 22, 2020 at 4:16 AM Oleg Nenashev  > wrote:
> I have started working on the announcements. Does everyone agree with the 
> suggested dates?
> 
> On Friday, September 18, 2020 at 2:58:12 PM UTC+2 Oleg Nenashev wrote:
> As agreed at the Sep 16 governance meeting (meeting notes 
> ,
>  video ), the suggested changed are 
> approved in principle, but there are some changes which might be requied 
> during the final process documentation review. Any feedback will be 
> appreciated : https://github.com/jenkins-infra/jenkins.io/pull/3712 
>   .
> 
> This pull request also includes the suggested dates:
> Sep 24 - Nominations open, Voting sign-up begins
> Oct 15 - Nominations deadline
> After the deadline, the election committee will process nominations and reach 
> out to candidates in order
> Oct 22: Election candidates are published, including personal statements
> Nov 02: Voting sign-up is over
> After this date, the election committee will verify the sign-up and prepare 
> the final list of voters
> Nov 10: Voting begins
> Email is distributed to all registered voters through Condorcet Internet 
> Voting Service 
> Nov 27: Voting ends, 11PM UTC
> Dec 03: Election results are announced and take effect.
> Best regards,
> Oleg
> On Tuesday, September 15, 2020 at 2:52:59 PM UTC+2 Oleg Nenashev wrote:
> Thanks to everyone for the feedback!
> I will keep working on the proposal and incorporating suggestions this week, 
> and I also suggest to have a discussion at the tomorrow's governance meeting
> 
> Best regards,
> Oleg Nenashev
> 
> On Tuesday, August 25, 2020 at 5:49:02 PM UTC+2, Oleg Nenashev wrote:
> Hi all,
> 
> As discussed at the previous governance meeting, I would like to follow-up on 
> the election process ahead of the 2020 elections this autumn (November). 
> After the 2019 elections we had a retrospective 
> 
>  where we discussed the major pains we experienced during the elections, 
> including the sign-up procedure (caused almost a 4+ weeks dela), eligibility 
> issues and lack of transparency.
> 
> I suggest that we follow-up on these issues and improve the process for the 
> incoming 2020 elections.In order to kick-off the discussion, I have assembled 
> an initial proposal about how the issues could be addressed. Google doc with 
> the proposal is here 
> .
> 
> Any feedback and suggestions would be appreciated!
> 
> Thanks for your time,
> Oleg Nenashev
> 
> 
> -- 
> 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/1d7eaa17-99ca-42db-9760-3c4f34342c83n%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/CAO49JtEPUS0M0OVXfUS3AkgTgz7NzBON%3DnHyoJi36tSxBE16qA%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/0BD3A4C6-0409-459B-B70D-B871A7B6BF46%40gmail.com.

[Event]: DevOps World Happening Now

[Alyssa Tong]

Hi All,

DevOps World  is taking place right
now. Lots of great Jenkins sessions taking place. Join us!

BR,
alyssa

-- 
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/CAC9wNazBV%3DCNudQF1-t9L-qejpHOFAqH5Ga_6qgsO_QbvymD5w%40mail.gmail.com.

Re: API to render links with RepositoryBrowser

[Ullrich Hafner]

Hmm, but how do I get the link for a commit hash then? There is no API to 
obtain change sets from the builds, or am I missing something obvious?

> Am 22.09.2020 um 18:55 schrieb Jesse Glick :
> 
> On Mon, Sep 21, 2020 at 6:18 PM Ullrich Hafner  
> wrote:
>> A repository browser operates on a ChangeSet. How can I create one from a 
>> simple git commit hash?
> 
> You do not. It would be added to a `Run` during `SCM.checkout`.
> 
> -- 
> 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/CANfRfr1JyHhsS%3DcQr_KVMXdwGWXXasCx82ch%2B5F0WLRL8CR1Ag%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/D604C6FE-9D11-4C86-A90A-C05885069167%40gmail.com.

Re: Jenkins Elections Process Question

['Gavin Mogan' via Jenkins Developers]

> jenkins-2020-elections@googlegroup
> It will definitely help contributors in areas where Google services are
blocked

Wouldn't it make sense for the fallback email to be something other than
google then?

cd.foundation is using mailgun (according to MX records), so maybe they
could setup jenkins-2020-elections@cd.foundation that forwards to
google/the board, so there's no issues.

Gavin

On Tue, Sep 22, 2020 at 11:01 AM Oleg Nenashev 
wrote:

> As an additional mitigation, we can also add a "send a sign-up email to
> jenkins-2020-elections@googlegroups" fallback process to the
> announcement. It will definitely help contributors in areas where Google
> services are blocked
>
> On Tue, Sep 22, 2020, 19:00 Mark Waite  wrote:
>
>>
>>
>> On Tue, Sep 22, 2020 at 4:28 AM Oleg Nenashev 
>> wrote:
>>
>>> >   it requires users to login to a Google account when using the Google
>>> Forms mechanism. It does allow us to reduce the possibility of duplicate
>>> voting.
>>>
>>> Apart from duplicate voting, it also prevents from submitting voting
>>> sign-up forms for other individuals. If we do not use a Google account or
>>> any other authentication service, anyone will be able to submit a form for
>>> anyone else, including doing submissions for participants who may not want
>>> their emails to be stored and who do not want to receive communications
>>> from the Jenkins project. It increases the risk of abuse for the voting
>>> sign-up system.
>>>
>>> We do not want to rely solely on Jenkins LDAP, but I think we need some
>>> kind of identity management. Google Auth could bridge the gap, as one of
>>> the options we can rollout quickly. We de-facto require it for many other
>>> contribution areas.
>>>
>>>
>> I think we should use Google Auth to bridge the gap as you've suggested.
>>
>>
>>> Best regards,
>>> Oleg
>>>
>>>
>>>
>>> On Monday, September 21, 2020 at 10:15:23 PM UTC+2 Richard Bywater wrote:
>>>
 Personally I don't think we should be forcing people to sign up for
 third-party services just to be able to vote on Jenkins related matters.
 There may be good reasons that people have for not wanting to create a
 Google account.

 Richard.

 On Tue, 22 Sep 2020, 3:15 AM Slide,  wrote:

> Hi Everyone,
>
> The Jenkins Governance Board Elections Committee is currently
> implementing the process which has been defined for Governance Board and
> Officer Elections. As part of this, we are creating the form that will be
> used for signing up to participate in the elections. We need to collect
> email addresses as part of the process. We are using a Google Form for the
> sign-up and it provides a mechanism to collect email addresses, but it
> requires users to login to a Google account when using the Google Forms
> mechanism. It does allow us to reduce the possibility of duplicate voting.
> We will not keep the data after the voting. Another option would be to 
> just
> have a short text input that accepts an email address and we would collect
> it that way. We would like the opinions of those on this list to determine
> whether this is acceptable or not. We need the email addresses in order to
> communicate if there are issues in the contribution information as well as
> to add the folks to the Condorcet vote.
>
> Please let us know ASAP your thoughts on this.
>
> Regards,
>
> Alex Earl
>
>
> --
> Website: http://earl-of-code.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/CAPiUgVer2x2iug%2BCFNoJkyQDmPoQt_BZyTukijGTnSjezJp2eA%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/cef9e1d2-f7a0-4e1e-bc04-00756c164eecn%40googlegroups.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/pzDc62So6xM/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email 

Re: Jenkins Elections Process Question

[Oleg Nenashev]

As an additional mitigation, we can also add a "send a sign-up email to
jenkins-2020-elections@googlegroups" fallback process to the announcement.
It will definitely help contributors in areas where Google services are
blocked

On Tue, Sep 22, 2020, 19:00 Mark Waite  wrote:

>
>
> On Tue, Sep 22, 2020 at 4:28 AM Oleg Nenashev 
> wrote:
>
>> >   it requires users to login to a Google account when using the Google
>> Forms mechanism. It does allow us to reduce the possibility of duplicate
>> voting.
>>
>> Apart from duplicate voting, it also prevents from submitting voting
>> sign-up forms for other individuals. If we do not use a Google account or
>> any other authentication service, anyone will be able to submit a form for
>> anyone else, including doing submissions for participants who may not want
>> their emails to be stored and who do not want to receive communications
>> from the Jenkins project. It increases the risk of abuse for the voting
>> sign-up system.
>>
>> We do not want to rely solely on Jenkins LDAP, but I think we need some
>> kind of identity management. Google Auth could bridge the gap, as one of
>> the options we can rollout quickly. We de-facto require it for many other
>> contribution areas.
>>
>>
> I think we should use Google Auth to bridge the gap as you've suggested.
>
>
>> Best regards,
>> Oleg
>>
>>
>>
>> On Monday, September 21, 2020 at 10:15:23 PM UTC+2 Richard Bywater wrote:
>>
>>> Personally I don't think we should be forcing people to sign up for
>>> third-party services just to be able to vote on Jenkins related matters.
>>> There may be good reasons that people have for not wanting to create a
>>> Google account.
>>>
>>> Richard.
>>>
>>> On Tue, 22 Sep 2020, 3:15 AM Slide,  wrote:
>>>
 Hi Everyone,

 The Jenkins Governance Board Elections Committee is currently
 implementing the process which has been defined for Governance Board and
 Officer Elections. As part of this, we are creating the form that will be
 used for signing up to participate in the elections. We need to collect
 email addresses as part of the process. We are using a Google Form for the
 sign-up and it provides a mechanism to collect email addresses, but it
 requires users to login to a Google account when using the Google Forms
 mechanism. It does allow us to reduce the possibility of duplicate voting.
 We will not keep the data after the voting. Another option would be to just
 have a short text input that accepts an email address and we would collect
 it that way. We would like the opinions of those on this list to determine
 whether this is acceptable or not. We need the email addresses in order to
 communicate if there are issues in the contribution information as well as
 to add the folks to the Condorcet vote.

 Please let us know ASAP your thoughts on this.

 Regards,

 Alex Earl


 --
 Website: http://earl-of-code.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/CAPiUgVer2x2iug%2BCFNoJkyQDmPoQt_BZyTukijGTnSjezJp2eA%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/cef9e1d2-f7a0-4e1e-bc04-00756c164eecn%40googlegroups.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/pzDc62So6xM/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/CAO49JtFVHGcagjz9ejMMwP027_30bjfQ_XUV6UZVXY-ASriamg%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 

Re: Jenkins Elections Process Question

[Mark Waite]

On Tue, Sep 22, 2020 at 4:28 AM Oleg Nenashev 
wrote:

> >   it requires users to login to a Google account when using the Google
> Forms mechanism. It does allow us to reduce the possibility of duplicate
> voting.
>
> Apart from duplicate voting, it also prevents from submitting voting
> sign-up forms for other individuals. If we do not use a Google account or
> any other authentication service, anyone will be able to submit a form for
> anyone else, including doing submissions for participants who may not want
> their emails to be stored and who do not want to receive communications
> from the Jenkins project. It increases the risk of abuse for the voting
> sign-up system.
>
> We do not want to rely solely on Jenkins LDAP, but I think we need some
> kind of identity management. Google Auth could bridge the gap, as one of
> the options we can rollout quickly. We de-facto require it for many other
> contribution areas.
>
>
I think we should use Google Auth to bridge the gap as you've suggested.


> Best regards,
> Oleg
>
>
>
> On Monday, September 21, 2020 at 10:15:23 PM UTC+2 Richard Bywater wrote:
>
>> Personally I don't think we should be forcing people to sign up for
>> third-party services just to be able to vote on Jenkins related matters.
>> There may be good reasons that people have for not wanting to create a
>> Google account.
>>
>> Richard.
>>
>> On Tue, 22 Sep 2020, 3:15 AM Slide,  wrote:
>>
>>> Hi Everyone,
>>>
>>> The Jenkins Governance Board Elections Committee is currently
>>> implementing the process which has been defined for Governance Board and
>>> Officer Elections. As part of this, we are creating the form that will be
>>> used for signing up to participate in the elections. We need to collect
>>> email addresses as part of the process. We are using a Google Form for the
>>> sign-up and it provides a mechanism to collect email addresses, but it
>>> requires users to login to a Google account when using the Google Forms
>>> mechanism. It does allow us to reduce the possibility of duplicate voting.
>>> We will not keep the data after the voting. Another option would be to just
>>> have a short text input that accepts an email address and we would collect
>>> it that way. We would like the opinions of those on this list to determine
>>> whether this is acceptable or not. We need the email addresses in order to
>>> communicate if there are issues in the contribution information as well as
>>> to add the folks to the Condorcet vote.
>>>
>>> Please let us know ASAP your thoughts on this.
>>>
>>> Regards,
>>>
>>> Alex Earl
>>>
>>>
>>> --
>>> Website: http://earl-of-code.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/CAPiUgVer2x2iug%2BCFNoJkyQDmPoQt_BZyTukijGTnSjezJp2eA%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/cef9e1d2-f7a0-4e1e-bc04-00756c164eecn%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/CAO49JtFVHGcagjz9ejMMwP027_30bjfQ_XUV6UZVXY-ASriamg%40mail.gmail.com.

Re: Jenkins 2020 Board and Officer elections - process changes discussion

[Mark Waite]

+1 from me as well.

On Tue, Sep 22, 2020 at 4:16 AM Oleg Nenashev 
wrote:

> I have started working on the announcements. Does everyone agree with the
> suggested dates?
>
> On Friday, September 18, 2020 at 2:58:12 PM UTC+2 Oleg Nenashev wrote:
>
>> As agreed at the Sep 16 governance meeting (meeting notes
>> 
>> , video ), the suggested changed
>> are approved in principle, but there are some changes which might be
>> requied during the final process documentation review. Any feedback will be
>> appreciated : https://github.com/jenkins-infra/jenkins.io/pull/3712  .
>>
>> This pull request also includes the suggested dates:
>>
>>- Sep 24 - Nominations open, Voting sign-up begins
>>- Oct 15 - Nominations deadline
>>   - After the deadline, the election committee will process
>>   nominations and reach out to candidates in order
>>- Oct 22: Election candidates are published, including personal
>>statements
>>- Nov 02: Voting sign-up is over
>>   - After this date, the election committee will verify the sign-up
>>   and prepare the final list of voters
>>- Nov 10: Voting begins
>>   - Email is distributed to all registered voters through Condorcet
>>   Internet Voting Service 
>>- Nov 27: Voting ends, 11PM UTC
>>- Dec 03: Election results are announced and take effect.
>>
>> Best regards,
>> Oleg
>> On Tuesday, September 15, 2020 at 2:52:59 PM UTC+2 Oleg Nenashev wrote:
>>
>>> Thanks to everyone for the feedback!
>>> I will keep working on the proposal and incorporating suggestions this
>>> week, and I also suggest to have a discussion at the tomorrow's governance
>>> meeting
>>>
>>> Best regards,
>>> Oleg Nenashev
>>>
>>> On Tuesday, August 25, 2020 at 5:49:02 PM UTC+2, Oleg Nenashev wrote:

 Hi all,

 As discussed at the previous governance meeting, I would like to
 follow-up on the election process ahead of the 2020 elections this autumn
 (November). After the 2019 elections we had a retrospective
 
  where
 we discussed the major pains we experienced during the elections, including
 the sign-up procedure (caused almost a 4+ weeks dela), eligibility issues
 and lack of transparency.

 I suggest that we follow-up on these issues and improve the process for
 the incoming 2020 elections.In order to kick-off the discussion, I have
 assembled an initial proposal about how the issues could be addressed.
 Google doc with the proposal is here
 
 .

 Any feedback and suggestions would be appreciated!

 Thanks for your time,
 Oleg Nenashev

 --
> 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/1d7eaa17-99ca-42db-9760-3c4f34342c83n%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/CAO49JtEPUS0M0OVXfUS3AkgTgz7NzBON%3DnHyoJi36tSxBE16qA%40mail.gmail.com.

Re: API to render links with RepositoryBrowser

[Jesse Glick]

On Mon, Sep 21, 2020 at 6:18 PM Ullrich Hafner  wrote:
> A repository browser operates on a ChangeSet. How can I create one from a 
> simple git commit hash?

You do not. It would be added to a `Run` during `SCM.checkout`.

-- 
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/CANfRfr1JyHhsS%3DcQr_KVMXdwGWXXasCx82ch%2B5F0WLRL8CR1Ag%40mail.gmail.com.

Re: Jenkins 2020 Board and Officer elections - process changes discussion

[Slide]

+1 from me for sure

On Tue, Sep 22, 2020 at 3:16 AM Oleg Nenashev 
wrote:

> I have started working on the announcements. Does everyone agree with the
> suggested dates?
>
> On Friday, September 18, 2020 at 2:58:12 PM UTC+2 Oleg Nenashev wrote:
>
>> As agreed at the Sep 16 governance meeting (meeting notes
>> 
>> , video ), the suggested changed
>> are approved in principle, but there are some changes which might be
>> requied during the final process documentation review. Any feedback will be
>> appreciated : https://github.com/jenkins-infra/jenkins.io/pull/3712  .
>>
>> This pull request also includes the suggested dates:
>>
>>- Sep 24 - Nominations open, Voting sign-up begins
>>- Oct 15 - Nominations deadline
>>   - After the deadline, the election committee will process
>>   nominations and reach out to candidates in order
>>- Oct 22: Election candidates are published, including personal
>>statements
>>- Nov 02: Voting sign-up is over
>>   - After this date, the election committee will verify the sign-up
>>   and prepare the final list of voters
>>- Nov 10: Voting begins
>>   - Email is distributed to all registered voters through Condorcet
>>   Internet Voting Service 
>>- Nov 27: Voting ends, 11PM UTC
>>- Dec 03: Election results are announced and take effect.
>>
>> Best regards,
>> Oleg
>> On Tuesday, September 15, 2020 at 2:52:59 PM UTC+2 Oleg Nenashev wrote:
>>
>>> Thanks to everyone for the feedback!
>>> I will keep working on the proposal and incorporating suggestions this
>>> week, and I also suggest to have a discussion at the tomorrow's governance
>>> meeting
>>>
>>> Best regards,
>>> Oleg Nenashev
>>>
>>> On Tuesday, August 25, 2020 at 5:49:02 PM UTC+2, Oleg Nenashev wrote:

 Hi all,

 As discussed at the previous governance meeting, I would like to
 follow-up on the election process ahead of the 2020 elections this autumn
 (November). After the 2019 elections we had a retrospective
 
  where
 we discussed the major pains we experienced during the elections, including
 the sign-up procedure (caused almost a 4+ weeks dela), eligibility issues
 and lack of transparency.

 I suggest that we follow-up on these issues and improve the process for
 the incoming 2020 elections.In order to kick-off the discussion, I have
 assembled an initial proposal about how the issues could be addressed.
 Google doc with the proposal is here
 
 .

 Any feedback and suggestions would be appreciated!

 Thanks for your time,
 Oleg Nenashev

 --
> 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/1d7eaa17-99ca-42db-9760-3c4f34342c83n%40googlegroups.com
> 
> .
>


-- 
Website: http://earl-of-code.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/CAPiUgVcUs07LY1OU1ZdM8rii--3xE0UCRxoYvXuXuLmWKhe7QQ%40mail.gmail.com.

Re: Jenkins build pipeline is failed in our plugin master branch

[Mark Waite]

Your job depends on the findbugs plugin.  The findbugs plugin
 reached end of life two years ago.
It has been replaced by the warnings-ng plugin.  The findbugs plugin was
removed from ci.jenkins.io last week.

The buildPlugin() pipeline script has been extended to support the
warnings-ng.  it can present findbugs analysis results.

On Tue, Sep 22, 2020 at 9:41 AM d...@kinneartech.com 
wrote:

> Hi:
> We just merged our code into master branch, but the Jenkins build pipeline
> is failed, it looks like failed during deploy stage, the build stage is
> successfully.
> The same build is working a couple of days ago.
> Is there anything wrong in Jenkins build pipeline now?
>
> https://ci.jenkins.io/job/Plugins/job/veracode-scan-plugin/job/master/11/console
>
> Thanks for your help.
> Dennis
>
> --
> 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/f7259e70-4c14-43a9-abd1-8bd2bac42335n%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/CAO49JtFuM%2BnSUxGdH1M4QeKCs2KZy-LD7%3D_piTAEPqEC3ngn0g%40mail.gmail.com.

RE: Unable to install Liquibase Runner Plugin via Jenkins

[Robert Reeves]

Wonderful! Thank you!


Robert Reeves
CTO | Liquibase
[cid:image015.png@01D690CE.F3C11B70]
Mobile: 5124222443
Email: r...@liquibase.com
Website: www.liquibase.com
[twitter]
[linkedin]
[stack-overflow]
[github]
[youtube]
[website]
Get certified and learn at: learn.liquibase.com |


From: jenkinsci-dev@googlegroups.com  On Behalf 
Of Daniel Beck
Sent: Tuesday, September 22, 2020 10:18 AM
To: JenkinsCI Developers 
Subject: Re: Unable to install Liquibase Runner Plugin via Jenkins

It's fixed now. Sorry about that. This problem was a side effect of our new 
mirror infra, how we circumvent having to do full syncs all the time, and the 
restoration of this plugin after it was suspended.


On Tue, Sep 22, 2020 at 4:49 PM Robert Reeves 
mailto:r...@liquibase.com>> wrote:
Hi!

We can now see the 1.4.9 Liquibase Plugin via the Jenkins Update Center.

However, it appears that 1.4.9 is not available from 
https://get.jenkins.io/plugins/liquibase-runner/1.4.9/liquibase-runner.hpi.

Here’s the output when I got to install from the Update Center:

java.io.FileNotFoundException: 
https://get.jenkins.io/plugins/liquibase-runner/1.4.9/liquibase-runner.hpi
at 
sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1896)
at 
sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1498)
at 
sun.net.www.protocol.http.HttpURLConnection.getHeaderField(HttpURLConnection.java:3061)
at java.net.URLConnection.getHeaderFieldLong(URLConnection.java:629)
at java.net.URLConnection.getContentLengthLong(URLConnection.java:501)
at java.net.URLConnection.getContentLength(URLConnection.java:485)
at 
sun.net.www.protocol.https.HttpsURLConnectionImpl.getContentLength(HttpsURLConnectionImpl.java:412)
at 
hudson.model.UpdateCenter$UpdateCenterConfiguration.download(UpdateCenter.java:1264)
Caused: java.io.FileNotFoundException: 
https://get.jenkins.io/plugins/liquibase-runner/1.4.9/liquibase-runner.hpi
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at 
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at 
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at 
sun.net.www.protocol.http.HttpURLConnection$10.run(HttpURLConnection.java:1950)
at 
sun.net.www.protocol.http.HttpURLConnection$10.run(HttpURLConnection.java:1945)
at java.security.AccessController.doPrivileged(Native Method)
at 
sun.net.www.protocol.http.HttpURLConnection.getChainedException(HttpURLConnection.java:1944)
at 
sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1514)
at 
sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1498)
at 
sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:268)
at 
hudson.model.UpdateCenter$UpdateCenterConfiguration.download(UpdateCenter.java:1280)
Caused: java.io.IOException: Failed to load 
https://updates.jenkins.io/download/plugins/liquibase-runner/1.4.9/liquibase-runner.hpi
 to /var/jenkins_home/plugins/liquibase-runner.jpi.tmp
at 
hudson.model.UpdateCenter$UpdateCenterConfiguration.download(UpdateCenter.java:1287)
Caused: java.io.IOException: Failed to download from 
https://updates.jenkins.io/download/plugins/liquibase-runner/1.4.9/liquibase-runner.hpi
 (redirected to: 
https://get.jenkins.io/plugins/liquibase-runner/1.4.9/liquibase-runner.hpi)
at 
hudson.model.UpdateCenter$UpdateCenterConfiguration.download(UpdateCenter.java:1321)
at hudson.model.UpdateCenter$DownloadJob._run(UpdateCenter.java:1869)
at 
hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:2147)
at hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:1843)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at 
hudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:118)
at java.lang.Thread.run(Thread.java:748)

Thanks!

Robert

Robert Reeves
CTO | Liquibase
[cid:image008.png@01D690CE.F3AB4980]
Mobile: 5124222443
Email: r...@liquibase.com
Website: www.liquibase.com
[twitter]
[linkedin]

Jenkins build pipeline is failed in our plugin master branch

[d...@kinneartech.com]

Hi:
We just merged our code into master branch, but the Jenkins build pipeline 
is failed, it looks like failed during deploy stage, the build stage is 
successfully.
The same build is working a couple of days ago.
Is there anything wrong in Jenkins build pipeline now?
https://ci.jenkins.io/job/Plugins/job/veracode-scan-plugin/job/master/11/console

Thanks for your help.
Dennis

-- 
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/f7259e70-4c14-43a9-abd1-8bd2bac42335n%40googlegroups.com.

Re: Unable to install Liquibase Runner Plugin via Jenkins

[Daniel Beck]

It's fixed now. Sorry about that. This problem was a side effect of our new
mirror infra, how we circumvent having to do full syncs all the time, and
the restoration of this plugin after it was suspended.


On Tue, Sep 22, 2020 at 4:49 PM Robert Reeves  wrote:

> Hi!
>
>
>
> We can now see the 1.4.9 Liquibase Plugin via the Jenkins Update Center.
>
>
>
> However, it appears that 1.4.9 is not available from
> https://get.jenkins.io/plugins/liquibase-runner/1.4.9/liquibase-runner.hpi
> .
>
>
>
> Here’s the output when I got to install from the Update Center:
>
>
>
> java.io.FileNotFoundException:
> https://get.jenkins.io/plugins/liquibase-runner/1.4.9/liquibase-runner.hpi
>
> at
> sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1896)
>
> at
> sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1498)
>
> at
> sun.net.www.protocol.http.HttpURLConnection.getHeaderField(HttpURLConnection.java:3061)
>
> at
> java.net.URLConnection.getHeaderFieldLong(URLConnection.java:629)
>
> at
> java.net.URLConnection.getContentLengthLong(URLConnection.java:501)
>
> at java.net.URLConnection.getContentLength(URLConnection.java:485)
>
> at
> sun.net.www.protocol.https.HttpsURLConnectionImpl.getContentLength(HttpsURLConnectionImpl.java:412)
>
> at
> hudson.model.UpdateCenter$UpdateCenterConfiguration.download(UpdateCenter.java:1264)
>
> Caused: java.io.FileNotFoundException:
> https://get.jenkins.io/plugins/liquibase-runner/1.4.9/liquibase-runner.hpi
>
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
>
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
>
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
>
> at
> sun.net.www.protocol.http.HttpURLConnection$10.run(HttpURLConnection.java:1950)
>
> at
> sun.net.www.protocol.http.HttpURLConnection$10.run(HttpURLConnection.java:1945)
>
> at java.security.AccessController.doPrivileged(Native Method)
>
> at
> sun.net.www.protocol.http.HttpURLConnection.getChainedException(HttpURLConnection.java:1944)
>
> at
> sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1514)
>
> at
> sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1498)
>
> at
> sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:268)
>
> at
> hudson.model.UpdateCenter$UpdateCenterConfiguration.download(UpdateCenter.java:1280)
>
> Caused: java.io.IOException: Failed to load
> https://updates.jenkins.io/download/plugins/liquibase-runner/1.4.9/liquibase-runner.hpi
> to /var/jenkins_home/plugins/liquibase-runner.jpi.tmp
>
> at
> hudson.model.UpdateCenter$UpdateCenterConfiguration.download(UpdateCenter.java:1287)
>
> Caused: java.io.IOException: Failed to download from
> https://updates.jenkins.io/download/plugins/liquibase-runner/1.4.9/liquibase-runner.hpi
> (redirected to:
> https://get.jenkins.io/plugins/liquibase-runner/1.4.9/liquibase-runner.hpi
> )
>
> at
> hudson.model.UpdateCenter$UpdateCenterConfiguration.download(UpdateCenter.java:1321)
>
> at
> hudson.model.UpdateCenter$DownloadJob._run(UpdateCenter.java:1869)
>
> at
> hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:2147)
>
> at
> hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:1843)
>
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>
> at
> hudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:118)
>
> at java.lang.Thread.run(Thread.java:748)
>
>
>
> Thanks!
>
>
>
> Robert
>
>
>
> Robert Reeves
>
> CTO | *Liquibase*
>
> 
>
> *Mobile:* 5124222443
>
> *Email:* r...@liquibase.com
>
> *Website:* www.liquibase.com
>
> [image: twitter] 
>
> [image: linkedin] 
>
> [image: stack-overflow] 
>
> [image: github] 
>
> [image: youtube]
> 
>
> [image: website] 
>
> Get certified and learn at: learn.liquibase.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
> 

Re: Updating links on Plugin Page

['Gavin Mogan' via Jenkins Developers]

As for releases, once the pom.xml is updated and released the releases tab
will pull info from
https://github.com/jenkinsci/liquibase-runner-plugin/releases

On Tue, Sep 22, 2020 at 7:52 AM Robert Reeves  wrote:

> Thanks, Mark!
>
>
>
>
>
> Robert Reeves
>
> CTO | *Liquibase*
>
> 
>
> *Mobile:* 5124222443
>
> *Email:* r...@liquibase.com
>
> *Website:* www.liquibase.com
>
> [image: twitter] 
>
> [image: linkedin] 
>
> [image: stack-overflow] 
>
> [image: github] 
>
> [image: youtube]
> 
>
> [image: website] 
>
> Get certified and learn at: learn.liquibase.com
>  |
>
>
>
>
>
> *From:* jenkinsci-dev@googlegroups.com  *On
> Behalf Of *Mark Waite
> *Sent:* Tuesday, September 22, 2020 9:50 AM
> *To:* Jenkins Developers 
> *Subject:* Re: Updating links on Plugin Page
>
>
>
>
> https://github.com/jenkinsci/liquibase-runner-plugin/blob/7ef75d44a1521cad94014e237f3b31fc344f4fc7/pom.xml#L53
> is the line that needs to be corrected in your pom.xml file.
>
> On Tuesday, September 22, 2020 at 8:49:37 AM UTC-6 r...@liquibase.com
> wrote:
>
> Hi!
>
>
>
> We’d like to update this page to fix some links:
> https://plugins.jenkins.io/liquibase-runner/.
>
>
>
> How do we do that?
>
>
>
>
>
> Current Issues:
>
>- GitHub link goes to
>https://github.com/jenkinsci/liqiubase-runner-plugin instead of
>https://github.com/jenkinsci/liquibase-runner-plugin. (Note the
>misspelling of “liquibase”.)
>- The releases tab also just seems to not complete the request.
>
>
>
> Thanks!
>
>
>
> Robert
>
>
>
>
>
>
>
> Robert Reeves
>
> CTO | *Liquibase*
>
> 
>
> *Mobile:* 5124222443
>
> *Email:* r...@liquibase.com
>
> *Website:* www.liquibase.com
>
> [image: twitter] 
>
> [image: linkedin] 
>
> [image: stack-overflow] 
>
> [image: github] 
>
> [image: youtube]
> 
>
> [image: website] 
>
> Get certified and learn at: learn.liquibase.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/f04a652a-cea4-4613-bcd6-ec2f6fcfc520n%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/CY4PR06MB2949ED9A45C245D4144035B9883B0%40CY4PR06MB2949.namprd06.prod.outlook.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/CAG%3D_Dut%3D5c18%2B9XXsH%3DUoERhy36_QxcCiYyyF%2B9GZSg5dBLOkA%40mail.gmail.com.

RE: Updating links on Plugin Page

[Robert Reeves]

Thanks, Mark!


Robert Reeves
CTO | Liquibase
[cid:image008.png@01D690C6.02550920]
Mobile: 5124222443
Email: r...@liquibase.com
Website: www.liquibase.com
[twitter]
[linkedin]
[stack-overflow]
[github]
[youtube]
[website]
Get certified and learn at: learn.liquibase.com |


From: jenkinsci-dev@googlegroups.com  On Behalf 
Of Mark Waite
Sent: Tuesday, September 22, 2020 9:50 AM
To: Jenkins Developers 
Subject: Re: Updating links on Plugin Page

https://github.com/jenkinsci/liquibase-runner-plugin/blob/7ef75d44a1521cad94014e237f3b31fc344f4fc7/pom.xml#L53
 is the line that needs to be corrected in your pom.xml file.
On Tuesday, September 22, 2020 at 8:49:37 AM UTC-6 
r...@liquibase.com wrote:
Hi!

We’d like to update this page to fix some links: 
https://plugins.jenkins.io/liquibase-runner/.

How do we do that?


Current Issues:

  *   GitHub link goes to https://github.com/jenkinsci/liqiubase-runner-plugin 
instead of https://github.com/jenkinsci/liquibase-runner-plugin. (Note the 
misspelling of “liquibase”.)
  *   The releases tab also just seems to not complete the request.

Thanks!

Robert



Robert Reeves
CTO | Liquibase
[https://groups.google.com/group/jenkinsci-dev/attach/356370294070d/image001.png?part=0.1=1]
Mobile: 5124222443
Email: r...@liquibase.com
Website: www.liquibase.com
[twitter]
[linkedin]
[stack-overflow]
[github]
[youtube]
[website]
Get certified and learn at: learn.liquibase.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/f04a652a-cea4-4613-bcd6-ec2f6fcfc520n%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/CY4PR06MB2949ED9A45C245D4144035B9883B0%40CY4PR06MB2949.namprd06.prod.outlook.com.

Re: Updating links on Plugin Page

[Mark Waite]

https://github.com/jenkinsci/liquibase-runner-plugin/blob/7ef75d44a1521cad94014e237f3b31fc344f4fc7/pom.xml#L53
 
is the line that needs to be corrected in your pom.xml file.

On Tuesday, September 22, 2020 at 8:49:37 AM UTC-6 r...@liquibase.com wrote:

> Hi!
>
>  
>
> We’d like to update this page to fix some links: 
> https://plugins.jenkins.io/liquibase-runner/.
>
>  
>
> How do we do that?
>
>  
>
>  
>
> Current Issues:
>
>- GitHub link goes to 
>https://github.com/jenkinsci/liqiubase-runner-plugin instead of 
>https://github.com/jenkinsci/liquibase-runner-plugin. (Note the 
>misspelling of “liquibase”.)
>- The releases tab also just seems to not complete the request.
>
>  
>
> Thanks!
>
>  
>
> Robert
>
>  
>
>  
>
>  
>
> Robert Reeves
>
> CTO | *Liquibase*
>
> 
>
> *Mobile:* 5124222443
>
> *Email:* r...@liquibase.com
>
> *Website:* www.liquibase.com
>
> [image: twitter] 
>
> [image: linkedin] 
>
> [image: stack-overflow] 
>
> [image: github] 
>
> [image: youtube] 
> 
>
> [image: website] 
>
> Get certified and learn at: learn.liquibase.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/f04a652a-cea4-4613-bcd6-ec2f6fcfc520n%40googlegroups.com.

Updating links on Plugin Page

[Robert Reeves]

Hi!

We'd like to update this page to fix some links: 
https://plugins.jenkins.io/liquibase-runner/.

How do we do that?


Current Issues:

  *   GitHub link goes to https://github.com/jenkinsci/liqiubase-runner-plugin 
instead of https://github.com/jenkinsci/liquibase-runner-plugin. (Note the 
misspelling of "liquibase".)
  *   The releases tab also just seems to not complete the request.

Thanks!

Robert



Robert Reeves
CTO | Liquibase
[cid:image001.png@01D690C4.FE28E110]
Mobile: 5124222443
Email: r...@liquibase.com
Website: www.liquibase.com
[twitter]
[linkedin]
[stack-overflow]
[github]
[youtube]
[website]
Get certified and learn at: learn.liquibase.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/CY4PR06MB2949558FC26211E165D155B5883B0%40CY4PR06MB2949.namprd06.prod.outlook.com.

Unable to install Liquibase Runner Plugin via Jenkins

[Robert Reeves]

Hi!

We can now see the 1.4.9 Liquibase Plugin via the Jenkins Update Center.

However, it appears that 1.4.9 is not available from 
https://get.jenkins.io/plugins/liquibase-runner/1.4.9/liquibase-runner.hpi.

Here's the output when I got to install from the Update Center:

java.io.FileNotFoundException: 
https://get.jenkins.io/plugins/liquibase-runner/1.4.9/liquibase-runner.hpi
at 
sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1896)
at 
sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1498)
at 
sun.net.www.protocol.http.HttpURLConnection.getHeaderField(HttpURLConnection.java:3061)
at java.net.URLConnection.getHeaderFieldLong(URLConnection.java:629)
at java.net.URLConnection.getContentLengthLong(URLConnection.java:501)
at java.net.URLConnection.getContentLength(URLConnection.java:485)
at 
sun.net.www.protocol.https.HttpsURLConnectionImpl.getContentLength(HttpsURLConnectionImpl.java:412)
at 
hudson.model.UpdateCenter$UpdateCenterConfiguration.download(UpdateCenter.java:1264)
Caused: java.io.FileNotFoundException: 
https://get.jenkins.io/plugins/liquibase-runner/1.4.9/liquibase-runner.hpi
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at 
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at 
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at 
sun.net.www.protocol.http.HttpURLConnection$10.run(HttpURLConnection.java:1950)
at 
sun.net.www.protocol.http.HttpURLConnection$10.run(HttpURLConnection.java:1945)
at java.security.AccessController.doPrivileged(Native Method)
at 
sun.net.www.protocol.http.HttpURLConnection.getChainedException(HttpURLConnection.java:1944)
at 
sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1514)
at 
sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1498)
at 
sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:268)
at 
hudson.model.UpdateCenter$UpdateCenterConfiguration.download(UpdateCenter.java:1280)
Caused: java.io.IOException: Failed to load 
https://updates.jenkins.io/download/plugins/liquibase-runner/1.4.9/liquibase-runner.hpi
 to /var/jenkins_home/plugins/liquibase-runner.jpi.tmp
at 
hudson.model.UpdateCenter$UpdateCenterConfiguration.download(UpdateCenter.java:1287)
Caused: java.io.IOException: Failed to download from 
https://updates.jenkins.io/download/plugins/liquibase-runner/1.4.9/liquibase-runner.hpi
 (redirected to: 
https://get.jenkins.io/plugins/liquibase-runner/1.4.9/liquibase-runner.hpi)
at 
hudson.model.UpdateCenter$UpdateCenterConfiguration.download(UpdateCenter.java:1321)
at hudson.model.UpdateCenter$DownloadJob._run(UpdateCenter.java:1869)
at 
hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:2147)
at hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:1843)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at 
hudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:118)
at java.lang.Thread.run(Thread.java:748)

Thanks!

Robert

Robert Reeves
CTO | Liquibase
[cid:image001.png@01D690C5.95B5E050]
Mobile: 5124222443
Email: r...@liquibase.com
Website: www.liquibase.com
[twitter]
[linkedin]
[stack-overflow]
[github]
[youtube]
[website]
Get certified and learn at: learn.liquibase.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/CY4PR06MB2949BF9DBCC8793C1D0FA864883B0%40CY4PR06MB2949.namprd06.prod.outlook.com.

Gitlab hook plugin development abandoned?

[Léon Hagenaars-Keus]

Hi all,

Is the development of the gitlab hook 
(https://github.com/jenkinsci/gitlab-hook-plugin, 
https://plugins.jenkins.io/gitlab-hook/) abandoned?
I've posted an issue there 
(https://github.com/jenkinsci/gitlab-hook-plugin/issues/62, as a 
notification of CVE-2020-2096/SECURITY-1683 issue to the maintainer), but 
the plugin has seen no development in 3 years.
I might be able to help in fixing the issue.

Kind regards,
Léon Hagenaars-Keus

-- 
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/385899ea-bd1c-4b7b-85f8-bb3635fdd192n%40googlegroups.com.

Re: Jenkins Elections Process Question

[Oleg Nenashev]

>   it requires users to login to a Google account when using the Google 
Forms mechanism. It does allow us to reduce the possibility of duplicate 
voting.  

Apart from duplicate voting, it also prevents from submitting voting 
sign-up forms for other individuals. If we do not use a Google account or 
any other authentication service, anyone will be able to submit a form for 
anyone else, including doing submissions for participants who may not want 
their emails to be stored and who do not want to receive communications 
from the Jenkins project. It increases the risk of abuse for the voting 
sign-up system.

We do not want to rely solely on Jenkins LDAP, but I think we need some 
kind of identity management. Google Auth could bridge the gap, as one of 
the options we can rollout quickly. We de-facto require it for many other 
contribution areas.

Best regards,
Oleg



On Monday, September 21, 2020 at 10:15:23 PM UTC+2 Richard Bywater wrote:

> Personally I don't think we should be forcing people to sign up for 
> third-party services just to be able to vote on Jenkins related matters. 
> There may be good reasons that people have for not wanting to create a 
> Google account.
>
> Richard. 
>
> On Tue, 22 Sep 2020, 3:15 AM Slide,  wrote:
>
>> Hi Everyone,
>>
>> The Jenkins Governance Board Elections Committee is currently 
>> implementing the process which has been defined for Governance Board and 
>> Officer Elections. As part of this, we are creating the form that will be 
>> used for signing up to participate in the elections. We need to collect 
>> email addresses as part of the process. We are using a Google Form for the 
>> sign-up and it provides a mechanism to collect email addresses, but it 
>> requires users to login to a Google account when using the Google Forms 
>> mechanism. It does allow us to reduce the possibility of duplicate voting. 
>> We will not keep the data after the voting. Another option would be to just 
>> have a short text input that accepts an email address and we would collect 
>> it that way. We would like the opinions of those on this list to determine 
>> whether this is acceptable or not. We need the email addresses in order to 
>> communicate if there are issues in the contribution information as well as 
>> to add the folks to the Condorcet vote. 
>>
>> Please let us know ASAP your thoughts on this.
>>
>> Regards,
>>
>> Alex Earl
>>
>>
>> -- 
>> Website: http://earl-of-code.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/CAPiUgVer2x2iug%2BCFNoJkyQDmPoQt_BZyTukijGTnSjezJp2eA%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/cef9e1d2-f7a0-4e1e-bc04-00756c164eecn%40googlegroups.com.

Re: repo-plugin: stalled pull requests

[Typz]

Done here:
https://github.com/jenkins-infra/repository-permissions-updater/pull/1672
Thanks,

-- 
Francois

On Tue, Sep 22, 2020 at 9:37 AM Robert Sandell 
wrote:

> I'm having less and less time to handle pull requests on the repo-plugin.
> So it's OK for me to have Typz added as a maintainer.
>
> @Typz add yourself to this file and make a PR so the admins can do their
> thing:
> https://github.com/jenkins-infra/repository-permissions-updater/blob/master/permissions/plugin-repo.yml
>
>
> /B
>
> Den ons 16 sep. 2020 kl 11:14 skrev Typz :
>
>> Hello,
>>
>> I made a 2 pull requests to repo-plugin
>>  a few months back, to
>> correctly handle multiple checkout from a single job (
>> https://github.com/jenkinsci/repo-plugin/pull/62) and fix changelog when
>> shallow checkout is used (
>> https://github.com/jenkinsci/repo-plugin/pull/63)
>>
>> Can anybody give some feedback, or merge the pull requests?
>>
>> If needed, I can also participate in maintenance of the plugin (my GitHub
>> username is *Typz*, and Jenkins infrastructure account is *typz*)
>>
>> Best regards,
>>
>> --
>> Francois
>>
>
>
> --
> *Robert Sandell*
> Senior Software Engineer
> CloudBees, Inc.
> 
> E: rsand...@cloudbees.com
> Twitter: robert_sandell
>

-- 
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/CAKEkdc5pf7Jo640yKsZLqV-34cM5FRigBgAb-qxHb2Qc4XHJ0g%40mail.gmail.com.

Re: Jenkins 2020 Board and Officer elections - process changes discussion

[Oleg Nenashev]

I have started working on the announcements. Does everyone agree with the 
suggested dates?

On Friday, September 18, 2020 at 2:58:12 PM UTC+2 Oleg Nenashev wrote:

> As agreed at the Sep 16 governance meeting (meeting notes 
> 
> , video ), the suggested changed are 
> approved in principle, but there are some changes which might be requied 
> during the final process documentation review. Any feedback will be 
> appreciated : https://github.com/jenkins-infra/jenkins.io/pull/3712  .
>
> This pull request also includes the suggested dates:
>
>- Sep 24 - Nominations open, Voting sign-up begins
>- Oct 15 - Nominations deadline
>   - After the deadline, the election committee will process 
>   nominations and reach out to candidates in order
>- Oct 22: Election candidates are published, including personal 
>statements
>- Nov 02: Voting sign-up is over
>   - After this date, the election committee will verify the sign-up 
>   and prepare the final list of voters
>- Nov 10: Voting begins
>   - Email is distributed to all registered voters through Condorcet 
>   Internet Voting Service 
>- Nov 27: Voting ends, 11PM UTC
>- Dec 03: Election results are announced and take effect.
>
> Best regards,
> Oleg
> On Tuesday, September 15, 2020 at 2:52:59 PM UTC+2 Oleg Nenashev wrote:
>
>> Thanks to everyone for the feedback!
>> I will keep working on the proposal and incorporating suggestions this 
>> week, and I also suggest to have a discussion at the tomorrow's governance 
>> meeting
>>
>> Best regards,
>> Oleg Nenashev
>>
>> On Tuesday, August 25, 2020 at 5:49:02 PM UTC+2, Oleg Nenashev wrote:
>>>
>>> Hi all,
>>>
>>> As discussed at the previous governance meeting, I would like to 
>>> follow-up on the election process ahead of the 2020 elections this autumn 
>>> (November). After the 2019 elections we had a retrospective 
>>> 
>>>  where 
>>> we discussed the major pains we experienced during the elections, including 
>>> the sign-up procedure (caused almost a 4+ weeks dela), eligibility issues 
>>> and lack of transparency.
>>>
>>> I suggest that we follow-up on these issues and improve the process for 
>>> the incoming 2020 elections.In order to kick-off the discussion, I have 
>>> assembled an initial proposal about how the issues could be addressed. 
>>> Google doc with the proposal is here 
>>> 
>>> .
>>>
>>> Any feedback and suggestions would be appreciated!
>>>
>>> Thanks for your time,
>>> Oleg Nenashev
>>>
>>>

-- 
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/1d7eaa17-99ca-42db-9760-3c4f34342c83n%40googlegroups.com.

Re: Hacktoberfest is coming

[Oleg Nenashev]

Hi all,

Hacktoberfest landing update has been integrated.
Everyone is welcome to add the featured projects 
to https://www.jenkins.io/events/hacktoberfest/#featured-projects . 
Pull requests are welcome!

Best regards,
Oleg

On Friday, September 18, 2020 at 10:40:04 PM UTC+2 marky.r...@gmail.com 
wrote:

> I can help in any way too
>
> { 
> "regards" : {
>  "name" : “marky”,
>  "phone" : "+1 (408) 464 2965 <+1%20(408)%20464%202965>”,
>  "email" : “marky.r...@gmail.com",
>  "team" : “jackson5“,
>  “role” : “software engineer"
>  }
>  }
>
> On Sep 18, 2020, at 1:29 PM, Jeff  wrote:
>
> 
>
> I'm happy to help with reviewing PRs
>
> Jeff
>
> On Wed, Aug 26, 2020 at 7:41 PM Mark Waite  wrote:
>
>> We had a very successful experience with last year's Hacktoberfest 
>> contributions to the Jenkins project.  This year we need help to prepare 
>> for Hacktoberfest and to review Hacktoberfest contributions during October.
>>
>> You can read about the 2019 Hacktoberfest 
>>  to see some of the types 
>> of things that could be done as part of 2020 Hacktoberfest.
>>
>> We need additional help to prepare for Hacktoberfest.  We're looking for 
>> volunteers that can help with:
>>
>>- Plan, host, and present at one or more Jenkins Online Meetups for 
>>Hacktoberfest,  similar to the 2019 welcome session 
>>
>>- Recommend and describe featured projects as pull requests to the 
>> Hacktoberfest 
>>page 
>>
>> 
>>- Identify good first issues in Jenkins plugins, Jenkins core, and 
>>Jenkins docs (Jira issues and GitHub issues)
>>- Write a Hacktoberfest blog post similar to the 2019 blog post 
>>
>>- Review Hacktoberfest pull requests
>>
>> Volunteers, please reply to this message or comment in the Hacktoberfest 
>> gitter channel at https://gitter.im/jenkinsci/hacktoberfest .
>>
>> Thanks,
>> Mark Waite
>>
>> -- 
>> 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/f9118fb0-753a-4c52-a2f0-38a3d8245c07n%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/CADVhPTpMsu1o4AJ5UiBOGGJa1QL5CvE0yW2kSud3fS%2Bu1FrLuw%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/c06c15cd-cb00-4402-a2b6-e925fc09db63n%40googlegroups.com.

Re: repo-plugin: stalled pull requests

[Robert Sandell]

I'm having less and less time to handle pull requests on the repo-plugin.
So it's OK for me to have Typz added as a maintainer.

@Typz add yourself to this file and make a PR so the admins can do their
thing:
https://github.com/jenkins-infra/repository-permissions-updater/blob/master/permissions/plugin-repo.yml


/B

Den ons 16 sep. 2020 kl 11:14 skrev Typz :

> Hello,
>
> I made a 2 pull requests to repo-plugin
>  a few months back, to
> correctly handle multiple checkout from a single job (
> https://github.com/jenkinsci/repo-plugin/pull/62) and fix changelog when
> shallow checkout is used (https://github.com/jenkinsci/repo-plugin/pull/63
> )
>
> Can anybody give some feedback, or merge the pull requests?
>
> If needed, I can also participate in maintenance of the plugin (my GitHub
> username is *Typz*, and Jenkins infrastructure account is *typz*)
>
> Best regards,
>
> --
> Francois
>


-- 
*Robert Sandell*
Senior Software Engineer
CloudBees, Inc.

E: rsand...@cloudbees.com
Twitter: robert_sandell

-- 
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/CALzHZS3oCxbYBLdCtn7SvO%2Bdc123sUZBE9FD6JwcYba2KKnNOQ%40mail.gmail.com.