Yep, afaik they do. The problem in this context is that due to the agents being ephemeral they are deleted immediately after they stop, and with that also this log is gone. So the idea was to add some basic output (eg the TaskID) in the actual build log for easier debugging for users.
So far I haven't found a way how I would put that information into the consoleLog per build for every node being spawned Am Mo., 13. Jan. 2020 um 16:59 Uhr schrieb Ullrich Hafner < ullrich.haf...@gmail.com>: > Am 13.01.2020 um 14:18 schrieb Andreas Sieferlinger < > psdsieferlin...@gmail.com>: > > Hey, > > i'm currently working on extending the Amazon ECS plugin a little bit to > add some information about the agent the job is run on the the builds log > in the UI. > For example the assumption was that the following line would create such a > log entry: > > https://github.com/jenkinsci/amazon-ecs-plugin/blob/logtest/src/main/java/com/cloudbees/jenkins/plugins/amazonecs/ECSLauncher.java#L152 > > > I never used the launcher extension point but from the code link it looks > that the method launch is invoked on the master so the lister messages > should end up in the log of the corresponding node. ( > http://localhost:8080/computer/[your-agent]/log) > Typically, a TaskListener reports the progress on the master... > > > As i learned on gitter (thanks btw to the people helping there) that this > is happening in a different context, and therefore is most likeley ending > up in the agents log. > > Do you see another way of providing information about the Agent within the > build log (eg somehow listening for builds and then trying to resolve that > information)? > > Thx for your help :) > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-dev+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/fbc6cdf5-6e3d-41c5-baa2-bf00548298b0%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-dev/fbc6cdf5-6e3d-41c5-baa2-bf00548298b0%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Jenkins Developers" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/jenkinsci-dev/peQPWLwdsT0/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > jenkinsci-dev+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/E43976B8-6093-4461-953A-51ECBEFCBE3A%40gmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/E43976B8-6093-4461-953A-51ECBEFCBE3A%40gmail.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAFXs%2BxyWifkFA-MrHtqb6Vr-WsFv_d_raFUUn4gr-c18raA1Og%40mail.gmail.com.
