You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Every time we update that file in github, it is no longer possible for users to build their plugins from the same original source.
Also, if their build system does not have external internet access, the build can never succeed, unless they figure out how to cache this code somewhere that gradle will find and use it--I'm not sure if that's possible?
We should, as part of building this tool, include a static, versioned copy of all required code to ensure that the results of what it builds are deterministic and cannot be compromised without leaving a clear trace.
The text was updated successfully, but these errors were encountered:
plambert
changed the title
The build.gradle should not pull in unversioned, remote code
The build.gradle in the template should not pull in unversioned, remote code
Oct 25, 2018
plambert
changed the title
The build.gradle in the template should not pull in unversioned, remote code
The build.gradle in the templates should not pull in unversioned, remote code
Oct 25, 2018
From
src/main/resources/templates/script-plugin/filecopier/build.gradle.template
:Every time we update that file in github, it is no longer possible for users to build their plugins from the same original source.
Also, if their build system does not have external internet access, the build can never succeed, unless they figure out how to cache this code somewhere that gradle will find and use it--I'm not sure if that's possible?
We should, as part of building this tool, include a static, versioned copy of all required code to ensure that the results of what it builds are deterministic and cannot be compromised without leaving a clear trace.
The text was updated successfully, but these errors were encountered: