<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>I agree in the principle. But for the approach to be successfull
we need our new new jenkins to be rocksolid which it isnt for now.
Our EGit tests fail randomly on it while they pass on the old
jenkins.<br>
</p>
<div class="moz-cite-prefix">Am 10.05.17 um 10:17 schrieb Dmitrii
Bocharov:<br>
</div>
<blockquote
cite="mid:CAFzf0b5vcRRZxpr3=Oi85wipGnWXFPCrwSkjdfKkdMt4mTcjOQ@mail.gmail.com"
type="cite">
<div dir="ltr">Jeff, for this purpose we can think of some special
comment for such PRs, that would allow to merge them (like <i>testPR</i>
for a new build). As far as i know it's possible.</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Wed, May 10, 2017 at 9:01 AM,
Jean-Francois Maury <span dir="ltr"><<a
moz-do-not-send="true" href="mailto:jmaury@redhat.com"
target="_blank">jmaury@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="auto">I'm ok with that rule except for one case
when the pr is done before the version bump has been
merged then the Jenkins build will fail because of the
baseline check so maybe we need to update the pr Jenkins
build
<div dir="auto"><br>
</div>
<div dir="auto">Jeff</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">
<div>
<div class="h5">Le 9 mai 2017 23:10, "Mickael Istria"
<<a moz-do-not-send="true"
href="mailto:mistria@redhat.com" target="_blank">mistria@redhat.com</a>>
a écrit :<br type="attribution">
</div>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<div class="h5">
<div dir="ltr">
<div>
<div>
<div>FYI, not merging the broken patches is
the policy followed by most Eclipse.org
projects and overall, none of this project
has complained from a reduced
productivity; on the contrary, catching
and fixing issues immediately on the right
context has improved quality and reduced
the necessary amount of quick fix patches
(which are actually quite time consuming
and stressful for their low added-value).<br>
</div>
So I think if it works for Eclipse.org
projects, it can work for JBoss Tools.<br>
<br>
</div>
Cheers,<br>
</div>
Mickael<br>
</div>
<br>
</div>
</div>
<span class="">______________________________<wbr>_________________<br>
jbosstools-dev mailing list<br>
<a moz-do-not-send="true"
href="mailto:jbosstools-dev@lists.jboss.org"
target="_blank">jbosstools-dev@lists.jboss.org</a><br>
<a moz-do-not-send="true"
href="https://lists.jboss.org/mailman/listinfo/jbosstools-dev"
rel="noreferrer" target="_blank">https://lists.jboss.org/mailma<wbr>n/listinfo/jbosstools-dev</a><br>
</span></blockquote>
</div>
</div>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
jbosstools-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:jbosstools-dev@lists.jboss.org">jbosstools-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/jbosstools-dev">https://lists.jboss.org/mailman/listinfo/jbosstools-dev</a></pre>
</blockquote>
<br>
</body>
</html>