Request permission for plugins

[Rick]

Hi there,

We will do localization work for some Jenkins core and plugins, more detail 
is here https://groups.google.com/forum/#!topic/jenkinsci-dev/QJQ_fzfILcI

In order to do localization better, it will be more convenient if we get 
the permission to merge PR request. 

-- 
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/96895823-3596-4774-9a1a-65ee815d6bed%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

How polite is to enforcer.skip?

[Aldrin Leal]

Hey there,

I'm updating one of my plugins, and I ran into the RequireUpperBoundDeps
issue:

$ mvn clean package
[INFO] Scanning for projects...
[INFO]
[INFO] ---< br.com.ingenieux.jenkins.plugins:codecommit-url-helper
>---
[INFO] Building AWS CodeCommit URL Helper 0.0.2-SNAPSHOT
[INFO] [ hpi
]-
[INFO]
[INFO] --- maven-clean-plugin:3.0.0:clean (default-clean) @
codecommit-url-helper ---
[INFO]
[INFO] --- maven-hpi-plugin:2.6:validate (default-validate) @
codecommit-url-helper ---
[INFO]
[INFO] --- maven-enforcer-plugin:3.0.0-M1:display-info (display-info) @
codecommit-url-helper ---
[INFO] Maven Version: 3.5.4
[INFO] JDK Version: 1.8.0_151 normalized as: 1.8.0-151
[INFO] OS Info: Arch: amd64 Family: unix Name: linux Version:
4.13.0-46-generic
[INFO]
[INFO] --- maven-enforcer-plugin:3.0.0-M1:enforce (display-info) @
codecommit-url-helper ---
[WARNING] Rule 4: org.apache.maven.plugins.enforcer.RequireUpperBoundDeps
failed with message:
Failed while enforcing RequireUpperBoundDeps. The error(s) are [
Require upper bound dependencies error for
org.jenkins-ci:annotation-indexer:1.11 paths to dependency are:
+-br.com.ingenieux.jenkins.plugins:codecommit-url-helper:0.0.2-SNAPSHOT
  +-org.jenkins-ci.plugins:git:3.9.1
+-org.jenkins-ci:annotation-indexer:1.11
and
+-br.com.ingenieux.jenkins.plugins:codecommit-url-helper:0.0.2-SNAPSHOT
  +-org.jenkins-ci.main:jenkins-core:2.121.3
+-org.jenkins-ci:annotation-indexer:1.12
and
+-br.com.ingenieux.jenkins.plugins:codecommit-url-helper:0.0.2-SNAPSHOT
  +-org.kohsuke:access-modifier-annotation:1.15
+-org.jenkins-ci:annotation-indexer:1.4
and
+-br.com.ingenieux.jenkins.plugins:codecommit-url-helper:0.0.2-SNAPSHOT
  +-org.jenkins-ci.plugins:git:3.9.1
+-com.infradna.tool:bridge-method-annotation:1.17
  +-org.jenkins-ci:annotation-indexer:1.4
and
+-br.com.ingenieux.jenkins.plugins:codecommit-url-helper:0.0.2-SNAPSHOT
  +-org.jenkins-ci.main:jenkins-core:2.121.3
+-org.jenkins-ci:bytecode-compatibility-transformer:1.8
  +-org.jenkins-ci:annotation-indexer:1.4
,
Require upper bound dependencies error for org.jenkins-ci.plugins:junit:1.2
paths to dependency are:
+-br.com.ingenieux.jenkins.plugins:codecommit-url-helper:0.0.2-SNAPSHOT
  +-org.jenkins-ci.plugins:git:3.9.1
+-org.jenkins-ci.plugins:matrix-project:1.7.1
  +-org.jenkins-ci.plugins:junit:1.2
and
+-br.com.ingenieux.jenkins.plugins:codecommit-url-helper:0.0.2-SNAPSHOT
  +-org.jenkins-ci.plugins:git:3.9.1
+-org.jenkins-ci.plugins:mailer:1.18
  +-org.jenkins-ci.plugins:display-url-api:0.2
+-org.jenkins-ci.plugins:junit:1.3
]
[INFO]

[INFO] BUILD FAILURE
[INFO]

[INFO] Total time: 7.760 s
[INFO] Finished at: 2018-08-17T16:54:32-05:00
[INFO]

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M1:enforce
(display-info) on project codecommit-url-helper: Some Enforcer rules have
failed. Look above for specific messages explaining why the rule failed. ->
[Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException


What should be the right approach? In my case, this plugin explictly
depends on both Git and AWS Credentials

--
-- Aldrin Leal,  / https://ingenieux.io/about/

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

Re: Jenkins Blue Ocean Roadmap

[Craig Rodrigues]

Jenn,

Thank you for managing Jenkins pipeline and Blue Ocean.  Those technologies
have really improved the user experience of using Jenkins, and adoption is
quickly
growing.  In the companies I have worked at, everyone that I have shown
Blue Ocean to
has liked it.

I would like to request two things from your team:

1.  Have more of a presence on the Blue Ocean gitter channel (
https://gitter.im/jenkinsci/blueocean-plugin ) from people (either manage
or developer) who are actively working on Blue Ocean.  I realize that
everyone is busy, but even if someone from your team logged into that
channel once a week or once a day, and quickly polled that for user issues
and bug reports, that would be nice.

2.  In JIRA, configure it so that blueocean-plugin bugs get auto-assigned
to a real person who can triage those bugs.  Right now when you create a
bug against the blueocean-plugin, it is Unassigned:

https://issues.jenkins-ci.org/issues/?jql=component%20in%20%20(blueocean-plugin)%20and%20assignee%20is%20empty%20and%20resolution%20%3D%20unresolved

I think these two things would help fill some of the potholes in Blue Ocean,
and improve the product.

Thank you.
--
Craig

On Wed, Jun 27, 2018 at 2:05 PM Jenn Briden  wrote:

> Hello, I am the product manager now working on the plugins for Jenkins
> pipeline and Blue Ocean. We're moving away from monolithic, long-lived
> roadmaps in favor of sharing areas of development and encouraging the
> community to submit Jenkins Enhancement Proposals (JEPs). I will have a PR
> out for the changes to the page in a few days. :)
>
> On Tuesday, June 19, 2018 at 10:31:28 AM UTC-7, Ryan wrote:
>>
>> Hi,
>>I work on a team that really enjoys using Jenkins with Blue Ocean.
>> I'm curious if there's a better, more up-to-date roadmap than what's
>> available here: https://jenkins.io/projects/blueocean/roadmap/.  The
>> roadmap is great, but it appears out of date, it references features
>> expected in 1.4.0, etc, while 1.5.0 is out, and it looks like 1.6.0 is in
>> beta.  Is there someplace that describes what is up-coming/planned for the
>> new releases?
>>
>> Thanks,
>> Best,
>> Ryan
>>
>
>

-- 
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%3DrPVf4-o%2BW7uQV0%3DUiD5Ji1KO6sFonceHCVoWVHBm94C%3D5dA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Pre-JEP check: Jenkins telemetry

[Daniel Beck]

> On 17. Aug 2018, at 15:38, Jesse Glick  wrote:
> 
> On Fri, Aug 17, 2018 at 7:57 AM Daniel Beck  wrote:
>>> Do you plan to implement this data collection in the core directly or in a 
>>> plugin?
>> 
>> Core (or core module).
> 
> Fine for the initial example of collecting system properties, but in
> general this sort of collection will need to make use of plugin code.
> For example, Pipeline developers might like to know things such as how
> many `FlowNode`s are created per build on overage. This is currently
> sent to `support-core` by `workflow-cps` but we would like to gather
> this sort of thing anonymously. (Note that `support-core` already
> includes an anonymization system.) I see no straightforward way to
> gather such a metric without explicit support from one of the Pipeline
> plugins. That implies an _API_ defined in core for transmitting data
> but _implementations_ possibly spread across core and various plugins.

That makes sense. Yes, that should definitely be possible.

> And this just highlights a fundamental question: how exactly do you
> plan to collect this kind of information during a “specific time
> frame”? You can add the collector logic to a core weekly release, or a
> plugin release, and enable the server side for that statistic at the
> same time; and then later turn off the server and remove the collector
> logic from the next component release.

That's one option, coupled with collectors defining the start and end dates 
during which they collect and submit data, otherwise being disabled 
client-side. Combined with shutting down collection on the server side for 
specific collectors should take care of this restriction.

> But users update software on
> whatever schedule they like, so lots of systems will not have the
> right collector logic in place during the window in which it is
> allowed to send data. Will that not bias the results toward
> installations that update frequently? Do you care?

Usage stats point to fairly good update behavior: More than a third of 
installations are on a release no older than eight weeks. This is true for both 
weeklies and LTS. That seems like a large enough user base to get telemetry 
from, while still being in a fairly limited time window.

Still, without extending the collection window to many months, we'd only really 
collect information on those 35-50% of users. It's also difficult to say right 
now how we'd handle LTS releases -- would collectors be eligible for backports? 
(I say yes, as optional extension points written such that they mostly silently 
fail.)

While my original intention was to limit the collection time span as much as 
possible while retaining useful data, it seems we might need to adapt over time 
to the upgrade behavior of our users. That said, I'd prefer to start with 
rather small windows by default, and extend them as needed based on our 
experience.

(Realistically, how much do we care about the experience of users who haven't 
upgraded in several months? We frequently reject their bug reports, they get no 
security updates, we only have a single LTS line…)

>>> we need to review conflicts with JEP-308 (Telemetry API for evergreen)
>> 
>> The client side of that is outside Jenkins itself, while mine would be 
>> inside. This alone means it's practically independent.
> 
> Well, in terms of current implementation, but we would like to align
> these things if at all possible so that developers of a given
> statistic can collect it both from Evergreen systems or from (more or
> less up to date) traditional installations as a single data stream.
> After all, what you are describing is very much one of the key goals
> of Evergreen (if not JEP-308 specifically):

To be useful, we need a large enough user base (one of the concerns you brought 
up above), and therefore cannot tie ourselves to Evergreen here, at least not 
in the short term.

When I first brought up this idea with Tyler a few months ago, IIRC the 
response (from him and/or Baptiste) was there's nothing we can realistically 
share. That's why I went ahead with an independent proposal.

-- 
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/D0033E93-A3C8-4BEA-9803-20F1B8BF85D8%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Adoption of ec2-plugin

[Fabrizio Manfredi]

Hi,
I'd like to adopt the ec2-plugin. I discussed briefly with the maintainer and
he doesn't have objection.
My credential are :
GitHub Login: thoulen
Jenkins Login: thoulen

I will send a pull request soon.

Br
FM

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

Re: Adoption of ec2-plugin

[Francis Upton]

And to confirm, I support this.

On Fri, 17 Aug 2018 at 10:31, Fabrizio Manfredi 
wrote:

> Hi,
> I'd like to adopt the ec2-plugin. I discussed briefly with the maintainer and
> he doesn't have objection.
> My credential are :
> GitHub Login: thoulen
> Jenkins Login: thoulen
>
> I will send a pull request soon.
>
> Br
> FM
>
>
>

-- 
Cell +1 510 432 1589

-- 
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/CADVu73Pv3RXM68-jSay1A-BBSDysAudDsgT0pfL%2Bu2PnRtVPDg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Looking to be added as a maintainer for pam-auth-plugin

[Oleg Nenashev]

Let's also get a response from Stephen

On Fri, Aug 17, 2018, 18:18 Matt Sicker  wrote:

> Great, thanks. Filed a PR at repository-permission-updater.
>
> On Fri, Aug 17, 2018 at 10:58 AM Jesse Glick  wrote:
>
>> On Fri, Aug 17, 2018 at 10:51 AM Matt Sicker 
>> wrote:
>> > CCing Jesse and Stephen who seem to be the two most active maintainers
>> historically for this plugin.
>>
>> According to history I have never done any material changes to the
>> plugin at all. If you care to maintain it, go ahead from my PoV.
>>
>> --
>> 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/CANfRfr0BMESX%3D%2Bm6KHoSBmmhkjNhjMoKhtbBWcypJsNdbvP6%3Dw%40mail.gmail.com
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
> --
> Matt Sicker
> Software Engineer, CloudBees
>
> --
> 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/HaQXmygCHMM/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/CAEot4oxqA3jkxtHQWtFDWHwpJp9AWPABP%3D_wZ3U-b%3DR%2BVtsyFg%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLCs_Gi2yQ_V%2BqbBkfUDksjx-NJOOqhe_mC2Vb3NMT3XoA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Growing community via a stronger Twitter presence

[R. Tyler Croy]

(replies inline)

On Fri, 17 Aug 2018, Oleg Nenashev wrote:

> I like the JEP draft in the current state.
> 
> IMHO it would be great to extend Infrastructure Requirements a bit:
> 
>- A new Tweetdeck account is created
>- Jenkins INFRA team has access to Tweetdeck so it can handle the 
>requests if needed


These two already exist.


>- The account is documented on the Jenkins INFRA wiki pages or jenkins.io
> 
> BR, Oleg
> 
> On Tuesday, August 14, 2018 at 2:34:37 PM UTC+2, Tracy Miranda wrote:
> >
> > Thanks Tyler, Daniel & Mark for the feedback so far. 
> >
> > I've updated the JEP based on this: 
> > https://github.com/jenkinsci/jep/pull/176
> >
> > Please review and let me know any further thoughts.
> >
> > Tracy
> >
> > On Mon, Aug 13, 2018 at 8:22 PM, R. Tyler Croy  > > wrote:
> >
> >>
> >> Following up on this thread, Tracy's taken the initiative to create a 
> >> good JEP
> >> describing the proposed process here:
> >> https://github.com/jenkinsci/jep/pull/175
> >>
> >>
> >> As the primary poster of @jenkinsci, I'm really looking forward to 
> >> sharing some
> >> responsibilities with other passionate twitter/jenkins contributors :)
> >>
> >>
> >>
> >>
> >>
> >> -- 
> >> 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/20180813192211.GG17800%40grape.lasagna.io
> >> .
> >> For more options, visit https://groups.google.com/d/optout.
> >>
> >
> >
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/2bb34025-53f4-4469-8d23-23799706bf80%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/20180817164214.GL17800%40grape.lasagna.io.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: PGP signature

Re: Looking to be added as a maintainer for pam-auth-plugin

[Matt Sicker]

Great, thanks. Filed a PR at repository-permission-updater.

On Fri, Aug 17, 2018 at 10:58 AM Jesse Glick  wrote:

> On Fri, Aug 17, 2018 at 10:51 AM Matt Sicker 
> wrote:
> > CCing Jesse and Stephen who seem to be the two most active maintainers
> historically for this plugin.
>
> According to history I have never done any material changes to the
> plugin at all. If you care to maintain it, go ahead from my PoV.
>
> --
> 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/CANfRfr0BMESX%3D%2Bm6KHoSBmmhkjNhjMoKhtbBWcypJsNdbvP6%3Dw%40mail.gmail.com
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Matt Sicker
Software Engineer, CloudBees

-- 
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/CAEot4oxqA3jkxtHQWtFDWHwpJp9AWPABP%3D_wZ3U-b%3DR%2BVtsyFg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Looking to be added as a maintainer for pam-auth-plugin

[Jesse Glick]

On Fri, Aug 17, 2018 at 10:51 AM Matt Sicker  wrote:
> CCing Jesse and Stephen who seem to be the two most active maintainers 
> historically for this plugin.

According to history I have never done any material changes to the
plugin at all. If you care to maintain it, go ahead from my PoV.

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

Re: Looking to be added as a maintainer for pam-auth-plugin

[Matt Sicker]

CCing Jesse and Stephen who seem to be the two most active maintainers
historically for this plugin.

On Fri, Aug 17, 2018 at 6:45 AM Oleg Nenashev 
wrote:

> Please reach out to the maintainer and get his explicit confirmation in
> this thread.
> If you want to request ownership transfer, the process is described here:
> https://wiki.jenkins.io/display/JENKINS/Adopt+a+Plugin#AdoptaPlugin-Requestcommitaccess
>
> BR, Oleg
>
> On Thursday, August 16, 2018 at 9:22:39 PM UTC+2, Matt Sicker wrote:
>>
>> I've got an open PR there, and I'd like to be added as a maintainer.
>>
>> --
>> Matt Sicker
>> Software Engineer, CloudBees
>>
> --
> 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/66d8deb8-1661-44c9-8efe-c2fdcfbe8cc0%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Matt Sicker
Software Engineer, CloudBees

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

Re: Pre-JEP check: Jenkins telemetry

[Jesse Glick]

On Fri, Aug 17, 2018 at 7:57 AM Daniel Beck  wrote:
>> Do you plan to implement this data collection in the core directly or in a 
>> plugin?
>
> Core (or core module).

Fine for the initial example of collecting system properties, but in
general this sort of collection will need to make use of plugin code.
For example, Pipeline developers might like to know things such as how
many `FlowNode`s are created per build on overage. This is currently
sent to `support-core` by `workflow-cps` but we would like to gather
this sort of thing anonymously. (Note that `support-core` already
includes an anonymization system.) I see no straightforward way to
gather such a metric without explicit support from one of the Pipeline
plugins. That implies an _API_ defined in core for transmitting data
but _implementations_ possibly spread across core and various plugins.

And this just highlights a fundamental question: how exactly do you
plan to collect this kind of information during a “specific time
frame”? You can add the collector logic to a core weekly release, or a
plugin release, and enable the server side for that statistic at the
same time; and then later turn off the server and remove the collector
logic from the next component release. But users update software on
whatever schedule they like, so lots of systems will not have the
right collector logic in place during the window in which it is
allowed to send data. Will that not bias the results toward
installations that update frequently? Do you care?

>> we need to review conflicts with JEP-308 (Telemetry API for evergreen)
>
> The client side of that is outside Jenkins itself, while mine would be 
> inside. This alone means it's practically independent.

Well, in terms of current implementation, but we would like to align
these things if at all possible so that developers of a given
statistic can collect it both from Evergreen systems or from (more or
less up to date) traditional installations as a single data stream.
After all, what you are describing is very much one of the key goals
of Evergreen (if not JEP-308 specifically):

https://github.com/jenkinsci/jep/blob/master/jep/300/README.adoc#connected

> ensure that Jenkins project developers receive useful error and usage 
> telemetry to drive further improvements in Jenkins

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

Re: Growing community via a stronger Twitter presence

[Oleg Nenashev]

I like the JEP draft in the current state.

IMHO it would be great to extend Infrastructure Requirements a bit:

   - A new Tweetdeck account is created
   - Jenkins INFRA team has access to Tweetdeck so it can handle the 
   requests if needed
   - The account is documented on the Jenkins INFRA wiki pages or jenkins.io

BR, Oleg

On Tuesday, August 14, 2018 at 2:34:37 PM UTC+2, Tracy Miranda wrote:
>
> Thanks Tyler, Daniel & Mark for the feedback so far. 
>
> I've updated the JEP based on this: 
> https://github.com/jenkinsci/jep/pull/176
>
> Please review and let me know any further thoughts.
>
> Tracy
>
> On Mon, Aug 13, 2018 at 8:22 PM, R. Tyler Croy  > wrote:
>
>>
>> Following up on this thread, Tracy's taken the initiative to create a 
>> good JEP
>> describing the proposed process here:
>> https://github.com/jenkinsci/jep/pull/175
>>
>>
>> As the primary poster of @jenkinsci, I'm really looking forward to 
>> sharing some
>> responsibilities with other passionate twitter/jenkins contributors :)
>>
>>
>>
>>
>>
>> -- 
>> 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/20180813192211.GG17800%40grape.lasagna.io
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/2bb34025-53f4-4469-8d23-23799706bf80%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

'Restart from Stage' Action (Java plugin development question)

[flavius . cater]

Hello.

Is there a way to check the implementation of the 'Run' button from the 
'Restart from Stage' action (job->build number page). 
I would want to check how i can build a pipeline from a specific stage and 
I thought this functionality would be the same, but in my case I would like 
to build the job with the up to date pipeline script. 
If there is any other solution please inform me as I am new to Jenkins 
plugin dev.

Thanks in advance !

-- 
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/d6fc0e1e-bb31-437f-b610-d29d2989714d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Adopt dashboard-view plugin

[Oleg Nenashev]

Yes, the request has timed out.
I have granted you permissions in GitHub and made you a default assignee.
If you are not a member of the JenkinsCI org, you should get an invitation 
soon.

Welcome aboard!

Best regards,
Oleg Nenashev

On Thursday, August 16, 2018 at 8:01:42 PM UTC+2, Tobias Gruetzmacher wrote:
>
> Hi, 
>
> it seems nobody reacted in the last 2 weeks - can we move ahead with 
> this? 
>
> Regards, Tobias 
>
> On Thu, Aug 02, 2018 at 11:29:59AM -0700, Oleg Nenashev wrote: 
> > Hi Tobias, 
> > 
> > Thanks a lot for the interest! AFAIK both listed maintainers are not 
> > active in the project now. 
> > 
> > Let's wait for the response or 2-week timeout. 
> > 
> > Best regards, 
> > 
> > Oleg 
> > 
> > On Wednesday, August 1, 2018 at 12:31:11 PM UTC+2, Tobias Gruetzmacher 
> wrote: 
> > 
> >   Hi, 
> >   I'd like to adopt the dashboard-view plugin. I'm currently using the 
> >   plugin and have one or two issues with it (I already opened a pull 
> >   request, but it was never merged), but have no "bigger" plans to 
> >   implement new features. But I will at least be available for merging 
> pull 
> >   requests and doing the occasional release. 
> >   GitHub Login: TobiX 
> >   Jenkins Login: tgr 
> >   (It doesn't seem it's up for adoption: 
> >   https://wiki.jenkins.io/display/JENKINS/Dashboard+View, but the last 
> >   release was a year ago) 
> >   Original authors (as listed in the pom.xml) are CCed. 
> >   Regards, Tobias 
> >   -- 
> >   GPG-Key 0x0EBD3CD637B2EE85 - signed/encrypted mail preferred 
> > 
> > -- 
> > 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/09af2fb2-ef90-4bd8-a7a8-ad2ea1b7a100%40googlegroups.com.
>  
>
> > For more options, visit https://groups.google.com/d/optout. 
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/20d14c91-1a24-4330-9398-522352e72d6e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [bulk-builder-plugin] follow up on pull request

[hugo . boog]

Hi Oleg,

I saw the e-mails! I hope I will have time next week to update the plug-in 
:).

Kind regards,

Hugo Boog

Op donderdag 16 augustus 2018 19:41:50 UTC+2 schreef Oleg Nenashev:
>
> Hi Hugo,
>
> The permissions have been granted.
> Welcome aboard, and thanks for your patience!
>
> Best regards,
> Oleg Nenashev
>
>
> On Tuesday, August 14, 2018 at 4:59:06 PM UTC+2, hugo...@gmail.com wrote:
>>
>> Hi Oleg,
>>
>> I just created a Jenkins JIRA ID: Alien_Fromspace
>> My Github account: alienfs
>>
>> Kind regards,
>>
>> Hugo Boog
>>
>> Op zaterdag 11 augustus 2018 15:57:57 UTC+2 schreef Oleg Nenashev:
>>>
>>> Hi Hugo,
>>>
>>> In order to complete ownership transfer, we need your GitHub and Jenkins 
>>> JIRA IDs.
>>>
>>> Thanks in advance,
>>> Oleg
>>>
>>> On Tuesday, July 31, 2018 at 5:38:42 PM UTC+2, Simon Westcott wrote:



 On Thursday, 26 July 2018 00:04:39 UTC+1, Daniel Beck wrote:
>
>
> > On 25. Jul 2018, at 15:52, hugo...@gmail.com wrote: 
> > 
> > I have contacted the original author and unfortunately he can no 
> longer access the repo anymore.I 
>
> Please have them file in iNFRA issue in our Jira for the 'github' 
> component. This can also be used to request that you be granted access. 
> If 
> they're still around, this is the cleanest solution. 
>
>
 Hey, I'm the original plugin author. I've raised 
 https://issues.jenkins-ci.org/browse/INFRA-1731.

>>>

-- 
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/b6fd4680-9100-41ac-8ec7-34c9c2333738%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Pre-JEP check: Jenkins telemetry

[Daniel Beck]

> On 17. Aug 2018, at 13:17, Oleg Nenashev  wrote:
> 
> Do you plan to implement this data collection in the core directly or in a 
> plugin?

Core (or core module).

> Obviously, we need to review conflicts with JEP-308 (Telemetry API for 
> evergreen) so that the proposals do not conflict with each other.

The client side of that is outside Jenkins itself, while mine would be inside. 
This alone means it's practically independent.

-- 
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/BCD71FAC-5458-412F-8724-4D75E1A67DE5%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: Looking to be added as a maintainer for pam-auth-plugin

[Oleg Nenashev]

Please reach out to the maintainer and get his explicit confirmation in 
this thread.
If you want to request ownership transfer, the process is described here: 
https://wiki.jenkins.io/display/JENKINS/Adopt+a+Plugin#AdoptaPlugin-Requestcommitaccess

BR, Oleg

On Thursday, August 16, 2018 at 9:22:39 PM UTC+2, Matt Sicker wrote:
>
> I've got an open PR there, and I'd like to be added as a maintainer.
>
> -- 
> Matt Sicker
> Software Engineer, CloudBees
>

-- 
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/66d8deb8-1661-44c9-8efe-c2fdcfbe8cc0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Deprecating ruby-runtime

[Oleg Nenashev]

Hi Daniel,

Thanks for the amendment!
Would it be also possible to add an "Announcement" section to reasoning and 
explicitly document why proposals (blogpost, administrative warning, direct 
maintainer notification) are rejected?

I still disagree with the user notification approach taken in this 
proposal, and I believe we should do the best possible effort to notify 
users.
Spending 1 hour to write a blogpost with heads-up and workaround guidelines 
(and invitations to contribute) is the most obvious way to do that.
I do not understand why there is so much resistance about that.

CCing all known plugin maintainers in this thread is another obvious way to 
make them aware of the thread. We cannot expect that any plugin maintainer 
carefully reads every thread in the mailing list.

"Scriptler, Build Flow, Copy to Slave, or Perforce."
>
 
I do not buy that justification for JEP-7. All these plugins have been 
depublished due to security reasons, so there was no way to properly notify 
users in advance. But even in such case, the users know about the incoming 
security release in advance so they can prepare to mitigate breaking 
changes. Maintainers also got directly contacted, and they acknowledged the 
action. Here you propose to depublish a bunch of 
non-healthy-but-operational plugins, and the proposed notification process 
is "let's just do that, they should have read mailing lists". And there are 
low-cost ways to let users know in advance and to soften the change. I 
cannot agree with such approach, sorry.

Best regards,
Oleg


On Thursday, August 16, 2018 at 9:45:33 PM UTC+2, Daniel Beck wrote:
>
>
> > On 16. Aug 2018, at 19:45, Oleg Nenashev  > wrote: 
> > 
> >> You mean, so that _new_ users can _install_ the plugins? I would say 
> no. 
> > 
> > How would you define a "new" user in the new configuration-as-code 
> world? If somebody uses official Jenkins Docker image with plugins.txt, the 
> plugins will fail to install when you rebuild the image after the change 
> gets deployed. And it is a pretty popular approach nowadays. Plugin 
> installation features in JCasC 1.0 RC would be also affected AFAICT. 
>
> As of last count, 111 installs of CasC plugin. I'd be _very_ surprised if 
> this ended up affecting more than 5 systems total. 
>
> And while this isn't the only approach to configuration-as-code, people 
> should not expect us to continue distributing plugins indefinitely after we 
> blacklisted the likes of Scriptler, Build Flow, Copy to Slave, or Perforce. 
>
> Notably, update sites only have the newest release, which isn't suitable 
> for C-as-C anyway, so I expect the more stable approaches to use our Maven 
> repo anyway -- which will not be affected. 
>
> Running one's own Maven repo has been an important best practice for a 
> long time. With C-as-C, running one's own update site should be similar. 
>
> I will amend the JEP to record this concern and the answers. I don't think 
> we need to change anything about the chosen approach. 
>
>

-- 
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/34ef7c17-96ac-469e-acc2-e1ceb74c92ef%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Pre-JEP check: Jenkins telemetry

[Oleg Nenashev]

Hi Daniel,

Do you plan to implement this data collection in the core directly or in a 
plugin?
In any case, it looks like a good opportunity to for us to get some data, 
so +1 for implementing the engine.

Obviously, we need to review conflicts with JEP-308 
 
(Telemetry API for evergreen) so that the proposals do not conflict with 
each other.
It would be great if we could somehow use the same APIs for both cases.

BR, Oleg

-- 
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/73b716bd-8e74-4e84-822a-c6be303d1bd7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.