I had a conversation with Oleg about this last week in the #jenkins-community
channel, which I promised I would summarize here. After reading the JEP and
discussing with Oleg a bit, I think this is a reasonable enhancement and has
little to no negative impact, so +1.
The primary question I had
Hi all,
FYI we have been accepted to GSoC 2018.
Soon everybody interested will be added as mentor to the Jenkins
organization
Thanks again to everybody who created project proposals!
We are still ready to accept more project ideas, so feel free to create new
ones
BR, Oleg
вторник, 6 февраля
> On 12. Feb 2018, at 13:39, artem.fedo...@blazemeter.com wrote:
>
> 1) Change email in our jenkins profile to `s...@blazemeter.com` , because
> current is personal email address. And change Maintainer to BlazeMeter.
> https://plugins.jenkins.io/BlazeMeterJenkinsPlugin
This information is
Hi,
Our BlazeMeter team want to make a few changes in our account:
1) Change email in our jenkins profile to `s...@blazemeter.com` , because
current is personal email address. And change Maintainer to BlazeMeter.
https://plugins.jenkins.io/BlazeMeterJenkinsPlugin
2) Add commit access to this
jenkins-test-harness version 1.642
On Friday, 9 February 2018 19:01:41 UTC+5:30, Jesse Glick wrote:
>
> On Fri, Feb 9, 2018 at 1:49 PM, Priya Pawar > wrote:
> > In this case value of seconds is just changing in log message only. Test
> is
> > still failing in 180