Hi Myroslav, Thanks for pointing this out. I think there was a misconfiguration in a couple of the parameters in Github Pull Request builder Jenkins plugin configured by the Apache Infra team. I have now corrected those and hopefully, the new builds should validate the merge of commits in pull requests against the target branch. I will keep an eye on this for a few days.
@Dmytro: We use https://wiki.jenkins.io/display/JENKINS/GitHub+pull+request+builder+plugin to trigger our builds. As mentioned in the document, the phrase "retest this please" can be used to start a new build. Thanks, Vivek Ratnavel On Fri, Jan 19, 2018 at 3:15 AM, Myroslav Papyrkovskyy < mpapyrkovs...@hortonworks.com> wrote: > Vivek, it looks like something is really wrong with jenkins builds for > pull requests (to feature branches at least) > I’m trying to look at builds for my PR#150 (https://github.com/apache/ > ambari/pull/150). > linked build is > https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/193/ > > - list of changes seem to be completely unrelated > - build seem to be executed agains trunk, not branch-3.0-perf > - didn't find any mentions of my commit in output except linking build to > PR > > found another jenkins build with my PR in description > https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/198/ > > for branch-2.6 this time, list of changes is also unrelated. > > Can you check this please? > > > Regards, > Myroslav Papirkovskyi > > 13 січ. 2018 р. о 01:04 Vivek Ratnavel <vivekratna...@apache.org<mailto: > vivekratna...@apache.org>> написав(ла): > > Hi team, > > We have successfully configured Github PullRequest Builder > <https://wiki.jenkins.io/display/JENKINS/GitHub+pull+ > request+builder+plugin> > plugin. This will give us the ability to re-trigger build jobs by just > leaving a comment "@asfbot retest" in the PR. I have updated the How to > Contribute > <https://cwiki.apache.org/confluence/display/AMBARI/How+to+Contribute> > guide to include this piece. > > There was also an issue where github comments and events were not logged in > the "Worklog" section of corresponding JIRA. I worked with Infra team on > this and they have resolved this issue as well. We should now see all of > those comments in the "Worklog" section going forward. > > Please let me know if you have any questions on this. > > Thanks, > Vivek Ratnavel > > > > > On Fri, Jan 12, 2018 at 1:54 PM, Vivek Ratnavel <vivekratna...@apache.org< > mailto:vivekratna...@apache.org>> > wrote: > > Hi all, > > I see that there are many build failures and there is no way to re-trigger > the failed builds from github. So, I am working with Apache Infra team to > resolve this issue by using another Jenkins plugin. So, please bear with us > for another few hours while we test this new plugin to trigger the builds. > I will update soon on the status. > > Thanks, > Vivek Ratnavel > > On Thu, Jan 11, 2018 at 11:28 AM, Vivek Ratnavel <vivekratna...@apache.org > <mailto:vivekratna...@apache.org> > wrote: > > I have modified the name of the Jenkins job to avoid confusion. Here is > the new url - https://builds.apache.org/view/A/view/Ambari/job/Ambari-Gi > thub-PullRequest-Builder/ > > Thanks, > Vivek Ratnavel > > On Thu, Jan 11, 2018 at 10:16 AM, Vivek Ratnavel < > vivekratnave...@gmail.com<mailto:vivekratnave...@gmail.com>> wrote: > > That is a good point, Attila. It is definitely possible. Let's work on > this. > > On Thu, Jan 11, 2018 at 9:52 AM, Doroszlai, Attila < > adorosz...@apache.org<mailto:adorosz...@apache.org>> wrote: > > Would you like to work with Vivek on this? > > Sure. > > -Attila > > On Thu, Jan 11, 2018 at 6:29 PM, Yusaku Sako <yus...@hortonworks.com< > mailto:yus...@hortonworks.com>> > wrote: > That is a good suggestion, Attila. > Would you like to work with Vivek on this? > > Yusaku > > On 1/11/18, 2:25 AM, "Doroszlai, Attila" <adorosz...@apache.org<mailto: > adorosz...@apache.org>> > wrote: > > Hi Vivek, > > Would it be possible to put the script that the job runs under > version > control (somewhere in dev-support directory)? > > -Attila > > On Thu, Jan 11, 2018 at 1:30 AM, Vivek Ratnavel > <vivekratna...@apache.org<mailto:vivekratna...@apache.org>> wrote: > Hi Team, > > I have created a jenkins job to monitor Github pull requests > and build and > report tests at > https://builds.apache.org/view/A/view/Ambari/job/Github-Pull > Request-Builder/ > > I will keep an eye on it for the next few days and keep > modifying its > configuration if needed to work as expected. It is expected > that ASF bot > will leave a comment in the Pull Request along with a link to > the build job > for every new pull request. Please let me know if you feel > something wrong > about this job. > > Thanks, > Vivek Ratnavel > > On Tue, Jan 9, 2018 at 3:32 PM, Yusaku Sako < > yus...@hortonworks.com<mailto:yus...@hortonworks.com>> wrote: > > Hi Vivek, > > Thanks for looking into this. > I’ve given you edit access to builds.apache.org<http://builds.apache.org> > Jenkins jobs. > > Yusaku > > On 1/9/18, 3:07 PM, "Vivek Ratnavel" <vivekratna...@apache.org<mailto: > vivekratna...@apache.org>> > wrote: > > Hi Team, > > There is a jenkins job > <https://builds.apache.org/view/A/view/Ambari/job/Ambari- > trunk-find-patches-available/> > that runs every 10 minutes looking for Ambari JIRA with > new patches. > This > will no longer run due to our new Github pull request > model to review > and > merge changes. > > I can edit this job to look for new github pull requests > and run tests > on > the pull request branch. But, I don't have permissions to > edit or > create > new jenkins job at builds.apache.org<http://builds.apache.org>. > > I request the PMC chair to grant me access to edit the > jenkins job to > do > the needful. > > Thanks, > Vivek Ratnavel > > > > > > > > > > > -- > -Vivek Ratnavel S > > > > > >
