All,
I am trying to test my grails app using Hudson. I have in grails I will run the command of test-app -unit and will recieve the following message:
Running script /home/test/grails-1.1.1/scripts/TestApp.groovy
Environment set to test
Plugin [hibernate-1.1.1] not
installed, resolving..
Reading remote plugin list ...
Error reading remote plugin list
[Connection timed out], building
locally...
Unable to list plugins, please check
you have a valid internet connection:
Connection timed out
Reading remote plugin list ... Error
reading remote plugin list [Connection
timed out], building locally...
Unable to list plugins, please check
you have a valid internet connection:
Connection timed out
Plugin 'hibernate' was not found in
repository. If it is not stored in a
configured repository you will need to
install it manually. Type 'grails
list-plugins' to find out what plugins
are available. Finished: FAILURE
I believe the reason for this is that I do not have access to an external network on the server. If I do a list-plugins there is no returns it just times out.
I also beleive that this is a grails issue not a hudson issue.
The answer is the following:
navigate to the /path/to/hudson/Jobs/JOBNAME/
run - grails install-plugin /location/to/grails-1.1.1/plugins/grails-hibernate-1.1.1.zip
This will install the hibernate plugin for the specific job. This workaround can also be used for other plugins needed.
This has been tested in hudson.
Grails is going to need the Internet somehow to get plugin information. What you might be able to do is get Grails installed on a machine that does have access, get all of the plugins you need (i.e. by running what Hudson would normally run, test-app or whatever), and then copy over the entire grails installation to $GRAILS_HOME on your Hudson machine.
I can't say I've ever tried this, but it seems like it should work.
Related
Reservation: I am not sure if this is a bug or a work limitation of the annotation #QuarkusTest. This is our first big project on this framework, so please do not judge strictly.
My team and I write a project using Kotlin, Quarkus as the main framework, Gradle as the build system and Smallrye GraphQL. We have an application that is covered with tests. The problem arises when we write integration HTTP tests for our EndPoints. The tests work out correctly, but only when we run them having the application started manually before. If we do not start the application using ./gradlew web:quarkusDev and put the #QuarkusTest annotation, which, according to the documentation, should run the application without any additional commands before running the tests, an exception occurs:
"Connection refused: no further information
java.net.ConnectException: Connection refused: no further information"
It seems like the application does not start at all.
This is the link to our small test project on github, which reproduces the problem.
We understand that requests should be sent to http://localhost:8081/mapins but it does not work. We get such response: "GraphQL Schema not generated. Make sure you have a GraphQL Endpoint. Go to https://quarkus.io/guides/microprofile-graphql to learn how". When we exclude the path from requests for autoconfiguration we get the same result as in the case when we send requests to http://localhost:8081/ - responses are just empty. We have already tried using quarkus.http.test-port but results are the same...
We searched for information about this problem, but the only thing we found was a bit similar question on StackOverflow, where the solution was - to connect "io.quarkus:quarkus-resteasy-reactive-jackson". We tried this option, but it did not help.
Maybe the problem is that our application is multimodule and needs to be started from concrete module and #QuarkusTest uses some kind of default command? ./gradlew web:quarkusDev has to be called for appropriate startup and maybe quarkus uses some other command during autoconfiguration. Is it possible to set starting command for tests manually?
Output of java -version:
Java 17, Kotlin 1.6.21
Quarkus version:
2.11.1.Final
Build tool (output of gradlew --version):
Gradle 7.4.2
My JMeter 3.0 installation was working fine and then I installed Selenium webdriver.
I copied the files and folders as mentioned in the installation steps given here.
I get the following error:
Writing log file to: C:\WINDOWS\system32\jmeter.log
An error occurred: Implementing class
errorlevel=1
Press any key to continue . . .
If I remove the selenium installation it works as expected.
Can someone help me with what might have gone wrong?
Thanks
The guide you're using is quite outdated, currently recommended way of installing JMeter Plugins is using JMeter Plugins Manager, so:
Install "clean" version of JMeter 3.0
Install JMeter Plugins Manager
From JMeter main menu choose
Options -> Plugins Manager -> Available Plugins -> Selenium/WebDriver Support
Click `Apply Changes and Restart JMeter
Plugins Manager is smart enough to detect and resolve libraries conflicts, moreover it is the handy way of managing the plugins and keeping them up-to-date.
We upgraded our AIX Environment from WL 6.1.0 to 6.1.0.1 without stopping the WL Server (ApplicationCenter is not installed in this WAS Profile). We have WAS 8 in Netowrk Deployment Configuration.
Installation Manager installed it successfully, then we reboot the server and we got this trying accessing the console:
Error 500: javax.servlet.ServletException: Worklight Console
initialization failed.Logged Exception:
com.worklight.server.database.api.WorklightDataSourceException:
FWLSE0194E: Worklight server cannot be started because of failure
while getting a connection from data-source bound to resource
reference: jdbc/WorklightDS. Make sure the database is up, the
credentials are correct and the driver is available for the server.
[project buytec_worklight]
I searched the right way to upgrade and I saw that we should have stopped the server than we should follow this procedure:
http://pic.dhe.ibm.com/infocenter/wrklight/v6r1m0/index.jsp?topic=%2Fcom.ibm.worklight.upgrade.doc%2Fdevenv%2Fc_upgrade_to_srvr610_upgrading_wl_console_upgrade_console.html
But at first, with WL 6.1.0 we didn't use the ant-task to deploy the console, we just put the .war found in the Eclipse Studio with the right plugin, so now i cannot manage to understand how to upgrade the console manually.
Have you any suggestions?
I don't know what you mean by "upgrade the console manually". The Worklight Console is part of the .war file you deploy to the application server, but the console doesn't have anything to do with the connection to the database.
If you want to "upgrade the console", you actually mean that you want to update the .war file, so deploy a .war file that was generated using Worklight Studio 6.1.0.1.
You can also follow the manual upgrade instructions for 6.1.0.1: http://pic.dhe.ibm.com/infocenter/wrklight/v6r1m0/topic/com.ibm.worklight.upgrade.doc/devenv/c_upgrade_to_srvr610_addl_info_manual_app_srvr_upgrade.html
Because you didn't properly start the upgrade process, I suggest that you will take the time to review all upgrade topics, from the start: http://pic.dhe.ibm.com/infocenter/wrklight/v6r1m0/topic/com.ibm.worklight.upgrade.doc/devenv/c_upgrade_to_srvr610_in_production_env.html
In addition, it doesn't matter how you first installed 6.1.0.0, you can still use either Ant or manual upgrading.
I simply re-add the .jar files driver for db2, checking that they are resolved, set again the Data sources JDBC, uploaded a new console.war created with eclipse and it worked!
We have a Live mule server (Community edition ) 3.3.0 running on a Windows 2008 server.
We have several apps running on it.
We tried to hotdeploy a new app in it. It failed saying some port was already in use/bind - this was a JMX port. However we were unable to undeploy it. It didn't create any anchor file as it had failed deployment so we couldn't do the clean undeploy. When we tried to delete the exploded folder it didn't allow as it said the jars in the lib were in use.
We tried to re-deploy the same file with fix again but it had no effect.
Question is irrespective of what caused out application to fail - how can one undeploy or take out a Mule app (failed) completely? It doesn't have anchor file and trying to delete says jar in use. Only way we could do was to stop mule and then delete the folder and restart Mule - totally unacceptable in production environment.
Any clues?
This is a known bug on 3.3.0 that was fixed on 3.3.1.
I'm trying to reconfigure our TeamCity build server (running on WIN 2008) and switch from SVN to Mercurial repository.
I use the following link as Configuring Mercurial (Hg) with TeamCity over SSH at RepositoryHosting.
I spent several days and still can't get it work.
I can reach the Mercurial repository from TeamCity (via Test Connect) and I can pull code from Mercurial via TrotoiseHG, but the build fails every time because TeamCity cannot pull source code from the server.
Does anybody had the same issue?
Have you tried using Agent-Side checkout instead of the default? Otherwise, TeamCity tries to "intelligently" detect changes and distribute them to build nodes. Failure can occur whenever something happens in the VCS that TeamCity doesn't understand how to replicate, such as using subrepos.