Eclipse Community Forums: Hudson » Hudson 3.3.0 Release Candidate is available for Testing

Home » Archived » Hudson » Hudson 3.3.0 Release Candidate is available for Testing(New Release)

Hudson 3.3.0 Release Candidate is available for Testing [message #1698117]

Thu, 11 June 2015 08:18

Eclipse User

We're glad to announce that the release candidate for Hudson 3.3.0 is now available for community testing from the downloads page.
This is an important release as it marks a move to only supporting Java 7 and above for the running of Hudson Core. You will still be able to run jobs that compile to older versions of Java, but you must use Java 7 or 8 to run your server and slaves.
We have tested this version with both Java 7 and Java 8 and the following Application Servers:

Jetty 9 (Built in)
JBoss 8.2
Glassfish 4.1
Tomcat 7
Tomcat 8

When testing this version of the core you should be able to upgrade from any release from 2.2.n upwards (be sure to do your backups first!) .
Because of the change in compilation version of Java and other library changes we have a separate plugin server for this release which 3.3.0 will automatically use. Be sure to upgrade your plugins as well.
You can see the full list of bugs addressed in this release in the changelog, but as usual, please report any problems you encounter in your testing via bugzilla.

All being well the production version of this release is scheduled for the 10th July.
Happy testing!

Re: Hudson 3.3.0 Release Candidate is available for Testing [message #1698301 is a reply to message #1698117]

Fri, 12 June 2015 23:43

Eclipse User

I get this exception if I enable my Google Login Plugin.

javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: vfs:/content/hudson.war/WEB-INF/lib/hudson-core-3.3.0-RC1.jar/hudson/security/SecurityRealm/loginDialog.jelly:72:69: <st:include> No page found 'loginFragment.jelly' for class org.vx68k.hudson.plugin.google.login.GoogleLoginService

This is probably caused by these lines in hudson.security.SecurityRealm/loginDialog.jelly.

        <j:forEach var="fls" items="${app.getFederatedLoginServices()}">
            <div>
                <st:include page="loginFragment.jelly" it="${fls}"/>
            </div>
        </j:forEach>

Re: Hudson 3.3.0 Release Candidate is available for Testing [message #1698307 is a reply to message #1698301]

Sat, 13 June 2015 01:25

Eclipse User

Strangely, the same errors started to occur even on 3.2.2, though it had worked before. Where is loginFragment.jelly?

Re: Hudson 3.3.0 Release Candidate is available for Testing [message #1698309 is a reply to message #1698307]

Sat, 13 June 2015 02:11

Eclipse User

Sorry, it was caused by my plugin configuration. I will recheck the problem soon.

Re: Hudson 3.3.0 Release Candidate is available for Testing [message #1698310 is a reply to message #1698309]

Sat, 13 June 2015 02:32

Eclipse User

I confirmed the problem was caused by my mistake.

I wanted to include a non-default resource into the plugin archive by adding a resources element in pom.xml but it totally overrode the default resources. That is why loginFragment.jelly was not found.

Previous Topic:	Old Hudson cannot checkout from Cloudforge - what is the simplest way to fix?
Next Topic:	Internal Server Error with the Google Login Plugin on Hudson 3.3.0-RC1

Goto Forum:

-=] Back to Top [=-

Current Time: Wed Jul 23 16:44:12 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter