# df -k
Filesystem                    1K-blocks    Used Available Use% Mounted on
devtmpfs                         498132       0    498132   0% /dev
tmpfs                            508060       0    508060   0% /dev/shm
tmpfs                            508060     772    507288   1% /run
/dev/mapper/vg_fedora-lv_root   7641992 6590912    656228  91% /
tmpfs                            508060       0    508060   0% /sys/fs/cgroup
tmpfs                            508060       0    508060   0% /media
/dev/sda1                        487652   84379    377673  19% /boot

# fdisk -l
 
Disk /dev/sda: 10.7 GB, 10737418240 bytes
255 heads, 63 sectors/track, 1305 cylinders, total 20971520 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000e3a8c
 
   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *        2048     1026047      512000   83  Linux
/dev/sda2         1026048    20971519     9972736   8e  Linux LVM
 
 
Disk /dev/mapper/vg_fedora-lv_swap: 2113 MB, 2113929216 bytes
255 heads, 63 sectors/track, 257 cylinders, total 4128768 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
 
 
Disk /dev/mapper/vg_fedora-lv_root: 8086 MB, 8086618112 bytes
255 heads, 63 sectors/track, 983 cylinders, total 15794176 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/sdb: 21.5 GB, 21474836480 bytes
255 heads, 63 sectors/track, 2610 cylinders, total 41943040 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Command (m for help): n
Partition type:
   p   primary (0 primary, 0 extended, 4 free)
   e   extended
Select (default p):
Using default response p
Partition number (1-4, default 1):
Using default value 1
First sector (2048-41943039, default 2048):
Using default value 2048
Last sector, +sectors or +size{K,M,G} (2048-41943039, default 41943039):
Using default value 41943039
Partition 1 of type Linux and of size 20 GiB is set
 
Command (m for help): v
Remaining 2047 unallocated 512-byte sectors
 
Command (m for help): w
The partition table has been altered!

pvcreate /dev/sdb1
vgextend vg_fedora /dev/sdb1
lvextend -l +100%FREE /dev/mapper/vg_fedora-lv_root
resize2fs /dev/mapper/vg_fedora-lv_root

#!/bin/sh
 
WWW_MYSQL_DIR='/var/www/answers/answers_mysql'
WWW_PGSQL_DIR='/var/www/answers/answers_postgres'
DB_NAME='answers'
 
rm -Rf $WWW_PGSQL_DIR/*
unzip -o prj.zip -d $WWW_PGSQL_DIR
mv $WWW_PGSQL_DIR/config/Settings.class.php.pgsql $WWW_PGSQL_DIR/config/Settings.class.php
chmod -R 777 $WWW_PGSQL_DIR
psql -U postgres -f $WWW_PGSQL_DIR/install/crt-pgsql.sql
psql -U postgres -f $WWW_PGSQL_DIR/install/postgres.sql $DB_NAME
 
rm -Rf $WWW_MYSQL_DIR/*
unzip -o prj.zip -d $WWW_MYSQL_DIR
mv $WWW_MYSQL_DIR/config/Settings.class.php.mysql $WWW_MYSQL_DIR/config/Settings.class.php
chmod -R 777 $WWW_MYSQL_DIR
mysql -v -u root  < $WWW_MYSQL_DIR/install/crt-mysql.sql
mysql -v -u root  < $WWW_MYSQL_DIR/install/mysql.sql $DB_NAME

<?xml version="1.0" encoding="UTF-8"?>
<project name="${env.JOB_NAME}" default="build" basedir=".">
  <property environment="env"/>
  <property name="tests" value="${env.WORKSPACE}/tests"/>
  <property name="ci" value="${env.WORKSPACE}/ci"/>
  <property name="code" value="${env.WORKSPACE}/code"/>
 
 
  <target name="make_settings">
      <exec executable="sed" output="${code}/config/Settings.class.php.mysql">
        <arg 
            line="-f ${ci}/deployment/config/mysql/settings-mysql.sed ${code}/config/Settings.class.template.php"
        />
      </exec>
      <exec executable="sed" output="${code}/config/Settings.class.php.pgsql">
        <arg 
            line="-f ${ci}/deployment/config/pgsql/settings-pgsql.sed ${code}/config/Settings.class.template.php"
        />
      </exec>
    </target>
 
  <target name="make_sql">
    <exec executable="sed" output="${code}/install/mysql.sql">
      <arg 
           line="-f ${ci}/deployment/config/mysql/install-mysql.sed ${code}/install/mysql.sql"
      />
    </exec>
    <exec executable="sed" output="${code}/install/postgres.sql">
      <arg
          line="-f ${ci}/deployment/config/pgsql/install-pgsql.sed ${code}/install/postgres.sql" 
      />
    </exec>
  </target>
 
  <target name="move_files" depends="make_settings,make_sql">
    <!-- Move authentication files to WAUT root -->
    <move file="${ci}/deployment/misc/login.php" tofile="${code}/login.php" />
    <move file="${ci}/deployment/misc/logout.php" tofile="${code}/logout.php" />
 
    <!-- Move MySQL db creation files to install folder -->
    <move
         file="${ci}/deployment/config/mysql/crt-mysql.sql"
         tofile="${code}/install/crt-mysql.sql"
    />
 
    <!-- Move PGSQL db creation files to install folder -->
    <move 
         file="${ci}/deployment/config/pgsql/crt-pgsql.sql" 
         tofile="${code}/install/crt-pgsql.sql" 
    />
 
    <!-- Move publish script to the workspace root, so it will be beside prj.zip -->
    <move 
         file="${ci}/deployment/publish-over-ssh/publish.sh"
         tofile="${env.WORKSPACE}/publish.sh"
    /> 
  </target>
 
  <target name="save_commit_info" depends="move_files">
      <!-- Temp fix for SVN client and SVN plugin incompatibility -->
      <exec dir="${env.WORKSPACE}" executable="svn" >
          <arg 
              line="--username jenkins --password 123456 upgrade"
          />
      </exec>
      <exec dir="${env.WORKSPACE}" executable="svn"  output="${env.WORKSPACE}/version.txt">  
          <arg line="--username jenkins --password 123456 log -r ${env.SVN_REVISION}" />
      </exec>
      <exec dir="${env.WORKSPACE}" executable="svn">  
          <arg line="--username jenkins --password 123456 log -r ${env.SVN_REVISION}" />
      </exec>          
  </target>	
 
  <target name="svn" depends="save_commit_info">
      <java
           dir="."
           jar="${ci}/deployment/scm-decorator.jar"
           fork="true"
           failonerror="true"
      >
 
          <arg value="svn"/>
          <arg value="${env.WORKSPACE}/version.txt"/> 
      </java>    	
  </target>
 
  <target name="zip" depends="svn" description="Compress project files">
      <jar destfile="${env.WORKSPACE}/prj.zip"
            basedir="${env.WORKSPACE}/code"
            excludes=".svn" />
  </target>
 
  <target name="build" depends="zip" />
</project>

<copy file="${resources}/config-mysql.xml" tofile="${output}/config.xml"/>

<properties>
    <entry key="suite-title">Answers Test Suite</entry>
    <entry key="tests-disabled">
        com.deepshiftlabs.testui.AnswersStartyCo. TestLogin,
        com.deepshiftlabs.testui.AnswersStartyCo.TestAddRemoveQuestionByAnonymous,
        com.deepshiftlabs.testui.AnswersStartyCo.TestAddRemoveQuestionByUser,
        com.deepshiftlabs.testui.AnswersStartyCo.TestSearch,
        com.deepshiftlabs.testui.AnswersStartyCo.TestReply,
        com.deepshiftlabs.testui.AnswersStartyCo.TestFilterSort,
        com.deepshiftlabs.testui.AnswersStartyCo.TestTags,
        com.deepshiftlabs.testui.AnswersStartyCo.TestSmoke,
    </entry>
 
    <entry key="website">http://answers.dslabs.lan/mysql</entry>

Started by an SCM change
Building in workspace /var/lib/jenkins/jobs/Answers/workspace
Cleaning local Directory .
Checking out http://192.168.3.97/repos/answers/trunk at revision 146
A         tests
----------- SOME LINES REMOVED ---------------------------------
A         ci/toolchain/build-toolchain.xml
At revision 146
[deployment] $ ant -file build.xml build
Buildfile: build.xml
 
make_settings:
 
make_sql:
 
move_files:
     [move] Moving 1 file to /var/lib/jenkins/jobs/Answers/workspace/code
     [move] Moving 1 file to /var/lib/jenkins/jobs/Answers/workspace/code
     [move] Moving 1 file to /var/lib/jenkins/jobs/Answers/workspace/code/install
     [move] Moving 1 file to /var/lib/jenkins/jobs/Answers/workspace/code/install
     [move] Moving 1 file to /var/lib/jenkins/jobs/Answers/workspace
 
save_commit_info:
     [exec] Upgraded '.'
----------- SOME LINES REMOVED ---------------------------------
     [exec] Upgraded 'ci/deployment/misc'
     [exec] Upgraded 'ci/toolchain'
     [exec] ------------------------------------------------------------------------
     [exec] r146 | igork | 2012-11-14 08:22:44 +0000 (Wed, 14 Nov 2012) | 1 line
     [exec] 
     [exec] "Fixed" robots.txt to initiate Jenkins build
     [exec] ------------------------------------------------------------------------
 
svn:
 
zip:
      [jar] Building jar: /var/lib/jenkins/jobs/Answers/workspace/prj.zip
 
build:
 
BUILD SUCCESSFUL
Total time: 0 seconds
SSH: Connecting from host [phpbb.deepshiftlabs.com]
SSH: Connecting with configuration [Answers test server] ...
SSH: EXEC: STDOUT/STDERR from command [chmod +x publish.sh
./publish.sh] ...
Archive:  prj.zip
   creating: /var/www/answers/answers_postgres/META-INF/
  inflating: /var/www/answers/answers_postgres/META-INF/MANIFEST.MF  
   creating: /var/www/answers/answers_postgres/config/
   creating: /var/www/answers/answers_postgres/include/
----------- SOME LINES REMOVED ---------------------------------
   creating: /var/www/answers/answers_postgres/utils/
  inflating: /var/www/answers/answers_postgres/ask.php  
----------- SOME LINES REMOVED ---------------------------------
  inflating: /var/www/answers/answers_postgres/utils/DBUtils.class.php  
  inflating: /var/www/answers/answers_postgres/utils/Utils.class.php  
  inflating: /var/www/answers/answers_postgres/utils/init.php  
DROP DATABASE
CREATE DATABASE
REVOKE
DROP ROLE
You are now connected to database "answers".
psql:/var/www/answers/answers_postgres/install/crt-pgsql.sql:7: NOTICE:  table "USERS_SOURCE_TABLE" does not exist, skipping
DROP TABLE
psql:/var/www/answers/answers_postgres/install/crt-pgsql.sql:17: NOTICE:  CREATE TABLE / PRIMARY KEY will create implicit index "users_source_table_pkey" for table "users_source_table"
CREATE TABLE
INSERT 0 1
INSERT 0 1
----------- SOME LINES REMOVED ---------------------------------
GRANT
Archive:  prj.zip
   creating: /var/www/answers/answers_mysql/META-INF/
  inflating: /var/www/answers/answers_mysql/META-INF/MANIFEST.MF  
   creating: /var/www/answers/answers_mysql/config/
   creating: /var/www/answers/answers_mysql/include/
----------- SOME LINES REMOVED ---------------------------------
   creating: /var/www/answers/answers_mysql/utils/
  inflating: /var/www/answers/answers_mysql/ask.php  
----------- SOME LINES REMOVED ---------------------------------
  inflating: /var/www/answers/answers_mysql/utils/DBUtils.class.php  
  inflating: /var/www/answers/answers_mysql/utils/Utils.class.php  
  inflating: /var/www/answers/answers_mysql/utils/init.php  
--------------
drop database answers
--------------
 
--------------
create database answers
--------------
 
--------------
DROP TABLE if exists USERS_SOURCE_TABLE
--------------
 
--------------
CREATE TABLE `USERS_SOURCE_TABLE` (
  USERS_ID_COLUMN int(11),
  username varchar(50),
  USERS_DISPLAY_NAME_COLUMN varchar(50),
  USERS_EMAIL_COLUMN varchar(50),
  CONSTRAINT USERS_SOURCE_TABLE_pkey PRIMARY KEY (USERS_ID_COLUMN)
) ENGINE=InnoDB DEFAULT CHARSET=utf8
--------------
 
----------- SOME LINES REMOVED ---------------------------------
 
--------------
CREATE VIEW `USERS_VIEW_NAME` AS
  SELECT
    `USERS_ID_COLUMN` AS `USERS_ID_COLUMN`,
    `USERS_DISPLAY_NAME_COLUMN` AS `USERS_DISPLAY_NAME_COLUMN`,
    `USERS_EMAIL_COLUMN` AS `USERS_EMAIL_COLUMN`
  FROM
    `USERS_SOURCE_TABLE`
--------------
 
--------------
GRANT SELECT, INSERT, UPDATE, DELETE ON TABLES_PREFIX_users TO 'ANSWERS_DB_USER'@localhost
--------------
 
--------------
GRANT SELECT, INSERT, UPDATE, DELETE ON TABLES_PREFIX_answers TO 'ANSWERS_DB_USER'@localhost
--------------
 
--------------
GRANT SELECT, INSERT, UPDATE, DELETE ON TABLES_PREFIX_questions TO 'ANSWERS_DB_USER'@localhost
--------------
 
--------------
GRANT SELECT, INSERT, UPDATE, DELETE ON TABLES_PREFIX_tags TO 'ANSWERS_DB_USER'@localhost
--------------
 
--------------
GRANT SELECT, INSERT, UPDATE, DELETE ON TABLES_PREFIX_tags_to_quest TO 'ANSWERS_DB_USER'@localhost
--------------
 
--------------
GRANT SELECT, INSERT, UPDATE, DELETE ON TABLES_PREFIX_subscribers TO 'ANSWERS_DB_USER'@localhost
--------------
 
--------------
GRANT SELECT, INSERT, UPDATE, DELETE ON TABLES_PREFIX_votes_a TO 'ANSWERS_DB_USER'@localhost
--------------
 
--------------
GRANT SELECT ON USERS_VIEW_NAME TO 'ANSWERS_DB_USER'@localhost
--------------
 
SSH: EXEC: completed after 1,003 ms
SSH: Disconnecting configuration [Answers test server] ...
SSH: Transferred 2 file(s)
Build step 'Send files or execute commands over SSH' changed build result to SUCCESS
2012-11-14 08:22:49 
 
---BEGIN PLUGIN EXECUTION---
2012-11-14 08:22:49 ---INITIALIZATION STARTED---
2012-11-14 08:22:49 
---BEGIN PLUGIN SETTINGS---
	Nerrvana HTTP address: https://api.nerrvana.com
	Nerrvana API key: 2bf7c81-a031f-1ad2-fd3a6-f59b9e0668e
	Secret key:  wctfFwelygx3tXS4TasrsOS4oXV7YadcPppvEnx55WG7qPk6jrAHjJi1TRoLlhrarIlabte4H9zWROXVkLnXto2LlVC47EXx91Uu
	Space ID: 4144
	Space: Answers
	Space path[FTPS folder]: Answers/_files
	Selenium nodes per platform: 1
	Test run name: Answers TRUNK MySQL
	Nerrvana platforms:
		Opera 12.02 (WinXP)
		Firefox 15.0 (WinXP)
	Executable file: xbuild-mysql.sh
	Nerrvana FTPS address: ftp.nerrvana.com
	Nerrvana FTPS user: demo154
	Nerrvana FTPS pass: dem0l54
	Workspace folder: ./tests
	Max execution time: 3600
	Poll period: 20
	Parse user messages mode[results analyzer]: OFF
-----END PLUGIN SETTINGS---
2012-11-14 08:22:49 -----INITIALIZATION COMPLETED---
 
2012-11-14 08:22:49 Generated test run name: Answers TRUNK MySQL build #55
2012-11-14 08:22:49 Generated test run description:
Created by Nerrvana-Jenkins plugin
Revision: 146
Committer: igork
Date: 2012-11-14 08:22:44 +0000 (Wed, 14 Nov 2012)
"Fixed" robots.txt to initiate Jenkins build
 
2012-11-14 08:22:49 ---BEGIN UPLOADING TESTS TO NERRVANA FTPS---
[workspace] $ lftp -f upload-build-55-1352863447229969289.ftp
2012-11-14 08:23:22 -----END UPLOADING TESTS TO NERRVANA FTPS
 
2012-11-14 08:23:25 Creating and starting test run via Nerrvana HTTP API call...done.
2012-11-14 08:23:25 New test run ID#952.
2012-11-14 08:23:25 New execution ID#5769.
2012-11-14 08:23:25 ---BEGIN NERRVANA POLLING CYCLE (waiting for tests to complete)
2012-11-14 08:23:47 	Current execution status: run
 
2012-11-14 08:24:09 	Current execution status: run
 
----------- SOME LINES REMOVED ---------------------------------
 
2012-11-14 08:26:42 	Current execution status: run
 
2012-11-14 08:27:04 	Current execution status: ok
 
2012-11-14 08:27:04 -----END NERRVANA POLLING CYCLE---
2012-11-14 08:27:04 Saving execution results into /var/lib/jenkins/jobs/Answers/builds/2012-11-14_08-22-45/results.xml...
2012-11-14 08:27:04 Done.
2012-11-14 08:27:04 
-----END PLUGIN EXECUTION---
 
 
2012-11-14 08:27:04 
 
---BEGIN PLUGIN EXECUTION---
2012-11-14 08:27:04 ---INITIALIZATION STARTED---
2012-11-14 08:27:04 
---BEGIN PLUGIN SETTINGS---
	Nerrvana HTTP address: https://api.nerrvana.com
	Nerrvana API key: 2bf7c81-a031f-1ad2-fd3a6-f59b9e0668e
	Secret key:  wctfFwelygx3tXS4TasrsOS4oXV7YadcPppvEnx55WG7qPk6jrAHjJi1TRoLlhrarIlabte4H9zWROXVkLnXto2LlVC47EXx91Uu
	Space ID: 4144
	Space: Answers
	Space path[FTPS folder]: Answers/_files
	Selenium nodes per platform: 1
	Test run name: Answers TRUNK PostgreSQL
	Nerrvana platforms:
		Opera 12.02 (WinXP)
		Firefox 15.0 (WinXP)
	Executable file: xbuild-pgsql.sh
	Nerrvana FTPS address: ftp.nerrvana.com
	Nerrvana FTPS user: demo154
	Nerrvana FTPS pass: dem0l54
	Workspace folder: ./tests
	Max execution time: 3600
	Poll period: 20
	Parse user messages mode[results analyzer]: ON
	User message threshold: ERROR
-----END PLUGIN SETTINGS---
2012-11-14 08:27:04 -----INITIALIZATION COMPLETED---
 
2012-11-14 08:27:04 Generated test run name: Answers TRUNK PostgreSQL build #55
2012-11-14 08:27:04 Generated test run description:
Created by Nerrvana-Jenkins plugin
Revision: 146
Committer: igork
Date: 2012-11-14 08:22:44 +0000 (Wed, 14 Nov 2012)
"Fixed" robots.txt to initiate Jenkins build
 
2012-11-14 08:27:04 ---TESTS UPLOAD SKIPPED---
2012-11-14 08:27:06 Creating and starting test run via Nerrvana HTTP API call...done.
2012-11-14 08:27:06 New test run ID#953.
2012-11-14 08:27:06 New execution ID#5770.
2012-11-14 08:27:06 ---BEGIN NERRVANA POLLING CYCLE (waiting for tests to complete)
2012-11-14 08:27:28 	Current execution status: run
 
2012-11-14 08:27:49 	Current execution status: run
 
----------- SOME LINES REMOVED ---------------------------------
 
2012-11-14 08:30:03 	Current execution status: run
 
2012-11-14 08:30:26 	Current execution status: ok
 
2012-11-14 08:30:26 -----END NERRVANA POLLING CYCLE---
2012-11-14 08:30:26 Saving execution results into /var/lib/jenkins/jobs/Answers/builds/2012-11-14_08-22-45/results.xml...
2012-11-14 08:30:26 Done.
2012-11-14 08:30:26 ---BEGIN TEST EXECUTION RESULTS---
2012-11-14 08:30:26 At least 11 message(s) from Nerrvana side reach(es) or exceed(s) threshold level (ERROR).
Message analyzer marks execution as failure.
2012-11-14 08:30:26 -----END TEST EXECUTION RESULTS---
2012-11-14 08:30:26 
-----END PLUGIN EXECUTION---
 
 
Build step 'Nerrvana plug-in' marked build as failure
Finished: FAILURE

2012-11-14 08:22:49 ---INITIALIZATION STARTED---
----------- SOME LINES REMOVED ---------------------------------
2012-11-14 08:22:49 -----INITIALIZATION COMPLETED---
2012-11-14 08:22:49 Generated test run name: Answers TRUNK MySQL build #55
2012-11-14 08:22:49 Generated test run description:
Created by Nerrvana-Jenkins plugin
Revision: 146
Committer: igork
Date: 2012-11-14 08:22:44 +0000 (Wed, 14 Nov 2012)
"Fixed" robots.txt to initiate Jenkins build

2012-11-14 08:22:49 ---BEGIN UPLOADING TESTS TO NERRVANA FTPS---
[workspace] $ lftp -f upload-build-55-1352863447229969289.ftp
2012-11-14 08:23:22 -----END UPLOADING TESTS TO NERRVANA FTPS

2012-11-14 08:23:25 Creating and starting test run via Nerrvana HTTP API call...done.
2012-11-14 08:23:25 New test run ID#952.
2012-11-14 08:23:25 New execution ID#5769.

2012-11-14 08:23:25 ---BEGIN NERRVANA POLLING CYCLE (waiting for tests to complete)
2012-11-14 08:23:47 	Current execution status: run
----------- SOME LINES REMOVED ---------------------------------
2012-11-14 08:27:04 	Current execution status: ok
2012-11-14 08:27:04 -----END NERRVANA POLLING CYCLE---
2012-11-14 08:27:04 Saving execution results into /var/lib/jenkins/jobs/Answers/builds/2012-11-14_08-22-45/results.xml...
2012-11-14 08:27:04 Done.
2012-11-14 08:27:04 
-----END PLUGIN EXECUTION---

---BEGIN PLUGIN EXECUTION---
2012-11-14 08:27:04 ---INITIALIZATION STARTED---
2012-11-14 08:27:04 
2012-11-14 08:27:04 -----INITIALIZATION COMPLETED---
2012-11-14 08:27:04 Generated test run name: Answers TRUNK PostgreSQL build #55
2012-11-14 08:27:04 Generated test run description:
Created by Nerrvana-Jenkins plugin
Revision: 146
Committer: igork
Date: 2012-11-14 08:22:44 +0000 (Wed, 14 Nov 2012)
"Fixed" robots.txt to initiate Jenkins build

2012-11-14 08:27:04 ---TESTS UPLOAD SKIPPED---

2012-11-14 08:27:06 Creating and starting test run via Nerrvana HTTP API call...done.
2012-11-14 08:27:06 New test run ID#953.
2012-11-14 08:27:06 New execution ID#5770.

2012-11-14 08:27:06 ---BEGIN NERRVANA POLLING CYCLE (waiting for tests to complete)
2012-11-14 08:27:28 	Current execution status: run
----------- SOME LINES REMOVED ---------------------------------
2012-11-14 08:30:26 	Current execution status: ok
2012-11-14 08:30:26 -----END NERRVANA POLLING CYCLE---

2012-11-14 08:30:26 Saving execution results into /var/lib/jenkins/jobs/Answers/builds/2012-11-14_08-22-45/results.xml...
2012-11-14 08:30:26 Done.
2012-11-14 08:30:26 ---BEGIN TEST EXECUTION RESULTS---
2012-11-14 08:30:26 At least 11 message(s) from Nerrvana side reach(es) or exceed(s) threshold level (ERROR).
Message analyzer marks execution as failure.
2012-11-14 08:30:26 -----END TEST EXECUTION RESULTS---
2012-11-14 08:30:26

<api-params>
        <!-- Address of the Nerrvana gateway. -->
        <gateway>https://api.nerrvana.com</gateway>
        <!-- User-specific key which identifies user on Nerrvana side. -->
        <!-- Available as an 'API public key' on Settings page 
            (https://cloud.nerrvana.com/user/editAccount) 
            in Nerrvana. -->
        <apikey>a6c171d-20eb5-61e3-60991-8a1e523ce</apikey>
        <!-- This key is used by the Nerrvana plug-in to create a checksum of API 
            call parameters to ensure their consistency. -->
        <!-- Available as an 'API private key' on Settings page in Nerrvana. -->
        <secretkey>z3rCWlLdAP35eCCYAmQZ2kPw9X0LByrcc3XGh</secretkey>
    </api-params>

<!-- Parameters related to Nerrvana-driven Selenium tests. -->
    <!-- Test Run name template, Jenkins build number will be added to the 
        end automatically. -->
    <test-run-name>Answers TRUNK</test-run-name>

<!-- Test Run description. All Test Runs created by this Jenkins build 
        step will have this description. -->
    <test-run-descr></test-run-descr>

<!-- Content of this file, if not empty, will be added to a description,
        defined by ‘test-run-descr’ parameter above.
        File path is relative to the Jenkins job workspace.
        During deployment phase you can extract revision number, commiter name and a
        commit message from your version control system, put them into this file and
        use them as a description.
        You can extract and parse SVN information into info.txt file with our little
        tool - https://github.com/deepshiftlabs/nerrvana-plugin-for-jenkins-ci
        You can read how we do it with SVN in our blog. -->
    <test-run-descr-file>version.txt</test-run-descr-file>

<!-- Which executable file Nerrvana should use to start tests. -->
    <executable-file>xbuild-mysql.sh</executable-file>

<project name="dslabs-test" default="" basedir=".">
  <!-- BEGIN versions -->
    <property name="title"          value="Tests of http://answers.starty.co"/>
    <property name="version"          value="0.02.000"/>
  <!-- END versions -->
 
  <!-- BEGIN build properties -->
    <property name="build.compiler"       value="javac1.6"/>
    <property name="libdir"               value="${basedir}/lib"/>
    <property name="output"               value="${basedir}/output"/>
    <property name="sources"              value="${basedir}/src"/>
    <property name="resources"            value="${basedir}/res"/>
    <property name="dist"                 value="${basedir}/dist"/>
    <property name="logdir"               value="${basedir}/log"/>
    <property name="bindir"               value="${basedir}/bin"/>
    <property name="logs"            	value="${basedir}/logs"/>
    <property name="test.failonerror"     value="true"/>
    <property name="compile.debug"        value="true"/>
    <property name="compile.debuglevel"   value="lines,vars,source"/>
    <property name="compile.deprecation"  value="true"/>
  <!-- END build properties -->
 
    <taskdef resource="testngtasks" classpath="${libdir}/testng-5.8-jdk15.jar"/>
 
    <path id="classpath">
        <fileset dir="${libdir}">
            <include name="*.jar"/>
        </fileset>
    </path>
 
    <target name="clean">
        <delete dir="${output}"/>
        <delete dir="${logs}"/>
    </target>
 
    <target name="prepare" depends="clean">
        <mkdir dir="${output}"/>
        <mkdir dir="${logs}"/>
    <!-- !!!-->
        <mkdir dir="${logs}/html"/>
        <copy todir="${logs}/html/js">
            <fileset dir="${resources}/js" />
        </copy>
        <copy todir="${logs}/html/img">
            <fileset dir="${resources}/img" />
        </copy>
        <copy todir="${logs}/html/css">
            <fileset dir="${resources}/css" />
        </copy>
 
        <copy file="${resources}/log4j.xml" todir="${output}"/>
        <copy file="${resources}/testng.xml" todir="${output}"/>
        <copy file="${resources}/config-mysql.xml" tofile="${output}/config.xml"/>
    </target>
 
    <target name="bld" depends="prepare">
        <javac
            srcdir="${sources}"
            destdir="${output}"
            excludes=""
            encoding="UTF8"
            debug="${compile.debug}"
            deprecation="${compile.deprecation}"
            optimize="${compile.optimize}"
            debuglevel="${compile.debuglevel}">
            <classpath refid="classpath" />
        </javac>
    </target>
 
    <path id="tests_classpath">
        <fileset dir="${libdir}">
            <include name="*.jar"/>
        </fileset>
        <pathelement location="${output}"/>
    </path>
 
    <target name="run" description="${title}">
        <java classpathref="tests_classpath"
            fork="true"
            dir="${output}"
            classname="org.testng.TestNG"
            failonerror="false">
            <arg value="-d" />
            <arg value="${logs}/testng_reports" />
            <arg value="testng.xml"/>
        </java>
<!--delete dir="${output}"/-->
    </target>
 
  <!-- build all -->
    <target name="all" depends="bld,run" description="Clean, build, and deploy project"/>
</project>

<!-- List of platforms to run tests against for this config. -->
    <platforms>
        <!-- List of available platforms. Uncomment to use. -->
        <!--platform>
            <code>centos_58_firefox_36</code>
            <name>Firefox 3.6 (CentOS)</name>
        </platform-->
        <!--platform>
            <code>winxp_sp3_firefox_110</code>
            <name>Firefox 11.0 (WinXP)</name>
        </platform-->
        <!--platform>
            <code>winxp_sp3_firefox_150</code>
            <name>Firefox 15.0 (WinXP)</name>
        </platform-->
        <!--platform>
            <code>winxp_sp3_firefox_36</code>
            <name>Firefox 3.6 (WinXP)</name>
        </platform-->
        <!--platform>
            <code>winxp_sp3_ie_8</code>
            <name>IE 8 (WinXP)</name>
        </platform-->
        <!--platform>
            <code>winxp_sp3_opera_1162</code>
            <name>Opera 11.62 (WinXP)</name>
        </platform-->
        <!--platform>
            <code>winxp_sp3_opera_1202</code>
            <name>Opera 12.02 (WinXP)</name>
        </platform-->
        <!--platform>
            <code>winxp_sp3_safari_515</code>
            <name>Safari 5.1.5 (WinXP)</name>
        </platform-->
        <!--platform>
            <code>winxp_sp3_safari_517</code>
            <name>Safari 5.1.7 (WinXP)</name>
        </platform-->
 
        <platform>
            <code>winxp_sp3_chrome_2001132</code>
            <name>Chrome 20.0.1132 (WinXP)</name>
        </platform>
        <platform>
            <code>winxp_sp3_chrome_2101180</code>
            <name>Chrome 21.0.1180 (WinXP)</name>
        </platform>
    </platforms>

<!-- How many Selenium nodes should be used for each platform. -->
    <nodes-count>2</nodes-count>

<!-- Parameters related to the transfer of the tests from Jenkins 
        to Nerrvana. -->
    <!-- Folder in the workspace of Jenkins job where Selenium tests will be 
        located. It is assumed that the SCM build step, which always occurs 
        BEFORE other steps, will put tests there. -->
    <folder-with-tests>.</folder-with-tests>

<folder-with-tests>./tests</folder-with-tests>

<!-- Nerrvana space previously created by you through the Nerrvana UI. -->
    <space>
        <id>4144</id>
        <name>Answers</name>
        <ftp-path>Answers/_files</ftp-path>
    </space>

<!-- Address and credentials of the Nerrvana FTPS connection. Note that 
        a system running Jenkins should have LFTP application installed. -->
    <ftp>
        <server>ftp.nerrvana.com</server>
        <!-- Your username -->
        <username>demo123</username>
        <!-- Replace this value with your password!! -->
        <password>[p a s s w o r d]</password>
    </ftp>

<!-- You can skip test sync when you call the Nerrvana plugin many times 
        in a single job and tests were synced in a previous step. -->
    <skip-tests-sync>false</skip-tests-sync>

<!-- Job status will be set to FAILED if test execution in Nerrvana is 
        unsuccessful (tests did not sync, executable file did not start your 
        tests, etc).
            If tests were executed successfully, you have a few options:
        1. Mark build as successful in Jenkins and analyse generated reports 
        for problems your tests discovered.
        2. If you want to mark a build as FAILED based on errors your tests 
        found, you can:
            (a) Add additional step, load results, parse them to analyse errors 
            your tests discovered, and mark build as FAILED based on it. Keep 
            this parameter as 'false' in this case.
            (b) Use Nerrvana "Messages" and let the Nerrvana plugin analyse 
            results, and change build status to FAILED based on it. Keep this 
            parameter as 'true' in this case and use additional parameter 
            'message-threshold' to add additional logic.
            If you use messages and invoke the Nerrvana plug-in several times 
            in the same build, keep this option as 'false' for all invocations 
            except the last one to let the build complete all tests and analyse 
            errors at the very end. -->
    <use-messages-to-set-build-status>false</use-messages-to-set-build-status>
 
    <!-- Defines the level at which a FAILED status is generated. If this 
        value is set to 'WARN', for example, and your tests generate one or more 
        'WARN' or higher severity messages (ERROR or FATAL), Nerrvana execution 
        status, and Jenkins build, will be FAILED. For the full list of levels, 
        visit http://www.nerrvana.com/docs/using-messages page. -->
    <message-threshold>ERROR</message-threshold>

<use-messages-to-set-build-status>true</use-messages-to-set-build-status>
    <message-threshold>ERROR</message-threshold>

<!-- Maximum execution time (in seconds). Defines how long the Nerrvana 
        plug-in will wait for tests to complete. Start by setting to a large 
        value and adjust accordingly after a few runs.-->
    <max-execution-time>3600</max-execution-time>

<!-- How often the Nerrvana plug-in will update test execution status 
        from Nerrvana (in seconds). -->
    <poll-period>20</poll-period>

---BEGIN PLUGIN EXECUTION---
2012-10-17 07:39:24 ---INITIALIZATION STARTED---
2012-10-17 07:39:24
---BEGIN PLUGIN SETTINGS---
   Nerrvana HTTP address: https://api.nerrvana.com
   Nerrvana API key: a6c171d-20eb5-61e3-60991-8a1e523ce
   Secret key: z3rCWlLdAP35eCCYAmQZ2kPw9X0LByrcc
   Space ID: 4144
   Space: Answers
   Space path[FTPS folder]: Answers/_files
   Selenium nodes per platform: 1
   Test run name: Answers TRUNK
   Nerrvana platforms:
      Opera 12.02 (WinXP)
      Firefox 15.0 (WinXP)
   Executable file: xbuild-mysql.sh
   Nerrvana FTPS address: ftp.nerrvana.com
   Nerrvana FTPS user: demo123
   Nerrvana FTPS pass: dem0I23
   Workspace folder: ./tests
   Max execution time: 3600
   Poll period: 20
   Parse user messages mode[results analyzer]: ON
   User message threshold: ERROR
-----END PLUGIN SETTINGS---
2012-10-17 07:39:24 -----INITIALIZATION COMPLETED---
 
2012-10-17 07:39:24 Generated test run name: Answers TRUNK MySQL build #51
2012-10-17 07:39:24 Generated test run description:
Created by Nerrvana-Jenkins plugin
Revision: 142
Committer: igork
Date: 2012-10-17 07:39:20 +0000 (Wed, 17 Oct 2012)
Launching all tests on two platforms
 
2012-10-17 07:39:24 ---BEGIN UPLOADING TESTS TO NERRVANA FTPS---
[workspace] $ lftp -f upload-build-51-8414449724631519802.ftp
 
2012-10-17 07:40:16 -----END UPLOADING TESTS TO NERRVANA FTPS
 
2012-10-17 07:40:18 Creating and starting test run 
                    via Nerrvana HTTP API call...done.
2012-10-17 07:40:18 New test run ID#884.
2012-10-17 07:40:18 New execution ID#5486.
2012-10-17 07:40:18 ---BEGIN NERRVANA POLLING CYCLE 
                       (waiting for tests to complete)
 
2012-10-17 07:40:40    Current execution status: run
 
2012-10-17 07:41:02    Current execution status: run
 
------ Some оutput removed ---------------------------------
 
2012-10-17 07:44:17    Current execution status: run
 
2012-10-17 07:44:38    Current execution status: ok
 
2012-10-17 07:44:38 -----END NERRVANA POLLING CYCLE---
2012-10-17 07:44:38 Saving execution results into results.xml...
2012-10-17 07:44:38 Done.
2012-10-17 07:44:38 ---BEGIN TEST EXECUTION RESULTS---
2012-10-17 07:44:38 At least 43 message(s) from Nerrvana side reach(es) 
                    or exceed(s) threshold level (ERROR).
Message analyzer marks execution as failure.
2012-10-17 07:44:38 -----END TEST EXECUTION RESULTS---
2012-10-17 07:44:38
-----END PLUGIN EXECUTION---
 
Build step 'Nerrvana plug-in' marked build as failure
Finished: FAILURE

<?xml version="1.0" encoding="UTF-8"?>
<project name="${env.JOB_NAME}" default="build" basedir=".">
    <property environment="env"/>
    <property name="tests" value="${env.WORKSPACE}/tests"/>
    <property name="ci" value="${env.WORKSPACE}/ci"/>
    <property name="code" value="${env.WORKSPACE}/code"/>
 
    <target name="make_settings">
        <exec executable="sed" output="${code}/config/Settings.class.php.mysql">
            <arg line="-f ${ci}/deployment/config/mysql/settings-mysql.sed ${code}/config/Settings.class.template.php" />
        </exec>
    </target>
 
    <target name="make_sql">
        <exec executable="sed" output="${code}/install/mysql.sql">
            <arg line="-f ${ci}/deployment/config/mysql/install-mysql.sed ${code}/install/mysql.sql" />
        </exec>
    </target>
 
    <target name="move_files" depends="make_settings,make_sql">
        <!-- Move authentication files to WAUT root -->
       <move file="${ci}/deployment/misc/login.php" tofile="${code}/login.php" />
        <move file="${ci}/deployment/misc/logout.php" tofile="${code}/logout.php" />
 
        <!-- Move MySQL db creation files to install folder -->
        <move file="${ci}/deployment/config/mysql/crt-mysql.sql" tofile="${code}/install/crt-mysql.sql" />
 
        <!-- Move publish script to the workspace root, so it will be beside prj.zip -->
       <move file="${ci}/deployment/publish-over-ssh/publish.sh" tofile="${env.WORKSPACE}/publish.sh" />
    </target>
 
    <target name="save_commit_info" depends="move_files">
        <exec dir="${env.WORKSPACE}" executable="svn" >
                    <arg line="--username jenkins --password 123456 upgrade" />
        </exec>    
      <exec dir="${env.WORKSPACE}" executable="svn"  output="${env.WORKSPACE}/version.txt">  
          <arg line="--username jenkins --password 123456 log -r ${env.SVN_REVISION}" />
      </exec>
      <exec dir="${env.WORKSPACE}" executable="svn">  
          <arg line="--username jenkins --password 123456 log -r ${env.SVN_REVISION}" />
      </exec>
 
    </target>   
 
    <target name="svn" depends="save_commit_info">
       <java dir="." jar="${ci}/deployment/scm-decorator.jar" fork="true" failonerror="true">
         <arg value="svn"/>
         <arg value="${env.WORKSPACE}/version.txt"/> 
       </java>       
    </target>
 
    <target name="zip" depends="svn" description="Compress project files">
        <jar destfile="${env.WORKSPACE}/prj.zip"
            basedir="${env.WORKSPACE}/code"
            excludes=".svn" />
    </target>
 
   <target name="build" depends="zip" />
</project>

<target name="test">
    <echo message="Jenkins workspace: ${env.WORKSPACE}"/>
    <echo message="Job directory: ${env.WORKSPACE}/../../${env.JOB_NAME}"/>
    <echo message="Build data: ${env.WORKSPACE}/../../${env.JOB_NAME}/builds/${env.BUILD_ID}"/>
</target>

<property name="tests" value="${env.WORKSPACE}/tests"/>
    <property name="ci" value="${env.WORKSPACE}/ci"/>
    <property name="code" value="${env.WORKSPACE}/code"/>

<target name="make_settings">
        <exec executable="sed" output="${code}/config/Settings.class.php.mysql">
            <arg line="-f ${ci}/deployment/config/mysql/settings-mysql.sed ${code}/config/Settings.class.template.php" />
        </exec>
    </target>

// Database IP or hostname (use colon, if runs on non-standard port: 127.0.0.1:563)
    const DB_HOST = "";
 
    // Username to connect to DB
    const DB_USER = "";

s/const DB_USER = "";/const DB_USER = "ANSWERS_DB_USER";/g
s/const DB_HOST = "";/const DB_HOST = "localhost";/g

// Database IP or hostname (use colon, if runs on non-standard port: 127.0.0.1:563)
    const DB_HOST = "localhost";
 
    // Username to connect to DB
    const DB_USER = "ANSWERS_DB_USER";

<target name="make_sql">
        <exec executable="sed" output="${code}/install/mysql.sql">
            <arg line="-f ${ci}/deployment/config/mysql/install-mysql.sed ${code}/install/mysql.sql" />
        </exec>
    </target>

s/USERS_TABLE/USERS_VIEW_NAME/g
s/USE ANSWERS_DATABASE/USE answers/g

<target name="move_files" depends="make_settings,make_sql">
        <!-- Move authentication files to WAUT root -->
       <move file="${ci}/deployment/misc/login.php" tofile="${code}/login.php" />
        <move file="${ci}/deployment/misc/logout.php" tofile="${code}/logout.php" />
 
        <!-- Move MySQL db creation files to install folder -->
        <move file="${ci}/deployment/config/mysql/crt-mysql.sql" tofile="${code}/install/crt-mysql.sql" />
 
        <!-- Move publish script to the workspace root, so it will be beside prj.zip -->
       <move file="${ci}/deployment/publish-over-ssh/publish.sh" tofile="${env.WORKSPACE}/publish.sh" />
    </target>

DROP DATABASE answers;
CREATE DATABASE answers;
use answers;
 
DROP TABLE if exists USERS_SOURCE_TABLE;
CREATE TABLE `USERS_SOURCE_TABLE` (
  USERS_ID_COLUMN int(11),
  username varchar(50),
  USERS_DISPLAY_NAME_COLUMN varchar(50),
  USERS_EMAIL_COLUMN varchar(50),
  CONSTRAINT USERS_SOURCE_TABLE_pkey PRIMARY KEY (USERS_ID_COLUMN)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;
 
INSERT INTO USERS_SOURCE_TABLE VALUES(1,'answ_test_admin@dslabs.lan','Arnie - Admin','answ_test_admin@dslabs.lan');
INSERT INTO USERS_SOURCE_TABLE VALUES(2,'answ_test_user@dslabs.lan','Ivan Danko - Captain','answ_test_user@dslabs.lan');
INSERT INTO USERS_SOURCE_TABLE VALUES(3,'answ_test_staff@dslabs.lan','Lee - Guru(Staff)','answ_test_staff@dslabs.lan');
 
DROP USER 'ANSWERS_DB_USER'@localhost;
FLUSH PRIVILEGES;

<target name="save_commit_info" depends="move_files">
        <exec dir="${env.WORKSPACE}" executable="svn" >
                    <arg line="--username jenkins --password 123456 upgrade" />
        </exec>    
      <exec dir="${env.WORKSPACE}" executable="svn"  output="${env.WORKSPACE}/version.txt">  
          <arg line="--username jenkins --password 123456 log -r ${env.SVN_REVISION}" />
      </exec>
      <exec dir="${env.WORKSPACE}" executable="svn">  
          <arg line="--username jenkins --password 123456 log -r ${env.SVN_REVISION}" />
      </exec>                  
    </target>

#cat version.txt
------------------------------------------------------------------------
r69 | igork | 2012-10-03 07:38:38 +0000 (Wed, 03 Oct 2012) | 1 line
 
Fixed bug #342
------------------------------------------------------------------------

#cat version.txt
Revision: 69
Committer: igork
Date: 2012-10-03 07:38:38 +0000 (Wed, 03 Oct 2012)
Fixed bug #342

<target name="svn" depends="save_commit_info">
       <java dir="." jar="${ci}/deployment/scm-decorator.jar" fork="true" failonerror="true">
         <arg value="svn"/>
         <arg value="${env.WORKSPACE}/version.txt"/> 
       </java>       
    </target>

<target name="zip" depends="svn" description="Compress project files">
        <jar destfile="${env.WORKSPACE}/prj.zip"
            basedir="${env.WORKSPACE}/code"
            excludes=".svn" />
    </target>

#!/bin/sh
 
WWW_MYSQL_DIR='/var/www/answers/answers_mysql'
DB_NAME='answers'
 
rm -Rf $WWW_MYSQL_DIR/*
unzip -o prj.zip -d $WWW_MYSQL_DIR
mv $WWW_MYSQL_DIR/config/Settings.class.php.mysql $WWW_MYSQL_DIR/config/Settings.class.php
chmod -R 777 $WWW_MYSQL_DIR
mysql -v -u root  < $WWW_MYSQL_DIR/install/crt-mysql.sql
mysql -v -u root  < $WWW_MYSQL_DIR/install/mysql.sql $DB_NAME

rm -Rf $WWW_MYSQL_DIR/*

unzip -o prj.zip -d $WWW_MYSQL_DIR

mv $WWW_MYSQL_DIR/config/Settings.class.php.mysql $WWW_MYSQL_DIR/config/Settings.class.php

chmod -R 777 $WWW_MYSQL_DIR

mysql -v -u root < $WWW_MYSQL_DIR/install/crt-mysql.sql

mysql -v -u root < $WWW_MYSQL_DIR/install/mysql.sql $DB_NAME

Started by an SCM change
Building in workspace /var/lib/jenkins/jobs/Answers_deployment_only/workspace
Cleaning local Directory .
Checking out http://192.168.3.97/repos/answers/trunk at revision 140
A         tests
------ Output removed - comment by Igor --------------------------------- 
AU        ci/deployment/scm-decorator.jar
A         ci/deployment/build.xml
A         ci/toolchain
A         ci/toolchain/build-toolchain.xml
At revision 140
[deployment] $ ant -file build.xml build
Buildfile: build.xml
 
make_settings:
 
make_sql:
 
move_files:
     [move] Moving 1 file to /var/lib/jenkins/jobs/Answers_deployment_only/workspace/code
     [move] Moving 1 file to /var/lib/jenkins/jobs/Answers_deployment_only/workspace/code/install
     [move] Moving 1 file to /var/lib/jenkins/jobs/Answers_deployment_only/workspace
 
save_commit_info:
     [exec] Upgraded '.'
------ Output removed - comment by Igor --------------------------------- 
     [exec] Upgraded 'ci/deployment/misc'
     [exec] Upgraded 'ci/toolchain'
     [exec] ------------------------------------------------------------------------
     [exec] r140 | igork | 2012-10-08 11:46:01 +0000 (Mon, 08 Oct 2012) | 1 line
     [exec] 
     [exec] Test 2345
     [exec] ------------------------------------------------------------------------
 
svn:
 
zip:
      [jar] Building jar: /var/lib/jenkins/jobs/Answers_deployment_only/workspace/prj.zip
 
build:
 
BUILD SUCCESSFUL
Total time: 0 seconds
SSH: Connecting from host [mantis.deepshiftlabs.com]
SSH: Connecting with configuration [Answers test server] ...
SSH: EXEC: STDOUT/STDERR from command [chmod +x publish.sh
./publish.sh] ...
Archive:  prj.zip<div style="float: left;"><img style="padding: 5px 20px 10px 0;" title="Using Nerrvana - deployment &amp; Jenkins (part 2)" src="http://www.deepshiftlabs.com/sel_blog/wp-content/uploads/2012/08/deployment_2_300.png" alt="Using Nerrvana - deployment &amp; Jenkins (part 2)" /></div>
[lang_ru]
<p style="text-align: center;"><em>Создание Jenkins job - подробности</br>сборки приложения у нас - установка</br>приложения для тестирования</em></p>
 
В <a href="http://www.deepshiftlabs.com/sel_blog/?p=2255&lang=ru" target="_blank">предыдущем посте</a> мы закончили конфигурирование Jenkins и теперь можем создать задачу по тестированию нашего приложения.
 
Открываем страницу http://your_jenkins_host/view/All/newJob и вводим название job. Поскольку наше приложение называется <a href="http://answers.starty.co" target="_blank">Answers</a>, то мы используем его.
 
На практике удобно добавить информацию о версии. Например, job 'Answers TRUNK' тестирует TRUNK, job 'Answers Release 1.4' тестирует Release 1.4.
[/lang_ru][lang_en-us]
<p style="text-align: center;"><em>What is a web application deployment - Jenkins installation and configuration - preparing Jenkins for deployment</em></p>
Let’s talk about deployment. In the most general case, it is a transformation of the source code retrieved from a version control system into a running application. We do not use Jenkins to update our live sites and services yet, but we assume that the deployment for testing is not very different from deployment for upgrade or install. In the latter case, you need to take care of users, informing them in advance about the service downtime, and to give attention to security - access rights to files, the possibility of a rollback automatically in case of failure. These problems do not interest us at the moment anyway. We need to get the application running on an internal server which can be accessed by Selenium tests. Each application will have a slightly different deployment, and we will describe how we deploy, with some simplifications. In the last post of this mini-series, we will show our real configuration, but for now this information will be excessive.
[/lang_en-us]<!--more-->[lang_ru]
 
<img class="aligncenter" style="-ms-interpolation-mode: bicubic;" src="http://www.deepshiftlabs.com/sel_blog/wp-content/uploads/2012/10/build_1.png" alt="New Jenkins job" title="New Jenkins job" />
 
Далее в секции 'Advanced Project Options' нажимаем кнопку 'Advanced ...' и выставляем 'Quiet period' в 0 секунд. Мы знаем, что многие делают build несколько раз в день. В этом случае параметры запуска Jenkins job будут иными. Мы же делаем build под каждый коммит и потому нам нет смысла ждать 5 секунд. Помощь в Jenkins к этому пункту очень хорошо описывает практические случаи, когда эта опция нужна.
 
<img class="aligncenter" style="-ms-interpolation-mode: bicubic;" src="http://www.deepshiftlabs.com/sel_blog/wp-content/uploads/2012/10/build_advanced_1_5.png" alt="New Jenkins job - Advanced project options" title="New Jenkins job - Advanced project options" />
 
Теперь переходим к секции 'Source Code Management', выбираем SVN, который мы используем.
 
<img class="aligncenter" style="-ms-interpolation-mode: bicubic;" src="http://www.deepshiftlabs.com/sel_blog/wp-content/uploads/2012/10/build_svn_1.png" alt="New Jenkins job - Source Code Management" title="New Jenkins job - Source Code Management" />
 
Jenkins попросит ввести детали пользователя SVN. Выбираем 'Check out strategy' - 'Always check out a fresh copy'.
 
<img class="aligncenter" style="-ms-interpolation-mode: bicubic;" src="http://www.deepshiftlabs.com/sel_blog/wp-content/uploads/2012/10/build_svn_2.png" alt="New Jenkins job - Check out strategy" title="New Jenkins job - Check out strategy" />
 
Следующая секция 'Build Triggers'. Используем 'Poll SCM'. В нашем случае 'push' trigger-ом, который советует использовать справка к этому пункту, является SVN хук, который мы <a href="http://www.deepshiftlabs.com/sel_blog/?p=2253&lang=ru" target="_blank">добавили ранее</a>. Если вы откроете справку к опции 'Build periodically', вы увидите следующее замечание: "When people first start continuous integration, they are often so used to the idea of regularly scheduled builds like nightly/weekly that they use this feature. However, the point of continuous integration is to start a build as soon as a change is made, to provide a quick feedback to the change." Как раз, поэтому наши builds запускаются сразу при изменении кода проекта.
 
<img class="aligncenter" style="-ms-interpolation-mode: bicubic;" src="http://www.deepshiftlabs.com/sel_blog/wp-content/uploads/2012/10/build_triggers_3.png" alt="New Jenkins job - Build Triggers" title="New Jenkins job - Build Triggers" />
 
Далее пропускаем секцию 'Build Environment' и переходим к 'Build'. Нажимаем кнопку 'Add build step' и выбираем опцию 'Invoke Ant'.
 
<img class="aligncenter" style="-ms-interpolation-mode: bicubic;" src="http://www.deepshiftlabs.com/sel_blog/wp-content/uploads/2012/10/build_step_4.png" alt="New Jenkins job - Add Build Step" title="New Jenkins job - Add Build Step" />
 
Как вы видите, конфигурационный файл Ant находится тоже в SVN. По завершении извлечении кода на предыдущем шаге, он оказывается в нужном месте в нужное время (хочется ему в этом позавидовать). Задача этого шага в том, чтобы подготовить код, извлеченный из системы контроля версий, к передаче на deployment хост для дальнейшей установки приложения на нём. Мы хотим по возможности сделать максимум операций на jenkins хосте.
 
<img class="aligncenter" style="-ms-interpolation-mode: bicubic;" src="http://www.deepshiftlabs.com/sel_blog/wp-content/uploads/2012/10/build_ant.png" alt="New Jenkins job - Invoke Ant" title="New Jenkins job - Invoke Ant" />
 
Далее я расскажу, чем мы озадачили Ant. Вот так выглядит наш build.xml. 
 
<pre lang="xml" line="1"><?xml version="1.0" encoding="UTF-8"?>
<project name="${env.JOB_NAME}" default="build" basedir=".">
    <property environment="env"/>
    <property name="tests" value="${env.WORKSPACE}/tests"/>
    <property name="ci" value="${env.WORKSPACE}/ci"/>
    <property name="code" value="${env.WORKSPACE}/code"/>
 
    <target name="make_settings">
        <exec executable="sed" output="${code}/config/Settings.class.php.mysql">
            <arg line="-f ${ci}/deployment/config/mysql/settings-mysql.sed ${code}/config/Settings.class.template.php" />
        </exec>
    </target>
 
    <target name="make_sql">
        <exec executable="sed" output="${code}/install/mysql.sql">
            <arg line="-f ${ci}/deployment/config/mysql/install-mysql.sed ${code}/install/mysql.sql" />
        </exec>
    </target>
 
    <target name="move_files" depends="make_settings,make_sql">
        <!-- Move authentication files to WAUT root -->
       <move file="${ci}/deployment/misc/login.php" tofile="${code}/login.php" />
        <move file="${ci}/deployment/misc/logout.php" tofile="${code}/logout.php" />
 
        <!-- Move MySQL db creation files to install folder -->
        <move file="${ci}/deployment/config/mysql/crt-mysql.sql" tofile="${code}/install/crt-mysql.sql" />
 
        <!-- Move publish script to the workspace root, so it will be beside prj.zip -->
       <move file="${ci}/deployment/publish-over-ssh/publish.sh" tofile="${env.WORKSPACE}/publish.sh" />
    </target>
 
    <target name="save_commit_info" depends="move_files">
        <exec dir="${env.WORKSPACE}" executable="svn" >
                    <arg line="--username jenkins --password 123456 upgrade" />
        </exec>    
      <exec dir="${env.WORKSPACE}" executable="svn"  output="${env.WORKSPACE}/version.txt">  
          <arg line="--username jenkins --password 123456 log -r ${env.SVN_REVISION}" />
      </exec>
      <exec dir="${env.WORKSPACE}" executable="svn">  
          <arg line="--username jenkins --password 123456 log -r ${env.SVN_REVISION}" />
      </exec>
 
    </target>   
 
    <target name="svn" depends="save_commit_info">
       <java dir="." jar="${ci}/deployment/scm-decorator.jar" fork="true" failonerror="true">
         <arg value="svn"/>
         <arg value="${env.WORKSPACE}/version.txt"/> 
       </java>       
    </target>
 
    <target name="zip" depends="svn" description="Compress project files">
        <jar destfile="${env.WORKSPACE}/prj.zip"
            basedir="${env.WORKSPACE}/code"
            excludes=".svn" />
    </target>
 
   <target name="build" depends="zip" />
</project>

<target name="test">
    <echo message="Jenkins workspace: ${env.WORKSPACE}"/>
    <echo message="Job directory: ${env.WORKSPACE}/../../${env.JOB_NAME}"/>
    <echo message="Build data: ${env.WORKSPACE}/../../${env.JOB_NAME}/builds/${env.BUILD_ID}"/>
</target>

<property name="tests" value="${env.WORKSPACE}/tests"/>
    <property name="ci" value="${env.WORKSPACE}/ci"/>
    <property name="code" value="${env.WORKSPACE}/code"/>

<target name="make_settings">
        <exec executable="sed" output="${code}/config/Settings.class.php.mysql">
            <arg line="-f ${ci}/deployment/config/mysql/settings-mysql.sed ${code}/config/Settings.class.template.php" />
        </exec>
    </target>

// Database IP or hostname (use colon, if runs on non-standard port: 127.0.0.1:563)
    const DB_HOST = "";
 
    // Username to connect to DB
    const DB_USER = "";

s/const DB_USER = "";/const DB_USER = "ANSWERS_DB_USER";/g
s/const DB_HOST = "";/const DB_HOST = "localhost";/g

// Database IP or hostname (use colon, if runs on non-standard port: 127.0.0.1:563)
    const DB_HOST = "localhost";
 
    // Username to connect to DB
    const DB_USER = "ANSWERS_DB_USER";

<target name="make_sql">
        <exec executable="sed" output="${code}/install/mysql.sql">
            <arg line="-f ${ci}/deployment/config/mysql/install-mysql.sed ${code}/install/mysql.sql" />
        </exec>
    </target>

s/USERS_TABLE/USERS_VIEW_NAME/g
s/USE ANSWERS_DATABASE/USE answers/g

<target name="move_files" depends="make_settings,make_sql">
        <!-- Move authentication files to WAUT root -->
       <move file="${ci}/deployment/misc/login.php" tofile="${code}/login.php" />
        <move file="${ci}/deployment/misc/logout.php" tofile="${code}/logout.php" />
 
        <!-- Move MySQL db creation files to install folder -->
        <move file="${ci}/deployment/config/mysql/crt-mysql.sql" tofile="${code}/install/crt-mysql.sql" />
 
        <!-- Move publish script to the workspace root, so it will be beside prj.zip -->
       <move file="${ci}/deployment/publish-over-ssh/publish.sh" tofile="${env.WORKSPACE}/publish.sh" />
    </target>

DROP DATABASE answers;
CREATE DATABASE answers;
use answers;
 
DROP TABLE if exists USERS_SOURCE_TABLE;
CREATE TABLE `USERS_SOURCE_TABLE` (
  USERS_ID_COLUMN int(11),
  username varchar(50),
  USERS_DISPLAY_NAME_COLUMN varchar(50),
  USERS_EMAIL_COLUMN varchar(50),
  CONSTRAINT USERS_SOURCE_TABLE_pkey PRIMARY KEY (USERS_ID_COLUMN)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;
 
INSERT INTO USERS_SOURCE_TABLE VALUES(1,'answ_test_admin@dslabs.lan','Arnie - Admin','answ_test_admin@dslabs.lan');
INSERT INTO USERS_SOURCE_TABLE VALUES(2,'answ_test_user@dslabs.lan','Ivan Danko - Captain','answ_test_user@dslabs.lan');
INSERT INTO USERS_SOURCE_TABLE VALUES(3,'answ_test_staff@dslabs.lan','Lee - Guru(Staff)','answ_test_staff@dslabs.lan');
 
DROP USER 'ANSWERS_DB_USER'@localhost;
FLUSH PRIVILEGES;

<target name="save_commit_info" depends="move_files">
        <exec dir="${env.WORKSPACE}" executable="svn" >
                    <arg line="--username jenkins --password 123456 upgrade" />
        </exec>    
      <exec dir="${env.WORKSPACE}" executable="svn"  output="${env.WORKSPACE}/version.txt">  
          <arg line="--username jenkins --password 123456 log -r ${env.SVN_REVISION}" />
      </exec>
      <exec dir="${env.WORKSPACE}" executable="svn">  
          <arg line="--username jenkins --password 123456 log -r ${env.SVN_REVISION}" />
      </exec>                  
    </target>

#cat version.txt
------------------------------------------------------------------------
r69 | igork | 2012-10-03 07:38:38 +0000 (Wed, 03 Oct 2012) | 1 line
 
Fixed bug #342
------------------------------------------------------------------------

#cat version.txt
Revision: 69
Committer: igork
Date: 2012-10-03 07:38:38 +0000 (Wed, 03 Oct 2012)
Fixed bug #342

<target name="svn" depends="save_commit_info">
       <java dir="." jar="${ci}/deployment/scm-decorator.jar" fork="true" failonerror="true">
         <arg value="svn"/>
         <arg value="${env.WORKSPACE}/version.txt"/> 
       </java>       
    </target>

<target name="zip" depends="svn" description="Compress project files">
        <jar destfile="${env.WORKSPACE}/prj.zip"
            basedir="${env.WORKSPACE}/code"
            excludes=".svn" />
    </target>

#!/bin/sh
 
WWW_MYSQL_DIR='/var/www/answers/answers_mysql'
DB_NAME='answers'
 
rm -Rf $WWW_MYSQL_DIR/*
unzip -o prj.zip -d $WWW_MYSQL_DIR
mv $WWW_MYSQL_DIR/config/Settings.class.php.mysql $WWW_MYSQL_DIR/config/Settings.class.php
chmod -R 777 $WWW_MYSQL_DIR
mysql -v -u root  < $WWW_MYSQL_DIR/install/crt-mysql.sql
mysql -v -u root  < $WWW_MYSQL_DIR/install/mysql.sql $DB_NAME

rm -Rf $WWW_MYSQL_DIR/*

unzip -o prj.zip -d $WWW_MYSQL_DIR

mv $WWW_MYSQL_DIR/config/Settings.class.php.mysql $WWW_MYSQL_DIR/config/Settings.class.php

chmod -R 777 $WWW_MYSQL_DIR

mysql -v -u root < $WWW_MYSQL_DIR/install/crt-mysql.sql

mysql -v -u root < $WWW_MYSQL_DIR/install/mysql.sql $DB_NAME

Started by an SCM change
Building in workspace /var/lib/jenkins/jobs/Answers_deployment_only/workspace
Cleaning local Directory .
Checking out http://192.168.3.97/repos/answers/trunk at revision 140
A         tests
------ Output removed - comment by Igor --------------------------------- 
AU        ci/deployment/scm-decorator.jar
A         ci/deployment/build.xml
A         ci/toolchain
A         ci/toolchain/build-toolchain.xml
At revision 140
[deployment] $ ant -file build.xml build
Buildfile: build.xml
 
make_settings:
 
make_sql:
 
move_files:
     [move] Moving 1 file to /var/lib/jenkins/jobs/Answers_deployment_only/workspace/code
     [move] Moving 1 file to /var/lib/jenkins/jobs/Answers_deployment_only/workspace/code/install
     [move] Moving 1 file to /var/lib/jenkins/jobs/Answers_deployment_only/workspace
 
save_commit_info:
     [exec] Upgraded '.'
------ Output removed - comment by Igor --------------------------------- 
     [exec] Upgraded 'ci/deployment/misc'
     [exec] Upgraded 'ci/toolchain'
     [exec] ------------------------------------------------------------------------
     [exec] r140 | igork | 2012-10-08 11:46:01 +0000 (Mon, 08 Oct 2012) | 1 line
     [exec] 
     [exec] Test 2345
     [exec] ------------------------------------------------------------------------
 
svn:
 
zip:
      [jar] Building jar: /var/lib/jenkins/jobs/Answers_deployment_only/workspace/prj.zip
 
build:
 
BUILD SUCCESSFUL
Total time: 0 seconds
SSH: Connecting from host [mantis.deepshiftlabs.com]
SSH: Connecting with configuration [Answers test server] ...
SSH: EXEC: STDOUT/STDERR from command [chmod +x publish.sh
./publish.sh] ...
Archive:  prj.zip
   creating: /var/www/answers/answers_mysql/META-INF/
------ Output removed - comment by Igor ---------------------------------   
  inflating: /var/www/answers/answers_mysql/utils/Utils.class.php  
  inflating: /var/www/answers/answers_mysql/utils/init.php  
--------------
drop database answers
--------------
 
--------------
create database answers
--------------
------ Output removed - comment by Igor --------------------------------- 
--------------
GRANT SELECT ON USERS_VIEW_NAME TO 'ANSWERS_DB_USER'@localhost
--------------
 
SSH: EXEC: completed after 1,003 ms
SSH: Disconnecting configuration [Answers test server] ...
SSH: Transferred 2 file(s)
Build step 'Send files or execute commands over SSH' changed build result to SUCCESS
Finished: SUCCESS
 
1-11 - Jenkins среагировал на коммит и делает check out a fresh copy
12-40  - выполняется build.xml с target build
24-28 - происходит ‘svn upgrade’ рабочей копии
29-33 - файл который декоратор преобразует в простой формат
44-46 - результаты были отправлены на deployment хост и запустился скрипт publish.sh
49-52 - распаковался prj.zip в корень виртуального хоста Apache
53-63 - выполнились SQL скрипты, которые запускает publish.sh