<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/xhtml; charset=utf-8">
<style>
div.markdown { white-space: normal; }
div.markdown h1 { font-size: 1.4em; }
div.markdown h2 { font-size: 1.2em; }
div.markdown h3 { font-size: 1.1em; }
blockquote.embedded,div.markdown blockquote { margin: 0 0 5px; padding-left: 5px; border-left: 2px solid #3983C4; color: #3983C4; }
blockquote.embedded blockquote.embedded,div.markdown blockquote blockquote { border-left-color: #7CBF0C; color: #7CBF0C; }
div.markdown div.footnotes li p { margin: 0.2em 0; }
</style>
</head>
<body>
<div class="markdown">
<p dir="auto">This sounds awesome. Any chance you could screencast or screenshot this workflow ?</p>
<p dir="auto">/max</p>
<blockquote>
</blockquote></div>
<blockquote class="embedded">
<div text="#000000" bgcolor="#FFFFFF">
Hi all,<br>
<br>
With <a class="moz-txt-link-freetext" href="https://issues.jboss.org/browse/JBIDE-22312">https://issues.jboss.org/browse/JBIDE-22312</a> , a new CI job [1]
now validates, mirror and runs p2diff [2] automatically whenever a
pull request is submitted against the
jhttps://github.com/jbosstools/jbosstools-target-platforms/
repository. This automated validation then report its success or
failure on the pull request directly, annotating it like Travis CI
does (with a green or red box depending on success).<br>
It returns a failure if TP validation or mirroring fail. It's most
likely to happen because of a wrong reference to a p2 repository, a
missing IU or an incorrect version, or a missing requirement.<br>
It returns a successful build if it managed to validate the PR and
mirror its content. In such case, there is still need to follow the
links to the jenkins job have a human look at the p2diff attached to
the build, and to comment whether p2diff looks fine on the PR. Then,
when build is successful and p2diff looks good, the PR can be
announced to the team and considered for a merge.<br>
<br>
Notes:<br>
* p2diff report is now generated automatically on regular Maven
build (even local ones), building the TP with the -Pmultiple2repo
profile.<br>
* Triggering validation build is setup as a cron running every 5
minutes, so it's fine if the build doesn't start immediately after
your PR creation/update. Just check it again a bit later and in case
of issue, ping @mickaelistria and/or @nickboldt on this PR<br>
* The validation build takes about 1 hour. There are for sure
opportunities to speed it up, but as the TP process is slow anyway
and that this approach is already faster than the previous ones
requiring local mirror and p2diff, speeding it up isn't high
priority at the moment.<br>
<br>
Cheers,<br>
<br>
[1]
<a class="moz-txt-link-freetext" href="https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Master/job/jbosstools-target-platform--pull-request/">https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Master/job/jbosstools-target-platform--pull-request/</a><br>
[2] <a class="moz-txt-link-freetext" href="https://issues.jboss.org/browse/JBIDE-22308">https://issues.jboss.org/browse/JBIDE-22308</a>
<div class="moz-signature">-- <br>
Mickael Istria<br>
Eclipse developer at <a href="http://www.jboss.org/tools">JBoss,
by Red Hat</a><br>
<a href="http://mickaelistria.wordpress.com">My blog</a> - <a
href="http://twitter.com/mickaelistria">My Tweets</a></div>
</div></blockquote>
<div class="markdown">
<blockquote>
<hr>
<p dir="auto">jbosstools-dev mailing list<br>
<a href="mailto:jbosstools-dev@lists.jboss.org">jbosstools-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/jbosstools-dev">https://lists.jboss.org/mailman/listinfo/jbosstools-dev</a></p>
</blockquote>
<p dir="auto">/max<br>
<a href="http://about.me/maxandersen">http://about.me/maxandersen</a></p>
</div>
</body>
</html>