<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/xhtml; charset=utf-8">
</head>
<body>
<div style="font-family:sans-serif"><div style="white-space:normal">
<p dir="auto"></p></div>
<div style="white-space:pre-wrap"><blockquote style="border-left:2px solid #777; color:#777; margin:0 0 5px; padding-left:5px"><blockquote style="border-left:2px solid #777; color:#999; margin:0 0 5px; padding-left:5px; border-left-color:#999"><div dir="auto">
</div><div dir="auto">
</div></blockquote><div dir="auto">With JJB, there are 2 types of jobs:
</div><div dir="auto">1) the service job that will typically run on schedule. This job will
</div><div dir="auto">then parse the devtools-ci-index.git repo and setup jenkins jobs,
</div><div dir="auto">change configs and notification details etc for the actual jobs. I
</div><div dir="auto">think leaving that on a 10 min cron might be ok.
</div></blockquote></div>
<div style="white-space:normal">
<p dir="auto">I assume the reasons for 10 min cron vs building on change <br>
is to ensure manual edits in jenkins UI do not stay in effect by accident ?</p>
<p dir="auto"></p></div>
<div style="white-space:pre-wrap"><blockquote style="border-left:2px solid #777; color:#777; margin:0 0 5px; padding-left:5px"><div dir="auto">2) the actual build jobs : I have a little PoC job there, let me try
</div><div dir="auto">and adapt that for the almighty-core and demonstrate the github
</div><div dir="auto">integration. We typically use the github webhooks to setup a notify
</div><div dir="auto">task into jenkins rather than the other way around. This has quite a
</div><div dir="auto">few advantages in that we can accept different kind of notify's and do
</div><div dir="auto">different operations based on those - however, it does come with the
</div><div dir="auto">downside that the ci-centos user needs to be added into the
</div><div dir="auto">contributors for the git repos in github.com. If this isnt seen as a
</div><div dir="auto">major problem, it would be the easiest, fastest path to take.
</div></blockquote></div>
<div style="white-space:normal">
<p dir="auto">We can add that if it is necessary - but is there any plans of having ci-centos<br>
have project specific users rather than global ci-centos users ?</p>
<p dir="auto">When I did JBoss Tools I did not accept letting JBoss Jenkins user have full<br>
access since it meant being okey that <em>anyone</em> by accident could nuke <br>
our repositories if they had access to Jenkins. </p>
<p dir="auto"><a href="https://www.reddit.com/r/programming/comments/1qefox/jenkins_developers_accidentally_do_git_push_force/" style="color:#3983C4">https://www.reddit.com/r/programming/comments/1qefox/jenkins_developers_accidentally_do_git_push_force/</a></p>
<p dir="auto">so yeah, for now we don't have much to loose - but something to consider how to handle better going forward.</p>
<p dir="auto">/max<br>
<a href="http://about.me/maxandersen" style="color:#3983C4">http://about.me/maxandersen</a></p>
</div>
</div>
</body>
</html>