FWIW, I created this JIRA issue to track the decision.
https://issues.apache.org/jira/browse/INFRA-17540
Thanks,
-Alex
On 12/13/18, 12:22 PM, "Zoran Regvart" wrote:
Hi Allen, Alex and Builders,
I must say that I also think like Alex, who's to say that the builds
done on a CI serve
> On Jan 3, 2019, at 7:34 AM, Christofer Dutz wrote:
>
> Hi Allen,
>
> thanks for that ... if I had known that simply selecting the "GitHub" as
> source instead of the generic "Git" ... would have made things easier ...
> however it seems that we have exceeded some sort of API usage limit:
Ok ... should have been a "paste" and not a "send":
[Thu Jan 03 15:32:23 UTC 2019] Starting branch indexing...
15:32:23 Connecting to https://api.github.com with no credentials, anonymous
access
ERROR: [Thu Jan 03 15:32:23 UTC 2019] Could not update folder level actions
from source a92f1485-12eb
Hi Allen,
thanks for that ... if I had known that simply selecting the "GitHub" as source
instead of the generic "Git" ... would have made things easier ... however it
seems that we have exceeded some sort of API usage limit:
Am 03.01.19, 16:24 schrieb "Allen Wittenauer"
:
> O
> On Jan 3, 2019, at 7:15 AM, Christofer Dutz wrote:
>
> Is there a way to check the status of a project?
There isn’t any sort of global “bad list”. haha. At least, I know I
personally gave up trying to keep track of the strays …
> I would like to help improve and have done some t
> On Jan 3, 2019, at 7:14 AM, Christofer Dutz wrote:
>
> I can't see that ... where can we find that ... and we don't want to
> automatically push everything that works.
>
> From the description of "Enable Git validated merge support" it would
> automatically push everything that passes the
Is there a way to check the status of a project?
I would like to help improve and have done some things, but I need a way to see
that what I'm doing is helping.
Chris
Am 03.01.19, 16:10 schrieb "Allen Wittenauer"
:
> On Jan 3, 2019, at 3:11 AM, Bertrand Delacretaz
wrote:
I can't see that ... where can we find that ... and we don't want to
automatically push everything that works.
From the description of "Enable Git validated merge support" it would
automatically push everything that passes the build ... that doesn't sound
desirable.
When I look at the "GitHub-P
> On Jan 3, 2019, at 3:11 AM, Bertrand Delacretaz
> wrote:
>
> Hi,
>
> On Fri, Dec 21, 2018 at 10:53 PM Allen Wittenauer
> wrote:
>
>> ...Culprits: Accumulo, Reef, and Sling.
>
> Sling has a few hundred modules, if you have more specific info on
> which are problematic please let us know
> On Jan 3, 2019, at 7:01 AM, Christofer Dutz wrote:
>
> Hi all,
>
> the IoTDB Team would like to have PRs automatically built. When using the
> Multibranch Pipeline plugin it already would validated PRs from a branch, but
> not from a fork.
> Now I was guided here and to this page:
> https
Hi all,
the IoTDB Team would like to have PRs automatically built. When using the
Multibranch Pipeline plugin it already would validated PRs from a branch, but
not from a fork.
Now I was guided here and to this page:
https://cwiki.apache.org/confluence/display/INFRA/GitHub+Pull+Request+Builder
Hi,
On Fri, Dec 21, 2018 at 10:53 PM Allen Wittenauer
wrote:
> ...Culprits: Accumulo, Reef, and Sling.
Sling has a few hundred modules, if you have more specific info on
which are problematic please let us know so we have a better chance of
fixing that.
-Bertrand
12 matches
Mail list logo
