Migrate CI build from CloudBees to OpenShift

[arun-gupta]

What does everybody think ?

Or use Travis ? Free offering ?

[aslakknutsen]

OpenShift is not a good choice atm. It's build around deploying to a gear, not as a genral purpose Jenkins

[aslakknutsen]

Why migrate anywhere?

[arun-gupta]

Got the following notice from CloudBees:

Dear CloudBees User:

You are receiving this mail because you are an admin or user of account arungupta.

This email provides details about how and when we are transitioning your existing free plan on CloudBees to a time-limited trial plan. As noted in an earlier mail to you, we are discontinuing our free plans on CloudBees as part of our focus on Jenkins and shut-down of our PaaS, RUN@cloud. For more information on our business and plan changes, please review our FAQ.

As an existing user of our free offering, we are transitioning you to a time-limited trial plan as of September 26, 2014. You will continue to have access to the same services under your free plan until the trial expires on October 13, 2014.

If you want to continue using CloudBees… please upgrade to a paid plan before October 13, 2014. The cheapest plan is our Starter plan at $60/month plus usage fees. You can do this by clicking the Upgrade Account button in the account settings dialog.

If you do nothing... your account will be deactivated on October 13, 2014. You will have no access to builds, applications, databases, or integrated partner services through CloudBees at that time. You don't need to cancel your account or take any action if you do not care about work you have hosted on CloudBees now.

If you need more time... please upgrade to a paid plan. You can pay on a credit card and cancel when needed.

If you are a developer in our FOSS program... then you should not have received this mail. Please contact us at help-run@cloudbees.com so we can fix our records and keep your builds running! If you want to be in our FOSS program, see the details on our web site.

Please contact us at help-run@cloudbees.com if you have questions or concerns.

We do not intend to send any follow-up notices regarding your account unless specifically required. We appreciate you trying out CloudBees and our free services, and we apologize for any problems the discontinuation of free plans causes. We hope CloudBees' offerings have been useful to you. We also hope we’ll see you again as a paid customer in the future!

[aslakknutsen]

well..

apply for the foss program;

If you are a developer in our FOSS program... then you should not have received this mail. Please contact us at help-run@cloudbees.com so we can fix our records and keep your builds running! If you want to be in our FOSS program, see the details on our web site.

[arun-gupta]

Ah, I didn't read the whole thing :-) Will follow up with them.

[radcortez]

Hi guys,

Yeah I agree we should apply to the FOSS program. I see no reason for not to work.

[johnament]

Hey

So I got the FOSS account setup. I started getting the build running, found a bunch of errors. Have some of them fixed locally.

The new URL will be https://javaee-support.ci.cloudbees.com/ for the jobs.

[arun-gupta]

Perfect, updated the link on https://github.com/javaee-samples/javaee7-samples.

So close this issue ?

[arun-gupta]

Guess we still need "Run on Cloudbees" logo somewhere ?

[johnament]

There's still a couple of issues floating around. For example, the env cloudbees gave me has very little disk space. I'm waiting to see if they can up it. If they cannot I'll see if I can trick arquillian to do the download app server once trick.

And yes, once we have everything up and running we need to add the logo to the site.

[arun-gupta]

Is Arquillian running in managed or remote mode?

[johnament]

WildFly == managed GlassFish == embedded.

[arun-gupta]

Can we change WildFly to be remote and start/stop the server before/after the tests ? This will ensure only a single instance of WildFly is downloaded and used.

Ditto for GlassFish

[johnament]

Yes, we're going to have to do something like that. The main problem is that a number of the tests are relying on custom configuration - which I can't find anywhere. Do you happen to know where the configuration is for the JASPIC tests?

[arjantijms]

Do you happen to know where the configuration is for the JASPIC tests?

It's in [wildfly-8.1.0.Final install]/standalone/configuration/standalone.xml

There it needs to be inserted into the security-domain tag, e.g.

 <subsystem xmlns="urn:jboss:domain:security:1.2">
        <security-domains>
            <security-domain name="other" cache-type="default">
                <authentication>
                    <login-module code="Remoting" flag="optional">
                        <module-option name="password-stacking" value="useFirstPass"/>
                    </login-module>
                    <login-module code="RealmDirect" flag="required">
                        <module-option name="password-stacking" value="useFirstPass"/>
                    </login-module>
                </authentication>
            </security-domain>
            <security-domain name="jboss-web-policy" cache-type="default">
                <authorization>
                    <policy-module code="Delegating" flag="required"/>
                </authorization>
            </security-domain>
            <security-domain name="jboss-ejb-policy" cache-type="default">
                <authorization>
                    <policy-module code="Delegating" flag="required"/>
                </authorization>
            </security-domain>
        </security-domains>
    </subsystem>

Needs to become:

 <subsystem xmlns="urn:jboss:domain:security:1.2">
        <security-domains>

            <!-- START DUMMY HACK FOR JASPIC -->
            <security-domain name="jaspitest" cache-type="default">
                <authentication-jaspi>
                    <login-module-stack name="dummy">
                        <login-module code="Dummy" flag="optional"/>
                    </login-module-stack>
                    <auth-module code="Dummy"/>
                </authentication-jaspi>
            </security-domain>
            <!-- END DUMMY HACK FOR JASPIC -->

            <security-domain name="other" cache-type="default">
                <authentication>
                    <login-module code="Remoting" flag="optional">
                        <module-option name="password-stacking" value="useFirstPass"/>
                    </login-module>
                    <login-module code="RealmDirect" flag="required">
                        <module-option name="password-stacking" value="useFirstPass"/>
                    </login-module>
                </authentication>
            </security-domain>
            <security-domain name="jboss-web-policy" cache-type="default">
                <authorization>
                    <policy-module code="Delegating" flag="required"/>
                </authorization>
            </security-domain>
            <security-domain name="jboss-ejb-policy" cache-type="default">
                <authorization>
                    <policy-module code="Delegating" flag="required"/>
                </authorization>
            </security-domain>
        </security-domains>
    </subsystem>

Note that the hack doesn't interfere with any of the other tests. It's a dummy domain that the test archive can refer to.

[johnament]

Still issues w/ JMS (HornetQ) on CloudBees (bees don't like hornets?) I'll just wait for a response from their support.

[radcortez]

@johnament I'm unable to access the jenkins service. It's currently hibernated, and I'm unable to wake it up. Not sure if this is a server problem or a permissions problem.

[arjantijms]

Since a while the project has been using Travis.