Re: Request to join Jenkins Security Team

[Andres Rodriguez]

+1

On Thu, Aug 31, 2017 at 3:00 PM, Baptiste Mathus  wrote:

> +1.
>
> Le 29 août 2017 16:14, "Robert Sandell"  a écrit :
>
>> +1
>>
>> 2017-08-28 19:29 GMT+02:00 Christopher Orr :
>>
>>> Hi there,
>>>
>>> I'd like to request to join the security team.
>>> I've got all the prerequisites listed (2FA, CLA, nickname on IRC).
>>>
>>> Thanks,
>>> Chris
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Jenkins Developers" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to jenkinsci-dev+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit https://groups.google.com/d/ms
>>> gid/jenkinsci-dev/1503941343.3112205.1087569072.66BA5581%40w
>>> ebmail.messagingengine.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> --
>> Robert Sandell
>> *Software Engineer*
>> *CloudBees Inc.*
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jenkinsci-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit https://groups.google.com/d/ms
>> gid/jenkinsci-dev/CALzHZS048dz9ufW9zCEskaUJnmGzVyTaW8RO5DP%
>> 2B-2YDiwJPdA%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/CANWgJS4yad2nPs45aFsswy7jN%
> 3D1Tr3jneX%2Bt2dgDvGiwH6boEw%40mail.gmail.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Regards,

Andres Rodriguez
www.cloudbees.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/CAM9%3DZ%2B5e0awsmW2FtdLgFY2HBQtACQG2LM6GnBUTUbEZi_KgOA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: PR reviews for jobcacher-plugin

[R. Tyler Croy]

(replies inline)

On Sun, 27 Aug 2017, Stephan Hoermann wrote:

> Hi,
> 
> I have raised two PRs on the jobcacher plugin to add support for non AWS S3 
> API compatible endpoints such as Swift and Ceph and to specify a default 
> branch to use for seeding empty 
> caches. https://github.com/jenkinsci/jobcacher-plugin/pull/3 
> and https://github.com/jenkinsci/jobcacher-plugin/pull/4. There doesn't 
> seem to be much activity on this repo. Another PR has been sitting there 
> since June. How can I get my PRs merged and released?

I suggest volunteering to adpot the plugin, see this wiki page for more:
https://wiki.jenkins.io/display/JENKINS/Adopt+a+Plugin


- R. Tyler Croy

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

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

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


signature.asc
Description: PGP signature

Re: Jenkins custom pipeline step timeout

[Jesse Glick]

Nothing running inside the CPS VM thread should occupy more than a second
or so. If your step takes no block argument, and _usually_ runs almost
instantaneously but _might_ rarely get held up, use
`SynchronousNonBlockingStepExecution`. Otherwise you must return false from
`start`, and asynchronously call `StepContext.onSuccess` from another
thread. More:

https://github.com/jenkinsci/workflow-step-api-plugin/blob/master/README.md

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

Re: Request to join Jenkins Security Team

[Baptiste Mathus]

+1.

Le 29 août 2017 16:14, "Robert Sandell"  a écrit :

> +1
>
> 2017-08-28 19:29 GMT+02:00 Christopher Orr :
>
>> Hi there,
>>
>> I'd like to request to join the security team.
>> I've got all the prerequisites listed (2FA, CLA, nickname on IRC).
>>
>> Thanks,
>> Chris
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jenkinsci-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit https://groups.google.com/d/ms
>> gid/jenkinsci-dev/1503941343.3112205.1087569072.66BA5581%
>> 40webmail.messagingengine.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Robert Sandell
> *Software Engineer*
> *CloudBees Inc.*
>
> --
> 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/CALzHZS048dz9ufW9zCEskaUJnmGzVyTaW8RO5DP%2B-2YDiwJPdA%
> 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/CANWgJS4yad2nPs45aFsswy7jN%3D1Tr3jneX%2Bt2dgDvGiwH6boEw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Jenkins custom pipeline step timeout

[artyom . melnikov]

Hello, i've created custom pipeline step, but it seems like it is being 
interrupted after 5 minutes of work. I didn't find any information about 
this timeout. How can i remove/workaround it? 

-- 
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/638b14d6-a4c9-459e-a0fd-845fdd39d8f2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: New SCMSource trait: filtering old git references

[Stephen Connolly]

On Thu 31 Aug 2017 at 08:37, Javier Delgado  wrote:

> Of course, I was expecting this trait to be included in a separate plugin
> (WIP already on https://github.com/witokondoria/git-aged-refs-trait-plugin
> )
>
> Those caches arent already implemented? What I feel I'm lacking is the
> commit date (and might be solved via the bitbucket and github api
> components)
>

I am not sure if the info you need is in one of the cached objects or not.

If it is already present, WIN!

If not present, I am happy to review PRs  on the "core" plugins that enable
the feature.


>
> El miércoles, 30 de agosto de 2017, 13:10:00 (UTC+2), Stephen Connolly
> escribió:
>>
>> On 30 August 2017 at 01:03, Javier Delgado  wrote:
>>
>>> Following this comment
>>> , I was planning
>>> on creating a new scm trait for excluding references according to a date
>>> threshold.
>>>
>>> The idea after the trait would be leaving out from an analysis branches
>>> considered deprecated or unmantained. This way, a new github organization
>>> or bitbucket team project wouldn't create jobs for the whole references
>>> sitting at the repository but just for the recent ones.
>>>
>>> With this, the implementation seems it could be easy as hell, define a
>>> class extending from SCMSourceTrait that would add a (pre)filter according
>>> the defined threshold value. Here comes my question and request for help:
>>>
>>> * Does anyone feel this would be an invaluable feature or doable in
>>> other way?
>>>
>>
>> I know there are users who would buy you beers if you implemented it for
>> them.
>>
>> There are other users who couldn't care less, which is why this will need
>> to be an extension plugin not part of the core plugins
>>
>>
>>>
>>> I cant seem to be able to look for a commit creation date. I can get the
>>> SHA1 for a branch tip via org.kohsuke.github.GHBranch$Commit and
>>>  com.cloudbees.jenkins.plugins.bitbucket.api.BitbucketBranch. From where
>>> could I extract the modification time of this commit?
>>>
>>> What seems true is that I cant apply a SCMSourceContext prefilter so
>>> this trait wont avoid trips to the Github API
>>>
>>
>> Yep I think you will be hitting round-trips.
>>
>> I am fine with adding supporting changes to the GitHub Branch Source
>> plugin to add lazy caches to the request object... my rule is
>>
>> * Core plugin PRs that enable extension plugins are yes. Stuff that could
>> be an extension plugin should not go in core.
>>
> --
>>> 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/5c30e3f7-7acb-4268-9d6c-c6bd91103304%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/f497407d-c330-47a2-968a-06eede877c11%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
-- 
Sent from my phone

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

Re: New SCMSource trait: filtering old git references

[Javier Delgado]

Of course, I was expecting this trait to be included in a separate plugin 
(WIP already on https://github.com/witokondoria/git-aged-refs-trait-plugin)

Those caches arent already implemented? What I feel I'm lacking is the 
commit date (and might be solved via the bitbucket and github api 
components)

El miércoles, 30 de agosto de 2017, 13:10:00 (UTC+2), Stephen Connolly 
escribió:
>
> On 30 August 2017 at 01:03, Javier Delgado  > wrote:
>
>> Following this comment 
>> , I was planning 
>> on creating a new scm trait for excluding references according to a date 
>> threshold.
>>
>> The idea after the trait would be leaving out from an analysis branches 
>> considered deprecated or unmantained. This way, a new github organization 
>> or bitbucket team project wouldn't create jobs for the whole references 
>> sitting at the repository but just for the recent ones.
>>
>> With this, the implementation seems it could be easy as hell, define a 
>> class extending from SCMSourceTrait that would add a (pre)filter according 
>> the defined threshold value. Here comes my question and request for help:
>>
>> * Does anyone feel this would be an invaluable feature or doable in other 
>> way?
>>
>
> I know there are users who would buy you beers if you implemented it for 
> them.
>
> There are other users who couldn't care less, which is why this will need 
> to be an extension plugin not part of the core plugins
>  
>
>>
>> I cant seem to be able to look for a commit creation date. I can get the 
>> SHA1 for a branch tip via org.kohsuke.github.GHBranch$Commit and 
>>  com.cloudbees.jenkins.plugins.bitbucket.api.BitbucketBranch. From where 
>> could I extract the modification time of this commit? 
>>
>> What seems true is that I cant apply a SCMSourceContext prefilter so this 
>> trait wont avoid trips to the Github API
>>
>
> Yep I think you will be hitting round-trips.
>
> I am fine with adding supporting changes to the GitHub Branch Source 
> plugin to add lazy caches to the request object... my rule is 
>
> * Core plugin PRs that enable extension plugins are yes. Stuff that could 
> be an extension plugin should not go in core. 
>
>> -- 
>> 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/5c30e3f7-7acb-4268-9d6c-c6bd91103304%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/f497407d-c330-47a2-968a-06eede877c11%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.