Skip to content
This repository has been archived by the owner on Jan 19, 2024. It is now read-only.

Send JES events as "job executor using $IMAGE" events #286

Open
agardnerIT opened this issue Jun 21, 2022 · 2 comments
Open

Send JES events as "job executor using $IMAGE" events #286

agardnerIT opened this issue Jun 21, 2022 · 2 comments
Labels
type:improvement Improves/enhances an existing feature

Comments

@agardnerIT
Copy link
Contributor

Currently every job that JES runs has a .started and .finished name as "job executor service".

It would be really nice to see that JES is being used to run X container image.

So rather than job executor service started we see something like alpine/helm:3.7.2 by job executor service started

@agardnerIT agardnerIT changed the title Send JES events as "job executor using $IMAGE" started Send JES events as "job executor using $IMAGE" events Jun 21, 2022
@Raffy23
Copy link
Member

Raffy23 commented Jun 22, 2022

I think that it's a good idea to add more information to the started event, but we probably can't just directly include the images in the message, because the job-executor can start multiple named actions, which can contain multiple named tasks. So we can potentially run multiple images in one .started event.

But besides that, I'm currently not sure if we can attach the required information to a .started event, such that it will be displayed correctly in the UI.

@christian-kreuzberger-dtx
Copy link
Contributor

That would be information we could add to a .status.changed event within the message. See keptn/spec/CloudEvents.md for reference of this type.

@christian-kreuzberger-dtx christian-kreuzberger-dtx added the type:improvement Improves/enhances an existing feature label Jun 23, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type:improvement Improves/enhances an existing feature
Projects
None yet
Development

No branches or pull requests

3 participants