tikal-multijob-plugin
tikal-multijob-plugin copied to clipboard
jenkinsci
Jobs status is greyed out even if build is running
Sub jobs does not display the status even if they are running. With the jenkins update to the version 2.107.2, status of sub jobs are greyed out and gives hard time to figure out the current phase of job while running.
We are also facing the same issue after the plug-in upgrade to 1.30 with Jenkins version 2.107.2
Downgrade to 1.29 from 1.30 resolved the issue for now. I think it's a regression .
I was unable to recreate this issue using Jenkins 2.107.2/3 and multijob 1.30 on a newly created multijob job. Please elaborate on the steps taken to recreate this issue. Also, try to create new multijob, phase, and an example job and confirm this issue recreates
@cohencil
Jenkins Version: 2.107.2/3
Before Upgrade:
Multi Job Project is working fine as below:
After Plugin Upgrade:
Updated Version 1.30
Job Icons are greyed out.
When created new multi-job project (with the same set of jobs), It works fine:
Jobs which are created before upgrade are having the issue.
@kkrhdd can you compare the config.xml of the upgraded job with the newly created job? There is probably something missing from the upgraded job - which should be handled by the plug-in.
Great - so if the plug-in /expects/ a jobAlias it should be added as part of the upgrade process.
As a work-around, editing and saving an upgraded multi-job project may be enough to add the missing properties - I will try this later on.
Unfortunately simply saving an existing job only results in empty jobAlias tags being added.
When going to the configuration, the 'Job alias' is available as an editable field - so I suppose the work-around is to copy / paste the 'Job name' to the 'Job alias'.
After adding the jobAliases everything works - but - all jobs are shown with their alias in brackets. I noticed that the comparison screen shots above do not show an extra alias. So figured that the jobAlias is /not/ mandatory. I removed the jobAlias thru the user interface again and everything seems to be behaving.
Conclusion: saving the job (which adds the jobAlias tags) is probably enough even though this step should not be necessary.
Update: even after running with saved jobs in which the jobAlias is set to empty - the update mechanism of a completed or running job does not look right. When the multi-job is complete, the status of the sub jobs looks pretty random and does not reflect the status of the job executed within the multi-job's context. I have subjobs reporting failed, when the last 10 builds were fine and the 11th oldest subjob failed. Delete the older failure resulted in the subjob within the multi-job showing 'completed' again.
I am reverting to the previous version of this plug-in, I hope the jobAlias change #126 is either thoroughly fixed and tested or rolled back.
This PR fixes the issue: https://github.com/jenkinsci/tikal-multijob-plugin/pull/142
. When the multi-job is complete, the status of the sub jobs looks pretty random and does not reflect the status of the job executed within the multi-job's context. I have subjobs reporting failed, when the last 10 builds were fine and the 11th oldest subjob failed. Delete the older failure resulted in the subjob within the multi-job showing 'completed' again.
@stefandrissen , I agree there's issue. That is #142 does not fully resolve it, however it solves "all jobs being gray" issue at least.
First I am very sorry for all the trouble i made with the jobAlias Changes... But I finally fixed the issue @stefandrissen talked about in detail. I also included the Fix from @vlsi in my own way so in other words it is not necessary to merge #142 .
It doesn't look fixed. Installed latest version of plugin and we still doesn't see the status of running sub-jobs.
Still looks like this is a problem, just upgraded to Jenkins 2.150.2 and MultiJob 1.32 and the issue is there with new and existing MultiJobs, roll back to 1.29 and problem goes away.
Sorry for the necro-bump, but any plans on fixing this?
Still not working on the latest 1.32 release.
I tried installing the .hpi file for the 1.29 version, taken from the plugins repository, but then the multi-job build step just stopped working entirely; the sub-jobs never got triggered, the parent job would just result in success always.
The plugin is incredibly useful overall, specially when paired with job-dsl, but this bug really makes the multi-job view that is created pretty much useless.
This is a problem for us also in Pipeline Multi Job, any idea by when the issue is planned to be fixed?
I'll try to find time for this soon. If someone can PR me on it, it would be great.
Yoram
On Mon, May 18, 2020 at 3:49 PM bpbhai [email protected] wrote:
This is a problem for us also in Pipeline Multi Job, any idea by when the issue is planned to be fixed?
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/jenkinsci/tikal-multijob-plugin/issues/135#issuecomment-630160479, or unsubscribe https://github.com/notifications/unsubscribe-auth/AASZBEV5CWKQHL6G47DA7VTRSEVF7ANCNFSM4E6LIC2A .
-- Yoram Michaeli DevOps Tech Leader 052-5766838 [email protected]
