Status: Open (View Workflow)
Jenkins version 2.377 Clean install All plugins up to date Jenkins running on RHEL 7 server using Amazon Coretto V11 (brand new download)
Our old Jenkins instance stopped working when it would not load older plugins at all and we could in NO WAY make it go back to a functioning state. FINE. We needed to update anyways.
New Jenkins instance in a fresh (blank) JENKINS-HOME. Fresh plugin downloads ALL around.
Tried the LTS version (2.361) and ran into this problem. Updated to 2.377 to try and address it. did NOT work.
We have (unfortunately) literally thousands of old jobs (which we keep for SCM purposes) which depend on the Join trigger. This trigger HAS to work. I have loaded up the custom join trigger build by Mr. White and that did NOT address the issue either. Its not that the trigger does not work, it does not RUN. Log attached from /var/log/jenkins.log.
I DO have the parameterized trigger installed and we require that plugin as well.
I can provide a sample job if requested, but honestly, a blank job shows the same behavior.
The Join Trigger item IS in the list of Post Build Triggers.
This is 100% reproducible.
- is blocked by
JENKINS-64639 Join plugin has tables to div regression
- In Review
Thanks for the timely response. I will test with my management.
This would be my first experience with jenkins plugins, what are they properly written in?
Jenkins plugins are written in Java.
We have the "Improve a Plugin" tutorial for new contributors. It guides a new contributor through the first steps of modernizing a plugin. The join plugin is a good candidate for modernization.
We have the table to div migration guide that provides instructions for that transformation.
There is also a "Contributing to Open Source" google doc that includes more notes on other improvements that can be made to plugins.
The documentation for the plugin needs to be moved into the GitHub repository. That is part of the five part video series on modernizing a plugin.
In addition to those resources, the Jenkins developer mailing list and the Jenkins gitter chat channels provide helps for developers.
The join plugin has not been released in 6 years. It is not being actively maintained. Considering its importance to your organization, you may want to propose to the management at your company that you would like the company to dedicate some development time to maintain the join plugin.
Jobs that use the join plugin cannot save their configuration due to JENKINS-64639. The join plugin depends on HTML table tags for the layout of its forms. Jenkins 2.277.1 and later use HTML div tags instead of HTML table tags.
I'm not aware of anyone that can answer your questions about the failure in the join plugin. I'm aware of the join plugin because of its impact on other users during the migration from HTML table layout to HTML div layout.