Hi folks!
Just a quick heads-up that the ASF JIRA is currently locked down to
counter a spam attack. Unfortunately, this lock down prevents our
normal open-policy that allows anyone with a JIRA account to create,
assign, and comment on issues.
If you are caught up in this, please drop me a note
[
https://issues.apache.org/jira/browse/AVRO-1705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15254146#comment-15254146
]
Ryan Blue commented on AVRO-1705:
-
Sounds reasonable to me.
> Set up Jenkins job to test all languages
[
https://issues.apache.org/jira/browse/AVRO-1705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15254130#comment-15254130
]
Sean Busbey commented on AVRO-1705:
---
I think that should be a different ticket that's filed as an
[
https://issues.apache.org/jira/browse/AVRO-1705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15254119#comment-15254119
]
Ryan Blue commented on AVRO-1705:
-
Is this the right approach to CI?
I think we should consider
The second solution sounds like a great alternative.
Branch aliases are more straightforward than an implicit order-sensitive
policy. They also have the additional benefit of giving users a bit more
flexibility: since defaults are specified on the branches’ types, it is
possible to have
[
https://issues.apache.org/jira/browse/AVRO-1704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15254092#comment-15254092
]
Niels Basjes commented on AVRO-1704:
Question: What would be the preferred way of handling error
[
https://issues.apache.org/jira/browse/AVRO-1705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey updated AVRO-1705:
--
Priority: Critical (was: Major)
> Set up Jenkins job to test all languages using Docker
>
