This options Defaults to false.
This ensure When a client pushes with git push –signed, this ensures that the push certificate is valid and signed with a valid public key stored in the refs/meta/gpg-keys branch of All-Users.
If true, server-side signed push validation is enabled.
Config in gerrit.config – receive.enableSignedPush
This saves you time and lets you incorporate your project into the Continuous Integration (CI) process.
API URL – If you server is github.com, your “API URL” would be “https://api.github.com” Otherwise if you use GitHub Enterprise, specify its API endpoint here (e.g., https://ghe.acme.com/api/v3/).
a) Check the GitHub project checkbox and set the Project URL to point to your GitHub Repository
c) Set the Jenkins hook URL as the URL for your Jenkins machine, and add /github-webhook/
Now you do the changes and commit , you will see jenkins build get trigger automatically. Don’t forget to do the settings in jenkins jobs to start the build when push code in github.
Reference
Computer hardware has traditionally been a scarce, expensive resource. In the early days of computing developers had to share a single machine. Today each developer usually has their own machine but it’s rare for a developer to have more than one. This means that running performance tests often involves scavenging for machines. Likewise, replicating even just part of a production environment is a major undertaking. With Amazon’s Elastic Compute Cloud (EC2), however, things are very different. A set of Linux servers is now just a web service call away. Depending on the type of the servers you simply pay 10-80 cents per server per hour for up to 20 servers! No more upfront costs or waiting for machines to be purchased and configured.
To make it easier for enterprise Java developers to use EC2, I have created EC2Deploy. It’s a Groovy framework for deploying an enterprise Java application on a set of Amazon EC2 servers. EC2Deploy provides a simple, easy to use API for launching a set of EC2 instances; configuring MySQL, Apache and one or more Tomcat servers; and deploying one or more web applications. In addition, it can also run JMeter and collect performance metrics.
Here is an example script that launches some EC2 instances; configures MySQL with one slave, Tomcat and Apache; deploys a single web application on the Tomcat server; and runs a JMeter test with first one thread and then two.
class ClusterTest extends GroovyTestCase {
void testSomething() {
AWSProperties awsProperties = new
AWSProperties("/…/aws.properties")
def ec2 = new EC2(awsProperties)
def explodedWar = '…/projecttrack/webapp/target/ptrack'
ClusterSpec clusterSpec =
new ClusterSpec()
.schema("ptrack", ["ptrack": "ptrack"],
["src/test/resources/testdml1.sql",
"src/test/resources/testdml2.sql"])
.slaves(1)
.tomcats(1)
.webApp(explodedWar, "ptrack")
.catalinaOptsBuilder({builder, databasePrivateDnsName ->
builder.arg("-Xmx500m")
builder.prop("com.sun.management.jmxremote")
builder.prop("com.sun.management.jmxremote.port", 8091)
builder.prop("com.sun.management.jmxremote.authenticate",
false)
builder.prop("com.sun.management.jmxremote.ssl", false)
builder.prop("ptrack.application.environment", "ec2")
builder.prop("log4j.configuration",
"log4j-minimal.properties")
builder.prop("jdbc.db.server", databasePrivateDnsName)})
SimpleCluster cluster = new SimpleCluster(ec2, clusterSpec)
cluster.loadTest("…/projecttrack/functionalTests/jmeter/SimpleTest.jmx",
[1, 2])
cluster.stop()
}
}
Let’s look at each of the pieces.
First, we need to configure the framework as follows:
AWSProperties awsProperties = new
AWSProperties("/…/aws.properties")
def ec2 = new EC2(awsProperties)
The aws.properties file contains various properties including the Amazon WS security credentials and the EC2 AMI (i.e. OS image) to launch. All servers use my EC2 appliance AMI that has Java, MySQL, Apache, Tomcat, Jmeter and some other useful tools pre-installed.
Next we need to configure the servers:
ClusterSpec clusterSpec =
new ClusterSpec()
.schema("ptrack", ["ptrack": "ptrack"],
["src/test/resources/testdml1.sql",
"src/test/resources/testdml2.sql"])
.slaves(1)
.tomcats(1)
.webApp(explodedWar, "ptrack")
.catalinaOptsBuilder({builder, databasePrivateDnsName ->
builder.arg("-Xmx500m")
builder.prop("com.sun.management.jmxremote")
builder.prop("com.sun.management.jmxremote.port", 8091)
builder.prop("com.sun.management.jmxremote.authenticate",
false)
builder.prop("com.sun.management.jmxremote.ssl", false)
builder.prop("ptrack.application.environment", "ec2")
builder.prop("log4j.configuration",
"log4j-minimal.properties")
builder.prop("jdbc.db.server", databasePrivateDnsName)})
SimpleCluster cluster = new SimpleCluster(ec2, clusterSpec)
This code first creates a ClusterSpec, which defines the configuration of the machines and the applications:
It then creates a cluster with that specification.
We then start the cluster:
cluster.start()
At this point EC2Deploy will:
Once the cluster is started we can run a JMeter load test:
cluster.loadTest("…/projecttrack/functionalTests/jmeter/SimpleTest.jmx", [1, 2])
The first argument specifies the test to run and the second argument is a list of JMeter thread counts. In this example, EC2deploy first runs the load test with one thread and then two threads. For each test run, it generates a report describing CPU utilization for each machine, average response time and throughput.
Finally, we stop the EC2 instances:
cluster.stop()
As you can see, EC2Deploy makes it pretty easy to deploy and test your enterprise Java application. I’ve used it to clone a production environment and run load tests. NOTE 1/28/08: The source code EC2Deploy along with a very cool Maven plugin is now available !