use-ink/cargo-contract

Follow-ups for the Verifiable Builds - #1148

Open

#1,214 opened on Jul 13, 2023

View on GitHub
 (0 comments) (0 reactions) (1 assignee)Rust (127 forks)github user discovery
enhancementgood first issue

Repository metrics

Stars
 (280 stars)
PR merge metrics
 (PR metrics pending)

Description

This is a tracking issue for all the follow-ups issues related to #1148

### Tasks
- [x] A GH workflow for an automatic release of the image tag upon a new release of cargo-contract
- [ ] Specify the docker command to be used for the build
- [ ] Recognise relative path dependencies and `--manifest-path` path to mount respective directories to the container
- [ ] Optimise the docker resources by either reusing the same container or re-create a single container instance and mounting crates.io local index

Contributor guide

Research direction
Review the original issue #1148 to understand the Verifiable Builds concept, then examine each open task (specify docker command, recognize relative path dependencies, optimize docker resources) to identify specific implementation details and existing workflows.
Tech stack
rustdockergithub actions
Domain
devopsci cdbuild systemblockchain
Issue type
DevOps
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Needs investigation
Prerequisites
RustDockerGitHub Actions
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40