[
https://issues.apache.org/jira/browse/RATIS-672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16937319#comment-16937319
]
Clay B. commented on RATIS-672:
-------------------------------
[~elserj] in the vein of ensuring all is checksumed and the {{docker}} and
{{vagrant}} processes share URLs/checksums, I think I have an updated process.
Interestingly/disturbingly, it does not appear that checksums are officially
published for Protobuf per [Issue
#2717|https://github.com/protocolbuffers/protobuf/issues/2717]. I have used
what I got for the GitHub artifact for {{protoc}} 3.5.0. Also it seems if one
specifies a Vagrant box checksum, at least the way I did {{vagrant destroy -f
ratis-build}} fails.
I again updated the patch on GitHub to ensure Docker and Vagrant use the same
artifacts. I tested the patch running:
* {{./start-build-env.sh}}
* {{cd dev-support/vagrant/ && ./run_all_tests.sh build}}
* It reports: {{/bin/sh: 1: ratis_protoc_url: Need $ratis_protoc_url}} if one
runs {{cd dev-support/docker && docker build .}} (without first running
{{source dev-support/binary_locations.sh}} for the necessary env. vars.).
Are there any other entry points for the Docker build than
{{start-build-env.sh}}? Is it okay I did not add in verificiation for
{{dumb-init_1.2.0_amd64}} and {{byteman-4.0.4.jar}} in
{{ratis-examples/src/main/docker/Dockerfile}}?
> Vagrant and Docker Test 404 on Maven Download
> ---------------------------------------------
>
> Key: RATIS-672
> URL: https://issues.apache.org/jira/browse/RATIS-672
> Project: Ratis
> Issue Type: Improvement
> Components: test
> Reporter: Clay B.
> Assignee: Clay B.
> Priority: Trivial
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The Vagrant tests are
> [pointing|https://github.com/apache/incubator-ratis/blob/35838f032a4096d78843130fa1435bcddf5ce961/dev-support/vagrant/Vagrantfile#L92]
> to a specific mirror and a URL which broke with the new Maven 3.6.x release.
> We should point to an {{archive.apache.org}} URL if I understand correctly.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
