By the way, I agree on the idea to use Travis in addition to Jenkins for fault tolerance, but I was unable to enable Travis CI for our repository on the web (https://travis-ci.org/apache/incubator-nemo) as it says that I do not have enough rights. Could we check if someone has enough rights to do this? Our repository already has .travis.yml file set up.
Wonook 2018-03-04 21:46 GMT+09:00 Byung-Gon Chun <[email protected]>: > Thanks! > > > > On Sun, Mar 4, 2018 at 9:43 PM, 송원욱 <[email protected]> wrote: > > > I've set up Jenkins CI. You can see them under > > https://builds.apache.org/job/Nemo/ . There's one that runs daily for > the > > master branch as a cron job, and there's another for our pull requests. > > However, I was unable to find the credentials on the Jenkins Job for our > > bot (probably one of the 'asfbot' or 'asfgit' users) to update the commit > > status on our GitHub. After that, it should work without a problem. > > > > Wonook > > > > 2018-03-04 16:44 GMT+09:00 Byung-Gon Chun <[email protected]>: > > > > > I added you and Jangho to hudson-jobadmin. > > > You should be able to set up Jenkins CI. > > > Let me know if you need other help. > > > > > > Thanks. > > > -Gon > > > > > > > > > > > > On Sun, Mar 4, 2018 at 4:41 PM, Byung-Gon Chun <[email protected]> > wrote: > > > > > > > Hi Wonook, > > > > > > > > This page is a good starting point to set up Jenkins. > > > > https://cwiki.apache.org/confluence/display/INFRA/Jenkins > > > > https://ci.apache.org/ > > > > > > > > Taegeon has experience on setting up CIs in Apache. > > > > > > > > It would be great to set up both Jenkins and Travis for fault > > tolerance. > > > :) > > > > > > > > Thanks. > > > > -Gon > > > > > > > > > > > > On Sun, Mar 4, 2018 at 4:34 PM, 송원욱 <[email protected]> wrote: > > > > > > > >> Now that we have our codebase migrated to apache, we should start > > > setting > > > >> up CI (probably Jenkins or Travis, or both) for our master branch. > > > >> > > > >> Can we set them up or should we open a ticket in INFRA? > > > >> > > > >> Moreover, to ensure the use of CI, we can set up a few things on > > GitHub. > > > >> We > > > >> can set our master branch as a protected branch and tick a few > options > > > >> like > > > >> > > > >> - Require pull request reviews before merging > > > >> - Dismiss stale pull request approvals when new commits are pushed > > > >> - Require status checks to pass before merging > > > >> - Require branches to be up to date before merging > > > >> - Include administrators > > > >> > > > >> These are the options that are ticked in our old repository. > > > >> > > > >> > > > >> Wonook > > > >> > > > > > > > > > > > > > > > > -- > > > > Byung-Gon Chun > > > > > > > > > > > > > > > > -- > > > Byung-Gon Chun > > > > > > > > > -- > Byung-Gon Chun >
