How do I deploy a grails application built on hudson to JbossAS 7? - grails

We have a grails application that we build using hudson. Hudson used to deploy the generated war to tomcat through the tomcat-manager. Now that we are moving to JBoss 7, there is no obvious step available in hudson to deploy to JBoss7. Is there are plugin for JBoss7 deployment that I can use? Or commands to perform deployments on JBoss7?

You should check this out:
https://docs.jboss.org/jbossas/7/plugins/maven/latest/
Also if you prefer to use scripting: https://github.com/maxandersen/as7scripting (it might be a little bit outdated now)
Regards

Related

How can you deploy a bitbucket-plugin (already built as jar) to the server via terminal?

We run a Bitbucket Server on version 7.21 and have recently developed a Plugin for it. Since this plugin finally reached a stable Version we wanted to integrate it into our cd/ci pipeline (bamboo).
We can build the plugin via bamboo build plan alright, but we are facing an issue when trying to deploy it.
atlas-sdk's "atlas-install-plugin" does not work for us (afaik) because we are not in the project space, but only have the built jar itself.
Is there any way to copy the jar to a specific location on the bitbucket server and it auto-deploys or something similar?
For anyone searching, I found the solution.
You can install plugins via the rest api: https://confluence.atlassian.com/confkb/installing-uninstalling-upgrading-and-downgrading-marketplace-apps-on-confluence-using-rest-api-1005343959.html

Continuous Integration with hybrid mobile app

I have a problem. I need to build a job in my Jenkins server hosted by macmini (localhost) to automatic build a deploy for my mobile hybrid apps. That's apps was building with ionic2, and need a deploy for Android (apk) and for iOS (ipa).
But when i run a build from Jenkins, with this shell command
I get this error
that's not all... because i try to execute, from the jenkins folder, the npm i and the result was this:
When i try to build my application from other "folder" and not from jenkins, they works correctly. How i can solve?
Without more information hard to say; you can either just script the things you do when you deploy "manually", or you might want to try a CLI tool like https://www.bitrise.io/cli or https://fastlane.tools which can auto-scan your project and configure a suitable configuration which is then easier to tweak.
In case of Bitrise CLI the base config can be generated with bitrise init in the repo root, and you can also use a visual editor to modify your configuration: https://discuss.bitrise.io/t/how-to-experiment-with-bitrise-configs-locally-on-your-mac-linux/1751
After a lot of time, just find the solution. Jenkins have a own "tools management". So i need to install, into jenkins, a property version of nodeJS, Npm and all other tools i need to deploy the application.
So, first of all you need to install property plugin (in my case nodejs).
After this, going into Jenkins Management System and configure a NodeJS version. That's all

Application starting issue websphere application server 8.5 after deployment Jenkins

I am using Jenkins websphere deployer plugin to deploy application to IBM WAS 8.5.5.
The ear deployment is successful but the start up is not successful though Jenkins shows success message.
I assume the ear (around 90MB) takes time for expansion in the remote server, and Jenkins success message is before the complete expansion. Is there a way to delay the process of startup after deployment is done.
Can anyone suggest?
You cannot work around this issue since it requires a modification to the websphere deployer plugin. There is a known synchronization issue for large EAR files. I believe there was a pull request that fixes this issue and was merged into the codebase for v1.3 of the plugin. This version is not yet released but can be viewed on github if you wish to compile and try it out for yourself.
You will need to use maven and to manual imports into your .m2 repository to compile and test this code in jenkins.
Reference: https://github.com/jenkinsci/websphere-deployer-plugin

JBoss Server and Grails 2.1.0 within STS

I've been working with a grails 1.3.7 project within STS for the last few months.
Our test and production environments use JBoss 5.1.
I upgraded our grails app to 2.1.0 recentlly and it all ran ok locally.
Major problems occured when I deployed it to our test environment (Jboss issues).
So in order to avoid this in future I would like to develop locally using JBoss also.
Is there a Eclipse/STS plugin I can use for this?
Thanks
Don't think there's a specific plugin for jboss
Seems your only options now are tomcat and jetty, if you need to stick with the 'run-app' command
If you can give up the debug console and check your test info at the browser, then you can probably write a small script to auto-deploy to a local jboss server, which you can set up through eclipse workspace

Effective grails plugin development

This has been very upsetting for me up till now. Here is what I am trying to do:
IDE I'm using is Intellij IDEA.
Building a grails application.
Grails application specifies two dependencies on in house grails plugins also being developed in IntelliJ as separate grails plugin projects.
Now to make any changes to plugins, I update the source code in plugin projects and use mavan-install (Maven Publisher plugin) to deploy to local Maven repository.
I have to uninstall the plugin in core grails project. Delete the plugin cache from ivy and then run the core grails project which gets the latest copy of plugin from local maven repository.
What's the effective and ideal way to achieve this? A single change makes me do some 5 minutes of labour work to even test and run core application.
Any recommendations/ best practices?
Use inline plugins for this - see section "Specifying Plugin Locations" in http://grails.org/doc/latest/guide/12.%20Plug-ins.html#12.1%20Creating%20and%20Installing%20Plug-ins
By specifying the plugin project directory with grails.plugin.location.<plugin-name> as the location of the installed plugin, you can edit the real files and the changes will affect the test application, and there's no need to sync anything up.

Resources