Re: [VOTE] [RESULT] Move ASF Github Bot comments to Worklog in JIRA

2018-01-11 Thread Vivek Ratnavel
Update: The comments should now be pushed to "Worklog" section in JIRA. -Vivek Ratnavel On Thu, Jan 11, 2018 at 4:51 PM, Vivek Ratnavel wrote: > Update: I have created a JIRA against INFRA - https://issues.apache.org/ > jira/browse/INFRA-15832 > > -Vivek Ratnavel > > On Thu, Jan 11, 2018 at 4:3

Re: [VOTE] [RESULT] Move ASF Github Bot comments to Worklog in JIRA

2018-01-11 Thread Vivek Ratnavel
Update: I have created a JIRA against INFRA - https://issues.apache.org/jira/browse/INFRA-15832 -Vivek Ratnavel On Thu, Jan 11, 2018 at 4:36 PM, Vivek Ratnavel wrote: > The vote passed with the following +1's: > > Binding (PMC): > Nate Cole > Jonathan Hurley > > Non-binding: > Sandor Molnar > A

[VOTE] [RESULT] Move ASF Github Bot comments to Worklog in JIRA

2018-01-11 Thread Vivek Ratnavel
The vote passed with the following +1's: Binding (PMC): Nate Cole Jonathan Hurley Non-binding: Sandor Molnar Attila Doroszlai Krisztian Kasa Balazs Bence Sari Dmytro Grinenko I will follow-up with Apache Infra to move the ASF Github Bot comments to the Worklog section in JIRA. Thank you, Vivek

Re: New JIRA - Commit messages

2018-01-11 Thread Vivek Ratnavel
Hi Nate, I find the addition of (username) to commit messages as redundant, since the user who contributed can be identified from the "Author" tag in git command line. I use "git log --grep=AMBARI-X" and get an output with the author tag. Regardless of the committer who merged the pull request

New JIRA - Commit messages

2018-01-11 Thread Nate Cole
All, Previous to the fork/pull request framework, we used to use commit message variations like so: “AMBARI-XX. Great change for stack (ncole)”   (for committers) or “AMBARI-XX. Great change for stack (Joe Smith via ncole)”   (for contributors) Commits have start

Re: Wait for pending Jenkins job before Merge

2018-01-11 Thread Vivek Ratnavel
This is the new url due to name change - https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/9/console On Thu, Jan 11, 2018 at 1:17 PM, Dmytro Grinenko wrote: > How to check this job? For me it showing as 404 Not Found > > -Original Message- > From: Vivek Ratnavel [mailto:viv

RE: Wait for pending Jenkins job before Merge

2018-01-11 Thread Dmytro Grinenko
How to check this job? For me it showing as 404 Not Found -Original Message- From: Vivek Ratnavel [mailto:vivekratnave...@gmail.com] Sent: Thursday, January 11, 2018 9:18 PM To: dev@ambari.apache.org Subject: Re: Wait for pending Jenkins job before Merge It looks like the build failed -

Re: Permissions to modify Jenkins job at builds.apache.org

2018-01-11 Thread Vivek Ratnavel
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-Github-PullRequest-Builder/ Thanks, Vivek Ratnavel On Thu, Jan 11, 2018 at 10:16 AM, Vivek Ratnavel wrote: > That is a good point, Attila. It is definite

Re: Wait for pending Jenkins job before Merge

2018-01-11 Thread Vivek Ratnavel
It looks like the build failed - https://builds.apache.org/job/Github-PullRequest-Builder/9/console On Thu, Jan 11, 2018 at 11:15 AM, Siddharth Wagle wrote: > I believe there is a problem in posting back the result: > > > https://github.com/apache/ambari/pull/90? > > > - Sid > > > __

Re: Wait for pending Jenkins job before Merge

2018-01-11 Thread Siddharth Wagle
I believe there is a problem in posting back the result: https://github.com/apache/ambari/pull/90? - Sid From: Vivek Ratnavel Sent: Thursday, January 11, 2018 10:58 AM To: dev@ambari.apache.org Subject: Wait for pending Jenkins job before Merge Hi Team, I a

Wait for pending Jenkins job before Merge

2018-01-11 Thread Vivek Ratnavel
Hi Team, I am happy that the jenkins job works as expected. It gets triggered on every new pull request and performs the following tasks: - Validate the merge - Build Ambari - Run unit tests The job will repo

Re: Permissions to modify Jenkins job at builds.apache.org

2018-01-11 Thread Vivek Ratnavel
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 wrote: > > Would you like to work with Vivek on this? > > Sure. > > -Attila > > On Thu, Jan 11, 2018 at 6:29 PM, Yusaku Sako > wrote: > > That is a good suggestion, At

Re: Permissions to modify Jenkins job at builds.apache.org

2018-01-11 Thread Doroszlai, Attila
> Would you like to work with Vivek on this? Sure. -Attila On Thu, Jan 11, 2018 at 6:29 PM, Yusaku Sako 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" wrote: > > Hi Vivek, > > Would it be

Re: Permissions to modify Jenkins job at builds.apache.org

2018-01-11 Thread Yusaku Sako
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" wrote: Hi Vivek, Would it be possible to put the script that the job runs under version control (somewhere in dev-support directory)? -Attila

Re: Permissions to modify Jenkins job at builds.apache.org

2018-01-11 Thread Doroszlai, Attila
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 wrote: > Hi Team, > > I have created a jenkins job to monitor Github pull requests and build and > report tests

Call for Presentations FOSS Backstage open

2018-01-11 Thread Isabel Drost-Fromm
Hi, As announced on Berlin Buzzwords we (that is Isabel Drost-Fromm, Stefan Rudnitzki as well as the eventing team over at newthinking communications GmbH) are working on a new conference in summer in Berlin. The name of this new conference will be "FOSS Backstage". Backstage comprises all things

[AMBARI-1518] Can I ask AMBARI-1518(Multiple Cluster Supported)'s progress?

2018-01-11 Thread 李书明
Our team have used Apache Ambari recently, however we met a common problem: we always want to install /asdfghjk multi Kafka/Elasticsearch/Solr multi cluster, this is because our team provide a basic service for multi other teams. I have found https://issues.apache.org/jira/browse/AMBARI-1518