GitHub Community
Replies: 59 comments 8 replies
-
|
This is really important. Currently logs of composite actions looks like mess. Why no update on this yet? |
Beta Was this translation helpful? Give feedback.
-
|
This is my biggest annoyance with composite actions atm. I am more than happy for them not to even be subspaced, but each step could be right at the top level just like regular steps. After all it is a "composite" of steps. |
Beta Was this translation helpful? Give feedback.
-
|
Bumping this as well, agree with the rest of the folks |
Beta Was this translation helpful? Give feedback.
-
|
We would also greatly benefit from this |
Beta Was this translation helpful? Give feedback.
-
|
This could make things a lot nicer. Upvoting!! |
Beta Was this translation helpful? Give feedback.
-
|
We would love to have this |
Beta Was this translation helpful? Give feedback.
-
|
Bumping, this would be so helpful |
Beta Was this translation helpful? Give feedback.
-
|
This is a must-have. Right now, I'm forced to do some awkward stuff with multiple jobs (despite the fact it could all be in one job) in order to try to make the "build" steps visually distinct from the "test" steps. Otherwise, if the build fails, it looks like the test job failed unless you look super closely. |
Beta Was this translation helpful? Give feedback.
-
|
I moved one of my job steps to composite action, to solve another github actions limitation (to be able to skip jobs and still run dependent ones without needing to spam jobs with |
Beta Was this translation helpful? Give feedback.
-
|
+1 bump bump |
Beta Was this translation helpful? Give feedback.
-
|
+1 its been such a long time and had many releases, this isn't fixed yet? |
Beta Was this translation helpful? Give feedback.
-
|
Hi guys! This is a bug at least since 2020. Can you guys please share some news, intentions or roadmap about this? |
Beta Was this translation helpful? Give feedback.
-
|
+1 This was initially presented in #1311 almost precisely three years ago. |
Beta Was this translation helpful? Give feedback.
-
|
ooh interesting. This is a pain point I haven't actually seen before :) let me dig in and learn. I will ensure that this goes onto our backlog of pain points to look at this year and if I have questions I will ensure I come back to this thread. |
Beta Was this translation helpful? Give feedback.
-
|
Same. I (and many other people) have probably used composite actions far less because of their illegibility issue. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks. It's not just a visual issue. It's difficult to ingest metrics and effectively determine bottlenecks when Composite Actions are rolled into a single step. Hopefully a solution will also result in more fine grained metrics. |
Beta Was this translation helpful? Give feedback.
-
|
ooh sorry I missed the offers! For those who are happy to run me through it :) if you give me permission I will nab an email address and drop you something over. (Trying to stay on lots of these has made my notifications a bit 🔥 ). Also with the caveat I have some leave coming up for a personal matter, so there may be a delay in the setup of that! |
Beta Was this translation helpful? Give feedback.
-
|
You have my permission, i look forward to it. |
Beta Was this translation helpful? Give feedback.
-
|
@nebuk89 You guys need better ways to handle customer feedback than random PM seeing a post after two years by accident... |
Beta Was this translation helpful? Give feedback.
-
|
This also affects how Datadog traces our GitHub workflows (context: https://docs.datadoghq.com/continuous_integration/pipelines/), example:
In the screenshot above: |
Beta Was this translation helpful? Give feedback.
-
|
See also actions/runner#1877 |
Beta Was this translation helpful? Give feedback.
-
|
+1 having composite actions should produce huge logs merged in just one step, as it makes it harder to read |
Beta Was this translation helpful? Give feedback.
and others
-
See actions/runner#1311.
Describe the enhancement
Currently when using composite actions, the logs are all aggregated as if it was one big action.
This becomes quickly problematic to debug an error occurring in one step since we can't easily see when one step starts and one ends.
The best would be to have the "sub-steps" clearly displayed in the interface liked the steps are for a "normal" actions. We could settle for a text based split but it would not be ideal.
I feel this will be essential for
ifconditions to be introduced (issue actions/runner#834), otherwise it will be a mess to try to debug which steps ran and which were skipped.Additional information
Here is what it could look like:
Beta Was this translation helpful? Give feedback.
All reactions