-
Notifications
You must be signed in to change notification settings - Fork 240
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
time_since_last_job_run and last_job_run_duration updated only when the status of job is changing #119
Comments
Hi @mkrvanton, indeed, this is a bug related to #106 I fixed through this commit : 5a91ba2 I will release it as part of |
@mkrvanton can you please try to upgrade to 0.3.3 and let us know if it works properly? |
gitlab_ci_pipeline_time_since_last_job_run_seconds is updating fine for running jobs, but doesnt update for successful/faled jobs, gitlab_ci_pipeline_last_job_run_status is not updating (stuck in running state) :( |
👋 hey @mkrvanton, I have just released 0.3.4 which should be fixing those issues! 🤞 |
Hey @mvisonneau,
|
can you run it in with |
@mvisonneau I have a logs.. can I send it to you as a private message or by the email? |
Hi, i have same problem(?), pipeline of my project ran a few seconds ago, but that's what i see: gitlab_ci_pipeline_time_since_last_run_seconds{kind="branch",project="gitlab/play_with_ci",ref="master",topics="",variables=""} 1.664266e+06 |
@mkrvanton sure, here is my keybase: https://keybase.io/mvisonneau |
@DjinNO I am not sure to understand how it does compare to this issue nor what is wrong with the log line you pasted 🤔 |
Sorry |
👋 hey @mkrvanton, thanks for the logs and apologies for the late feedback on this! I managed to reproduce it locally and to sort it out with 48a6778! it will be part of the next release, in the meantime you can try it out from the source if you want or with the |
These changes are part of the 0.4.0 release! Feel free to reopen if necessary @mkrvanton 🙇! |
Hi!
Thank you so much for your pipeline-exporter project it is awesome! :)
After some short research, I was found one issue as I think...
I checked it on 0.3.2 version.
As I guess gitlab_ci_pipeline_time_since_last_job_run_seconds and gitlab_ci_pipeline_last_job_run_duration_seconds updated only when the status of job is changing.
Is it a bug or a feature?
The text was updated successfully, but these errors were encountered: