I'm trying to get Play 2.1.3 working on a Jenkins server (in TeamForge). I got my dependencies loaded into our local Artifactory because there's no internet for resolving dependencies. When I try to startup Play, it hangs forever trying to resolve scala-sbt
+ /opt/collabnet/PLAY/play-2.1.3/play
Getting org.scala-sbt sbt 0.12.4 ...
I don't understand how to configure Play for the initial bootstrap, and I suspect it isn't getting a chance to read my plugins.sbt or Build.scala files where I specified the location of the Artifactory repository. Do I need to do something with sbt.boot.properties or play.boot.properties? How can I get scala-sbt loaded without an internet?
Related
I downloaded the jar file from https://github.com/jenkinsci/plugin-installation-manager-tool as specified in the docs. We are behind a corporate proxy, so tried both with and without the proxy the following command ..
java -jar jenkins-plugin-manager-*.jar --war C:\PathToJenkins\Jenkins\jenkins.war --available-updates --plugin-file C:\PathToJenkins\Jenkins\plugins.txt
kept running into "Error getting update center json"
Has anyone faced similar issue ? Am I doing anything wrong ?
My Server is running behind a proxy.
I have deployed jenkins a tried to install my required plugins but got connection error:
Failed to download from https://updates.jenkins.io/download/plugins/echarts-api/5.3.0-2/echarts-api.hpi
(redirected to: https://ftp.belnet.be/mirror/jenkins/plugins/echarts-api/5.3.0-2/echarts-api.hpi)
I have checked and found that I my proxy allow me connecting to another mirror (ftp.halifax.rwth-aachen.de)
I have downloaded the default config uplaod-center.json, edit it by replacing updates.jenkins.io with ftp.halifax.rwth-aachen.de and configured my file in the Update Site screen.
I have restared jenkins but I'm still getting the same connection issue to updates.jenkins.io.
Am I missing any thing here?
I created an ASP.Net project (.net 4.7.1), it's basically the default temple project without any change at all!
I created a build to publish it to an Azure WebApp- result : works just fine.
then I cloned the build and this time I target a virtual directory (I built the virtual directory from the portal and ticked it as an application)
surprisingly, although it has published successfully ( I doubled check from console), but when I browse it , it doesn't work and I get te below error:
HTTP Error 502.5 - Process Failure Common causes of this issue: The
application process failed to start The application process started
but then stopped The application process started but failed to listen
on the configured port Troubleshooting steps: Check the system event
log for error messages Enable logging the application process' stdout
messages Attach a debugger to the application process and inspect
it doesn't make sense to me, so I tried with different project type and .net version but the result is the same!
I found a workaround if I deploy pure HTML file (without asp.net) in the root, then the virtual directories will start working.
it looks like it's related to the fact that web.config of the virtual directory inserts something from the config of the root.
For my Selenium/Cucumber/Maven project I downloaded the latest version of the Chrome and IE driver via Webdrivermanager on an virtual machine with an internet connection. After this I used the same project (using the same Maven local repo folder) on a Windows server without an internet connection, set an override for the local Maven repo folder in IntelliJ and added the forceCache option:
ChromeDriverManager.getInstance().forceCache().setup();
driver = new ChromeDriver();
Version of webdrivermanager = 1.7.2
When executing a test via the command line of Windows with Maven command mvn test clean, I receive below connection error. The browser driver is available in the local repo.
INFO BrowserManager - Reading https://chromedriver.storage.googleapis.com/
to seek [chromedriver]
[main] INFO BrowserManager - Reading
https://chromedriver.storage.googleapis.com/ to seek [chromedriver]
[main] WARN BrowserManager - [1/3] Exception reading
https://chromedriver.storage.googleapis.com/ to seek [chromedriver]:
org.apache.http.conn.HttpHostConnectException Connect to
chromedriver.storage.googleapis.com:443
[chromedriver.storage.googleapis.com/216.58.212.208] failed: Connection
timed out: connect
UPDATE: I have executed my test again via the virtual machine with an internet connection. It looks like that Maven is still using the default .m2 folder, which doesn't contain the cached browser drivers and webdrivermanager tries to download the files. So this is not an webdrivermanager issue, but a Maven issue. Has anyone suggestions to fix this issue? I have already restarted my machine, but with no luck.
The cache used by WebDriverManager in a Windows machine is located at C:\Users\your-user\.m2\repository. Concretely, for chromedriver, the binary should be at C:\Users\your-user\.m2\repository\webdriver\chromedriver\win32\2.33\chromedriver.exe. Check this file actually exists, since this is what the forceCache() method is going to look for. I have doubled checked again and this feature is still working as expected. In your case, it seems that the cache file is not available, and therefore WebDriverManager tries to download it.
I tried to deploy a Play app to Cloudbees (only via push to git repo from which it is built by jenkins), it compiled and should work but I get a "502 Bad Gateway" error when loading the app. There is no error shown in the console only that it answers "502 Bad Gateway" when trying to access it. But that's what I see in the browser, too.
Cloudbees say that there is no other manipulation necessary, just cloning/pulling the ClickStart-Project, making it you application and pushing it back. The Play project works fine locally.
I am very grateful for any help. Please let me know if I need to provide any other information. Thanks a lot!
Edit: It works fine with Heroku only adding a Procfile. I don't get the problem with Cloudbees...
In this case the error is due to the database needing evolutions to be run before it can start:
[warn] play - Run with -DapplyEvolutions.default=true and -DapplyDownEvolutions.default=true if you want to run them automatically (be careful)
Oops, cannot start the server.
#6eg39l651: Database 'default' needs evolution!
You can see the error in your application console:
https://run.cloudbees.com/a/strehlst#app-manage/logs:strehlst/odzh
or via bees app:tail if you have the bees CLI installed.
You can also deploy direct from your desktop if you like:
play dist
bees app:deploy -t play2 dist/yourapp.zip
And it will push direct to your app (if you don't want a continuous deployment pipeline).