[
https://issues.apache.org/jira/browse/HIVE-22942?focusedWorklogId=438414&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-438414
]
ASF GitHub Bot logged work on HIVE-22942:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 28/May/20 20:07
Start Date: 28/May/20 20:07
Worklog Time Spent: 10m
Work Description: kgyrtkirk commented on a change in pull request #948:
URL: https://github.com/apache/hive/pull/948#discussion_r432093713
##########
File path: Jenkinsfile
##########
@@ -0,0 +1,199 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements. See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership. The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance
+ * with the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+properties([
+ // max 5 build/branch/day
Review comment:
I haven't thinked about that - if it starts; it usually left to be
finished. however: anyone will be able to cancel builds on the jenkins ui
manually
Killing an in-flight build might not be the best - however all the builds
will be waiting for the lock to start - I believe at that point a check could
be than if there is any other pending run - and abort the actual build if there
are any....
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 438414)
Time Spent: 1h (was: 50m)
> Replace PTest with an alternative
> ---------------------------------
>
> Key: HIVE-22942
> URL: https://issues.apache.org/jira/browse/HIVE-22942
> Project: Hive
> Issue Type: Improvement
> Reporter: Zoltan Haindrich
> Assignee: Zoltan Haindrich
> Priority: Major
> Labels: pull-request-available
> Attachments: HIVE-22942.01.patch
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> I never opened a jira about this...but it might actually help collect ideas
> and actually start going somewhere sooner than later :D
> Right now we maintain the ptest2 project inside Hive to be able to run Hive
> tests in a distributed fashion...the backstab of this solution is that we are
> putting much effort into maintaining a distributed test execution framework...
> I think it would be better if we could find an off the shelf solution for the
> task and migrate to that instead of putting more efforts into the ptest
> framework
> some info/etc about how it compares to existing one:
> https://docs.google.com/document/d/1dhL5B-eBvYNKEsNV3kE6RrkV5w-LtDgw5CtHV5pdoX4/edit#heading=h.e51vlxui3e6n
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
