-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Fix #2363. Add /pre- and /post-entrypoint handling #2377
Fix #2363. Add /pre- and /post-entrypoint handling #2377
Conversation
Thank you for wanting to implement this, I think that I should provide you some pointer where these pre/post steps should be run to not cause some unexpected execution orders Those pre/pre steps are managed by the following: Lines 488 to 651 in 935e4c3
hasPreStep should return true if your preentrypoint field is non empty and the type is docker action, similar to post in the later methods. You could pass the entrypoint to the execasdocker and call it also for pre/post sections of the referenced code What you have done so far reads like you do
If you have more than a single step it could look like
I would expect, that is enshured by the advanced pre post logic written by former maintainers
|
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #2377 +/- ##
===========================================
+ Coverage 61.56% 76.37% +14.81%
===========================================
Files 53 61 +8
Lines 9002 7856 -1146
===========================================
+ Hits 5542 6000 +458
+ Misses 3020 1300 -1720
- Partials 440 556 +116 ☔ View full report in Codecov by Sentry. |
as far as I understand,
what is happening with composite actions, I did not understand at all. something terrible seems. if I understand correctly, I need to implement something like |
Feel free to ask me if something is unclear, as English is one of my foreign languages
yes, basically execJobContainer for docker actions _You have already written the code that can execute each pre, main and post stage for docker actions, so I think it's not much work to select one of the three via an additional parameter to execasdocker.
Yes, but only for nodejs actions. execAsDocker should be called there for docker actions Lines 188 to 193 in 935e4c3
That is handled by the existing code, therefore not your problem if you would put the change to runPreStep/hasPostStep
yes, probably just varying the following entrypoint is enough Lines 324 to 329 in 935e4c3
I don't understand what you mean by this, actions have 3 entrypoints (those are not called sequencially per action except if your job is basically a single docker action) this is implemented only for nodejs and composite actions while docker actions only execute in the main stage at this time |
Fix #2363. Add /pre- and /post-entrypoint handling