universe.dagger.io/examples/todoapp on europa-docs-plan-tanguy-fresh-pair-of-eyes [$!?] via v17.4.0
❯ bin/dagger do build
4:32PM FTL failed to execute plan: cyclic task dependency:
task client.filesystem."./_build".write refers to
task actions.build.contents._copy refers to
task actions.build.run._exec refers to
task actions.test._exec refers to
task actions.deps._dag."2"._exec refers to
task actions.deps._dag."1"._copy refers to
task client.filesystem."./_build".write:
/Users/gerhard/github.com/gerhard/dagger/pkg/universe.dagger.io/cue.mod/pkg/dagger.io/dagger/fs.cue:114:2
/Users/gerhard/github.com/gerhard/dagger/pkg/universe.dagger.io/docker/build.cue:49:2
/Users/gerhard/github.com/gerhard/dagger/pkg/universe.dagger.io/docker/run.cue:162:2
Signed-off-by: Gerhard Lazu <gerhard@lazu.co.uk>
Thank you Tanguy for the "fresh pair of eyes" perspective.
Thank you Tom for the link suggestions.
Supersedes https://github.com/dagger/dagger/pull/1847
Signed-off-by: Gerhard Lazu <gerhard@lazu.co.uk>
This commit adds `node_modules` to dagger run commands so cached builds have
similar speed times as running commands locally directly through yarn
<script>
Signed-off-by: Marcos Lilljedahl <marcosnils@gmail.com>
This is the first thing that someone new to Dagger tried to do.
I wanted to capture it in an example so that we can reference in the future.
I am sure that we can improve on this small step in a direction that I
have seen a new member take.
Signed-off-by: Gerhard Lazu <gerhard@lazu.co.uk>
The file is entirely commented and I keep getting e-mails from GH on
each PR complaining about ".github/workflows/test-docs.yml: No jobs were
run"
Signed-off-by: Andrea Luzzardi <aluzzardi@gmail.com>
The todoapp example contains a Netlify plan which uses the latest dagger
additions: do & Client API. We are thinking of merging the examples
repository into this one to make working with this easier. This is a
step in that direction.
We are not using the yarn package so that we can revert
https://github.com/dagger/dagger/pull/1673 without breaking this
implementation.
The GitHub Action is WIP, we will continue with that tomorrow:
https://github.com/dagger/dagger-for-github/issues/24
Signed-off-by: Gerhard Lazu <gerhard@lazu.co.uk>
The goal is to preserve the container.input interface so that custom
images can be specified, as per yarn/test/test.cue while keeping the
initial fix for https://github.com/dagger/dagger/issues/1670
Signed-off-by: Gerhard Lazu <gerhard@lazu.co.uk>
If multiple yarn.#Run commands run in parallel, they will corrupt each
other's yarn cache mount. Because we extract yarn install into a
separate step, LLB will dedup the yarn install step and only run it
once, regardless how many yarn.#Run commands run in parallel.
Fixes https://github.com/dagger/dagger/issues/1670
Signed-off-by: Gerhard Lazu <gerhard@lazu.co.uk>
- Simplify cache id parameter with a field `name`
- Configure GOOS & GOARCH values
- Container image can now be overridden
- Simplify build export
Signed-off-by: Vasek - Tom C <tom.chauveau@epitech.eu>
- Improve #Container with a better docker.#Run integration
- Supports concurrency caching in #Container
- Simplify code maintainability and readability
- Simplify binary export in #Build
- Support multi binary building
- External #Version management
Signed-off-by: Vasek - Tom C <tom.chauveau@epitech.eu>
Definition are now split in their own file.
`#Image` is a simple base image to set up a go container
`#Container` is a standalone environment to execute go command, any go command
should use this definition.
It shares `docker.#Run` fields to easily maintains this definition.
`#Build` and `#Test` are high level definition that use `#Container` to
execute common go operation in a CI.
Those definitions are tested with a simple greeting package.
Signed-off-by: Vasek - Tom C <tom.chauveau@epitech.eu>
