1,234
edits
Changes
no edit summary
{{Admon/obsolete}}
<big><big> Continuous Integration Project for NexJ Express Code</big></big>
{{NexJ_Express Index}}
[[category: NexJ_Past_Projects]]
==Project goal==
Currently, NexJ has a Mercurial Repository (Internal) in which, the NexJ Express Server (Core) code is maintained with all its histories. NexJ is planning to share a Core Repository with the Open Source Community by creating a Repository (External) that will be kept in sync with the Internal Repository.<br/>
=== Contributors ===
* [[Minooz/Projects | Minoo Ziaei]]
* [[User:Gbatumbya|Grace Batumbya]]
==Version Control ToolCurrent Status==* Basic Tutorial @ http:<big><big>Project Completed</big></hginit.com/big>* '''comparing popular version control tools''' [http://martinfowler.com/bliki<br/VersionControlTools.html]# '''[[Mercurial-nexj | Mercurial]]'''#'''CVS'''#'''SVN'''#'''Git'''>
==ScriptingProject Phases===== Phase 1: Design Proposal (Done) ===*1Get requirements from NexJ* Incorporate requirements from NexJ into Design of algorithm for syncing repositories* Provide the proposal for review and approved - '''[[Ant-nexj Continuous_Integration/proposal | Antfinal version of proposal]]''', [https://docs.google.com/document/d/17Fuj_9A7sBkzlbP0t0bOY3Qs1iiAhKAvfNTuUMnHUcg/edit?hl=en_US Google Doc ] ===Phase 2:A new ant script is created eCreating Similar Environment (Done) ===* Internal Repository** Creating a Mercurial repository and adding some changes to it to grow the history of it.g* Controller** This will be containing temporary repositories as the result of scripting. * External Repository** Creating another Mercurial repository using 'hg'buildHudson.xmlcommands from the latest 'change-set' that triggers the target(assign1of Internal Repository.test) of main build file ===Phase 3: Scripting (build.xmlDone) ===* Ant** Doesn't support some of non-regular Mercurial commands that we need to play with ''change-sets''* Bash** Supports everything we need for the project. See below:[[Continuous_Integration/script | script]] <source lang=java><project name="assign1" basedir="." defaultPhase 4: Running the script on CI system (Done) ==="myTarget"> <target name="assign1* Buildbot* Hudson** Simple to setup and configure.build.call"> <!-- Call the target that does everything -->** Runs different types of scripts: ''bash'', ''ant'', ''batch''** Can be scheduled to run automatically or manually <ant antfile="build** [http://iran.proximity.xml" target="assign1on.test"ca:8080/>Test Project] </target> <target name="myTarget.check" depends="assign1.build.call">=Phase 5: Code Review (Done)=== <echo>The assign1* Execute the script on one of Nexj computers.build was called!</echo> </target></project>===Phase 6: Make Changes as per Code Review (Done)===</source>* Define paths based on Nexj's requirements*2Modify the script to be able to retrieve change- '''sets of a remote repository* Create specific error message for each problem during running the script ===Phase 7: Code Review (Done)===* Send code for review.* [[Bash-http://mercurial.nexj| Bash].com/express.cgi/ NexJ Express Repository in use]'''
==Challenges==
*1- I was receiving an error message while trying to do a new build on Hudson. It didn't let to clone the project on Hudson workspace. The error message is "Access is denied". So I had to delete the project and create a new one. Apparently one of the reasons is that Hudson doesn't let you queue the jobs. So, if you interrupt a job that is scheduled, you'll get the error message.*2- To run a bash script to build the project, there are 2 ways: :Execute Windows Batch Command: <source lang=bash>D:\cygwin\bin\bash /home/HudsonPrac/buildHudson.sh</source>:Invoke an Ant Script<source lang=java><project name="assign1" basedir="."> <target name="myTarget" > <exec executable="D:\cygwin\bin\bash" newenvironment="false"> <arg value="/home/HudsonPrac/buildHudson.sh"/> </exec> </target></project></source>*3- Since the bash script is running in Windows platform through Cygwin, there are some conflicts,so the PATH was changed to: PATH=/usr/bin:$PATHRead more about some conflicts [http://cygwin.com/cygwin-ug-net/using.html#using-pathnames here]*4- If there was an error applying a patch to a repository e.g. <code> hg import patch12.patch <[Continuous_Integration/code>, there might be a problem with line numbers merging issue. So, there will be an error created with this message: "Hunk #1 Failed". There are some ways to remove the hunks manually or just ignore that patch, if the later versions are fixed.: By "hunk" I mean a "snippet of change", i.e. a part challenges | List of the "diff". TortoiseHg uses this terminology and so does darcs. – Deniz Dogan: For Hunk Failed message, first we need to make sure it's not applied before. Second thing to check is that bases are the same. All the revisions before that new changeset even with failed build should be applied before applying the successfully built change-set.*5- If there is an uncommited message, the script can not work properly, e.g. Rev is 18+. So, error should be displayed for the uncommited change-sets.*6- To run JUnit Tests from command line:: add the JUnit installation directory and the junit.jar file and also QTjava to the CLASSPATH. e.g. <code>CLASSPATH=".;D:\cygwin\home\java\junit3.0.1\junit.jar;C:\Program Files\java\jre6\lib\ext\QTjava"</code>: to run a sample AllTests class go to the installation directory and run: <code> java junit.textui.TestRunner junit.samples.AllTests </code>: to run NexJ AllTests do::: build the model: go to ws/core/build/ run <code> ant </code> or <code> ant -f build_JUnitTest.xml</code> :: from command line: go to ws/out/core/ run <code> java junit.textui.TestRunner nexj.core.AllTests</code> (getting error IOExcpetion) so we just ran one test file <code> java junit.textui.TestRunner nexj.core.util.MathUtilTest</code> (We did some changes to <code> core/test/nexj/core/util</code> to practice with it) Or we can run the ant target for test: <code> ant -f build_JUnitTest.xml test </code>*7- Bugs after implementation at NexJ : Working with remote repository; getting tip and log from remote repository is not as simple as moving to local repo and get all the information we need. challenges]]
