[
https://issues.apache.org/jira/browse/BEAM-13187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17438923#comment-17438923
]
Brian Hulette edited comment on BEAM-13187 at 11/4/21, 8:39 PM:
----------------------------------------------------------------
Yeah this is tricky to integration test, since there's a certain code path
taken iff we're running from a released version of Beam.
We could make it download a SNAPSHOT jar if a local jar doesn't exist. Then
that could be continuously tested, but as Cham points out the version skew
might make that unstable. Do we have a way to run tests only on commits that
generate snapshots?
was (Author: bhulette):
Yeah this is tricky to integration test, since there's a certain code path
taken iff we're running from a released version of Beam.
We could make it download a SNAPSHOT jar if a local jar doesn't exist, but as
Cham points out the version skew might make that unstable. Do we have a way to
run tests only on commits that generate snapshots?
> BeamJarExpansionService fails to stage remote artifacts
> -------------------------------------------------------
>
> Key: BEAM-13187
> URL: https://issues.apache.org/jira/browse/BEAM-13187
> Project: Beam
> Issue Type: Bug
> Components: cross-language, sdk-py-core
> Reporter: Brian Hulette
> Assignee: Robert Bradshaw
> Priority: P1
> Fix For: 2.34.0
>
> Time Spent: 7h 40m
> Remaining Estimate: 0h
>
> See https://github.com/apache/beam/pull/15638/files#r742413302
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
