Hi Folks,
We are upgrading our Jenkins from 2.332.3 to 2.462.2 and as part of that have upgraded all our plugins to latest versions which are compatible with LTS 2.462.2 version, Jenkins is up with whatever changes we have made as part of plugins & now as part of testing we are facing below outstanding issues:
Parent Job when triggers Child Jobs, It fails in the Checkout Step since it considers BRANCH_NAME and Revision of First Repo for checking out Second Repo. which is blocker for us now & because of which we are not able to upgrade our Jenkins to LTS version, attaching screenshot for reference:
There are 2 repository which it calls in our pipeline - first time it checkout to correct first repository & later it again try to checkout to first repository branch revision itself instead of that it should checkout to second repository revision & perform remaining tasks.
Issue was specific to when build was triggered using parent job
Child jobs when triggered manually works fine
Another issue that we could see is, there are 2 broken images for console output & purge job offline agent option as below:
Thank you for reporting this issue. While I don’t have a direct solution to your problems, I can offer some guidance on how to proceed.
Report the Issue: I encourage you to inform the developers about the issues you encountered during your migration. You can do this using the feedback icons available on the LTS download page:
Review Existing Bugs: Please check if your issue is related to any of the bugs already filed for this LTS series:
Consider Version Differences: Please note that the issues you’re experiencing may be related to any changes implemented between versions 2.332.3 and 2.462.2.
File a New Bug: If you don’t find a matching issue, please don’t hesitate to file a new bug report. This will allow developers to assess and address your specific problem.
Update Recommendation: While it may not directly solve your current issue, I recommend upgrading to version 2.462.3, as it includes important security fixes.
Hi @poddingue , Thanks for your prompt response, can I get to know which plugins are affecting this broken images(purge Job offline agent & Console output option)??
The broken image for the purge job is coming from the plugin No Agent Job Purge, last released 12 years ago so still referring to old images that have been removed.
Not sure where the console link comes from, might be Extra Columns although this properly shows the icon properly in the latest release.
Hi @mawinter69, Thanks for your prompt response ,as you mentioned, no agent purge plugin not released since 8 years which I can also see on official release page but not sure how it is working on our old production Jenkins v2.332.3(on both old Jenkins (2.332.3)& new Jenkins (2.462.2) we have same plugin version for no agent purge)
Can you please guide us on same
Thanks,
Snehal
The plugin is relying that this image is provided by Jenkins core. But due to the UI renovation of Jenkins in the last years the image is no longer shipped. The problem has already been addressed in the plugin but no new release was done so the problem remains. You might want to adopt the plugin and create a new release if this is important for you.
Thanks @mawinter69 for explaining this in detail, regarding Console output you suggested to check extra-column plugin, I checked & we are using same plugin i.e. 1.26 which we are using in production old version (2.332.3) & in production it is working as expected.
If its related to extra-coulmn plugin then it could be same case as like no agent purge job plugin.
There is one more plugin which I checked i.e. dashboard-view which contributes a new view implementation that provides a dashboard / portal-like view for your Jenkins instance. but im not sure if its related to this issue
I don’t think you use the extra-columns plugin to show this link. The reason is that the extra-columns plugin is not print the text Console in the table header as it can be seen in the screenshot in your initial post. You might want to change the view to use the extra-column plugin instead or you use the Console Column
The log shows problems with name resolution
I can’t help further as I don’t user kubernetes
You still use an agent with remoting 4.13.3, that is quite old, maybe updating the the latest remoting version helps.
@mawinter69 ,As part of agent configuration, when we configure an agent, we specify the version of the remoting library that the agent should use. In our case, the agent is using jenkins/inbound-agent:4.13.3-1, which includes remoting version 4.13.3-1.
