For a project we need to the wsdl files to be published in the artifacts folder.
For continuous integration we use TeamCity.
The project type is a Windows Communication Service Project.
Is it possible to have a buildstep that will generate the wsdl files from a webservice project?
Yes you can do that just from the project. Use a nant script or similar that can execute command line for you. Have the script execute the tool against your project, you can use CmdHelper for example. http://www.stephan-brenner.com/?page_id=82
Related
I have created a test script jmx from Jmeter and I'm able to execute it in GUI mode and in non-GUI mode,
but it needs always jmeter application as prerequisite in order to invoke the jmx script as input to jmeter application.
Now I would build the jmx script in an executable file to launch it from cli and free from jmeter application.
Is there a way to build the jmx script (and eventually qith essential jmeter jars) in only one executable file ?
For example I have created the test.jmx.
It prerequisites jmeter and it can executed as /jmeter -n -t test.jmx
I would build it as or test.exe
and run it as test.exe
Is it possible ?
If you really need an ".exe" take a look at Launch4j project
If you just want to have the way of running a .jmx script without having to install JMeter first you can consider the following alternative options:
JMeter Maven Plugin (possibly connected with Maven Wrapper so you won't have to install Maven)
Taurus tool which can automatically download and install JMeter
thanks #Dmitri for you answers and links which has triggered the solution to the question
Other important links applied to build jmeter project with maven are been:
https://sarkershantonu.github.io/2020/09/04/maven-jmeter-reporting/
and
https://github.com/jmeter-maven-plugin/jmeter-maven-plugin/wiki/Adding-Excluding-libraries-to-from-the-classpath
I'm trying to automate my build process with TeamCity. Some tutorials tell me I need to set up a .build script to do stuff, but it looks like TeamCity can already do all that stuff. Can't I just call MsBuild and pass in the target solution/project and specify a configuration name and publish profile name? What's so special about a .build file?
TeamCity uses what they call "Runners." There are a dozen already configured, one of which is the Visual Studio runner, and that will allow you to build a Visual Studio solution. The difference between a build file and TeamCity runners is that you have to configure the runners through the interface (or the API) while a complicated build you can craft through a single build script. It's a matter of preference.
I have created a test framework for testing .jsp files and .tag files using embedded jetty. I'm starting Jetty server programmatically using Java API, adding servlet holder and wrapper test JSP and initializing the server passing the project's web root.
There were some issues with Jasper discovering TLD locations during runtime when run from maven surefire plugin. I fixed it by providing
<useManifestOnlyJar>false</useManifestOnlyJar>
plugin classpath settings. Everything works good when I run tests using mvn clean install now.
Running tests from eclipse context menu has one issue. If there is any other project in workspace in the multi module maven build, TLD's in that project are not resolved. One workaround I tried was to 'close' the project in eclipse workspace and it worked out.
However I would want it to work with all the projects open in workspace and running from the eclipse JUnit context menu. The problem is in the jasper TldScanner that looks for tld files in jar and WEB-INF of current project only.
TldScanner.scanTlds()
processWebDotXml();
scanJars();
processTldsInFileSystem("/WEB-INF/");
I'm using org.glassfish.web.jsp-impl 2.2.2-b06 version with Jetty-8.1.0-RC5.
Is there a way to specify file based TLD scanning for jasper for extra classpath items?
I have been trying to get Gradle working on our Continuous Integration server, which has no access to internet (external) URLs.
Currently, we get our maven-style dependencies from an internal proxy server. So I uploaded the gradle wrapper onto that server too, such that when the CI server starts up it can download the wrapper from the internal maven proxy server.
Problem solved, I thought; the build will carry on and pull down the project dependencies from the internal proxy server as well (it's set up in the build script) and should be OK now.
But in between getting the wrapper Zip file and starting the build, it's doing the following:
Downloading http://maven.internal.mycompany.com:8081/nexus/content/repositories/thirdparty/org/gradle/gradle/1.0-milestone-3/gradle-1.0-milestone-3-bin.zip ................
Unzipping /home/user/.gradle/wrapper/dists/gradle-1.0-milestone-3-bin.zip to /home/user/.gradle/wrapper/dists
Set executable permissions for: /home/user/.gradle/wrapper/dists/gradle-1.0-milestone-3/bin/gradle
Download http://repo1.maven.org/maven2/org/codehaus/groovy/groovy/1.7.3/groovy-1.7.3.pom
Download http://repo1.maven.org/maven2/antlr/antlr/2.7.7/antlr-2.7.7.pom
etc...
*** then the actual build starts ***
Download http://maven.internal.mycompany.com:8081/nexus/content/groups/public/commons-lang/commons-lang/2.6/commons-lang-2.6.jar
E.g. it's trying to pull down extra dependencies for the gradle executable from repo1.maven.org which fails on the continous integration server, as it has no access to this server.
In my build.gradle file I have:
repositories {
mavenRepo urls: "http://maven.internal.mycompany.com:8081/nexus/content/groups/public"
}
and in my ./gradle/wrapper/gradle-wrapper.properties file I have :
distributionUrl=http\://maven.internal.mycompany.com:8081/nexus/content/repositories/thirdparty/org/gradle/gradle/1.0-milestone-3/gradle-1.0-milestone-3-bin.zip
So is there another place I can specify which server the wrapper should use to get it's additional dependencies ? Or is this hard-coded into the wrapper itself ? Or I might be missing a trick here, as Google doesn't seem to show up anyone else having this issue at all !
Ben
Picked up a hint from another forum that led me to the answer - a plugin for cobertura that I was pulling down had it's own gradle build file that included the default maven repositories.
I've removed that now, and the calls to external maven have ceased.
How does one deploy scala or scalatra onto Jetty servlet container? Does anyone have experience or can point me to some resources online?
If you're using sbt, run the package command from within the sbt shell. This will create you a war file in the target dir. You can drop that into jetty's webapps directory and configure a context xml file in its contexts directory.
If you're using maven, I believe the command you want is mvn package.
Are you using Simple Build Tool (SBT) for your project? If you do, it's as easy as running "sbt jetty"
Check it out: http://code.google.com/p/simple-build-tool/