-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot remove artifact of job #14
Comments
Also, trying to run Do we maybe need an :rm-all job task that does recurse into images used by the job and removes them? |
Hm. Looks like https://github.com/dnephin/dobi/blob/master/tasks/job/remove.go#L14 answers part of my previous question. The intent of JOB:rm is to remove both the use container and any artifacts. What about dependencies? |
It should remove both the artifact and the container. The warning on the missing container should be fixed by #15. Can you confirm if the artifact (the files) were removed correctly?
Correct, it would be good to add
Correct, and with #15 that should be the case.
I've been thinking about something like that. One idea I had was to create a built-in task called
I think I'd like to avoid having For now, I hope that |
I'm trying to verify this, but unfortunately I'm still having trouble with building dobi. :/ The docker command got past the part that was failing before, but then died on this:
One other odd thing I noted is after attempting to run that docker command, the image left in my docker has an unusual tag name:
So, I tried to run the released version of dobi in this cloned dobi repo to build the test branch you offered. That fails in the linter with this error:
I copied the pre-commit.log file out of the container, and it had this:
Unfortunately, I'm not sure at all where to go from here. I don't suppose there is any chance you use gitter.im or slack or hangouts or something and would be able to chat real quick to try to get me over this hump? |
I just created https://gitter.im/dnephin-dobi/Lobby |
This problem was related to having my dobi repo as a submodule of another repo. The self building logic doesn't like that as it can't see the actual .git definition which is in the parent outside the build context. |
When running the examples/minimal-docker-image project, I wasn't able to follow the instructions as currently written in the README.md. I submitted a quick fix/workaround PR there, but it seems there are a couple of underlying bugs I'll also raise.
In that example, there is a job task with the name "binary". It uses the builder image and produces the artifact dist/bin/hello.
If you try to run dobi binary:rm, it fails with the following warning:
Looks like it is mistakenly trying to target a container rather than the artifact. If I look into this and fix it, I'm assuming that the binary:rm shouldn't cascade down to the builder image and rm that as well, right?
The text was updated successfully, but these errors were encountered: