[
https://issues.apache.org/jira/browse/BEAM-12830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17536241#comment-17536241
]
Beam JIRA Bot commented on BEAM-12830:
--------------------------------------
This issue is P2 but has been unassigned without any comment for 60 days so it
has been labeled "stale-P2". If this issue is still affecting you, we care!
Please comment and remove the label. Otherwise, in 14 days the issue will be
moved to P3.
Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed
explanation of what these priorities mean.
> Remove GoGradle plugin
> ----------------------
>
> Key: BEAM-12830
> URL: https://issues.apache.org/jira/browse/BEAM-12830
> Project: Beam
> Issue Type: Sub-task
> Components: sdk-go
> Reporter: Robert Burke
> Priority: P2
> Labels: stale-P2
> Time Spent: 9.5h
> Remaining Estimate: 0h
>
> GoGradle has never been updated to handle Go Modules, and it turns out it
> leaves .gogradle folders everywhere, which contain it's local gopath, and
> it's non-writable mod caches. This was the root cause of
> https://issues.apache.org/jira/browse/BEAM-12829.
> The solution is to stop using it, as it's never been ideal for our use, and
> replace it with direct shellouts to the go command.
> The main functionality that needs replacing is getting and using a set Go
> version so we can be sure what we're testing/validating against and building
> with, and using a common GoPath/ModuleCache throughout the repo. Otherwise,
> most instances can be replaced with simple tasks that call the Go function.
> A single module cache, if able to be reused across jenkins builds will also
> reduce build times. Note that these are for external versioned dependencies
> anyway, and not for Beam repo code.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
