-
Notifications
You must be signed in to change notification settings - Fork 157
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
Multiple steps in a job #123
Comments
This should be possible right now, provided the steps exist in the same workflow. For possible future releases:
Oh, and looking at your example, you also should have the |
I do have the package in my repo, so this is not the issue
I will try to add the exact same |
Hi, thanks @felfert, duplicating the |
Hi, |
Well, I guess that @uraimo is right. Problem is, that you did just post an example and not the real script that you actually use. I believe you use this one. In there, ALL invocations include the parameter |
Yep, you're correct this is the action I'm working on. Sorry for not giving the full script (as it was quite long with a lot of stuff, I did not want to put too many unrelated info). Or am I missing something obvious? |
So, I made a lighter script to test. Both github token and install part are required so that the steps reused the cached package:
Here is the script:
Here are the logs for step 1
Here are the logs for step 2
Here are the logs for step 3
|
Hello,
I was wondering if it was possible to use the same containers across multiple steps in the same jobs?
Something along the line of:
The idea is to split the building chain into multiple steps so it's easier to monitor.
It seems that at the moment, each steps is recreating the container at each run...
The text was updated successfully, but these errors were encountered: