Java Project - Revision history

Kurpick at 12:14, 15 March 2012

2012-03-15T12:14:17Z

← Older revision		Revision as of 12:14, 15 March 2012
Line 17:		Line 17:
	== Advanced setup ==		== Advanced setup ==

-	* Continous Integration with Jenkins ( [~~https://wiki.jenkins-ci.org/display/JENKINS/Use+Jenkins] )~~	+	* Continous Integration with Jenkins ( [[Setting Up Continuous Integration]] )
-	**run the war Archive[~~https://wiki.jenkins-ci.org/display/JENKINS/Starting+and+Accessing+Jenkins~~] ~~or deploy it on your Glassfish or Tomcat server.~~	+
-	**Now you can access Jenkins via the Homepage (e.g. http://localhost:8080/jenkins) configure generall settings and create your first Job. In Jenkins a Job is a Softwareproject that should be build.	+
-	**Choose for your Job a Name and the "Free-Style" Type of the Job. After that step a new Job is created and you can configure this Job.	+
-	**For "Source-Code-Management" choose Subversion. The Repository URL is something like: sselab.de/lab2/private/svn/<SSELAB-Prjoject-Name>/trunk/.	+
-	**In the next two steps you have to configure when and how the Project should be compiled. For CI you should select "Poll SCM". If you want to compile your Sourcecode with Apache Ant, you can define the Ant targets and files under Build-Invoke Ant.	+
-	**You can define some additional Post-build Actions like: run JUnit, measure Code Quality with Sonar, write some Emails.	+
-	*Codemesurement with Sonar in Jenkins (general installation [http://docs.codehaus.org/display/SONAR/Install+Sonar] )	+
-	**To measure your code in Jenkins with Sonar you have to install Sonar [http://www.sonarsource.org/].	+
-	**After downloading your copy of Sonar, you can configure the basic sonar settings like the used DB-Server. Since the default settings meet our actual needs (and no external Database has to be configured) we can directly compile the war-Archive.	+
-	**Do so with executing the build-war file in /sonar-2.1.13.1/war/ of the downloaded ZIP-Archive. As the next step you have to deploy that WAR-File on your JEE-Server. (Be advised that Glassfish and JBoss is not officially supported!)[http://docs.codehaus.org/display/SONAR/Install+Sonar#InstallSonar-SupportedPlatforms]	+
-	**Now you can browse to your local Sonar installation (on e.g. http://localhost:8080/sonar).	+
-	**In the next step you have to install the Sonar Plugin in your Jenkins, configure the Plugin in the global Jenkins settings (http://localhost:8080/jenkins/configure/ ) and activate that plugin for your job in Jenkins.	+
-	**it might be neccessary for sonar to increase the available heapspace (see next section Improvements)	+
-	*Improvements	+
-	**increase available Heapspace for Jenkins and Sonar in Glassfish	+
-	**configure Sonar with an external Database like Postgres or MySQL to gain more speed during Code measurement	+
-	**secure Jenkins [https://wiki.jenkins-ci.org/display/JENKINS/Standard+Security+Setup] and Sonar with username/password access	+
-	**all processes started during a build of Jenkins are killed by Jenkins after the build, so be careful with starting anything that should run even after the build finishes [https://wiki.jenkins-ci.org/display/JENKINS/ProcessTreeKiller]	+

	== Send feedback to extend this scenario ==		== Send feedback to extend this scenario ==

	Please contact us if you have question concerning the usage of the services. We are also curious about new ideas for additional services and new usage scenarios. [https://sselab.de/lab1/user/messages/send/ Send us a message over the contact form] or [mailto:admin@sselab.de?subject=Scenario%20Java%20Project write us an email]		Please contact us if you have question concerning the usage of the services. We are also curious about new ideas for additional services and new usage scenarios. [https://sselab.de/lab1/user/messages/send/ Send us a message over the contact form] or [mailto:admin@sselab.de?subject=Scenario%20Java%20Project write us an email]

Rumpe at 11:46, 18 February 2012

2012-02-18T11:46:53Z

← Older revision		Revision as of 11:46, 18 February 2012
Line 1:		Line 1:
		+	Agile software development needs ever running integrated software. Tool support is essential. We provide the following services and are working on further ones, such as [[nightly build]] and [[automatic deployment of web systems]] that are developed. Coming soon.
		+
	== Services involved ==		== Services involved ==
	* [[Subversion]]		* [[Subversion]]
	* [[Trac]]		* [[Trac]]
		+	* [[Mailing list]]
	* [[Mediawiki-internal\|MediaWiki (internal)]]		* [[Mediawiki-internal\|MediaWiki (internal)]]
		+
		+	A number of additional services are available. Check out what you want to use, e.g. to generate code or tests.

	== Initial setup ==		== Initial setup ==

Robert: /* Advanced setup */

2012-02-10T09:51:39Z

Advanced setup

Robert: /* Advanced setup */

2012-02-03T09:05:44Z

Advanced setup

← Older revision		Revision as of 09:05, 3 February 2012
Line 16:		Line 16:
	**Now you can access Hudson via the Homepage (e.g. http://localhost:8080/hudson) configure generall settings and create your first Job. In Hudson a Job is a Softwareproject that should be build by Hudson.		**Now you can access Hudson via the Homepage (e.g. http://localhost:8080/hudson) configure generall settings and create your first Job. In Hudson a Job is a Softwareproject that should be build by Hudson.
	**Choose for your Job a Name and the "Free-Style" Type of the Job. After that step a new Job is created and you can configure this Job.		**Choose for your Job a Name and the "Free-Style" Type of the Job. After that step a new Job is created and you can configure this Job.
-	**For "Source-Code-Management" choose Subversion. The Repository URL is something like: ~~https://~~sselab.de/lab2/private/svn/<SSELAB-Prjoject-Name>/trunk/.	+	**For "Source-Code-Management" choose Subversion. The Repository URL is something like: sselab.de/lab2/private/svn/<SSELAB-Prjoject-Name>/trunk/.
	**In the next two steps you have to configure when and how the Project should be compiled. For CI you should select "Poll SCM". If you want to compile your Sourcecode with Apache Ant, you can define the Ant targets and files under Build-Invoke Ant.		**In the next two steps you have to configure when and how the Project should be compiled. For CI you should select "Poll SCM". If you want to compile your Sourcecode with Apache Ant, you can define the Ant targets and files under Build-Invoke Ant.
	**You can define some additional Post-build Actions like: run JUnit, measure Code Quality with Sonar, write some Emails.		**You can define some additional Post-build Actions like: run JUnit, measure Code Quality with Sonar, write some Emails.

Robert: /* Advanced setup */

2012-02-03T09:04:32Z

Advanced setup

← Older revision		Revision as of 09:04, 3 February 2012
Line 12:		Line 12:
	== Advanced setup ==		== Advanced setup ==

-	* Continous Integration with Hudson	+	* Continous Integration with Hudson (general installation [http://wiki.hudson-ci.org/display/HUDSON/Installing+Hudson] )
-	Download Hudson Web Archive from Hudson Homepage [http://hudson-ci.org/] and deploy it to your favorite Java Application Server (e.g. Glassfish).	+	**Download Hudson Web Archive from Hudson Homepage [http://hudson-ci.org/] and deploy it to your favorite Java Application Server (e.g. Glassfish).
-		+	**Now you can access Hudson via the Homepage (e.g. http://localhost:8080/hudson) configure generall settings and create your first Job. In Hudson a Job is a Softwareproject that should be build by Hudson.
-	Now you can configure your Hudson ~~via~~ the ~~Webpage~~:	+	**Choose for your Job a Name and the "Free-Style" Type of the Job. After that step a new Job is created and you can configure this Job.
-	you have to ~~point~~ to your local ~~JDK~~ installation	+	**For "Source-Code-Management" choose Subversion. The Repository URL is something like: https://sselab.de/lab2/private/svn/<SSELAB-Prjoject-Name>/trunk/.
		+	**In the next two steps you have to configure when and how the Project should be compiled. For CI you should select "Poll SCM". If you want to compile your Sourcecode with Apache Ant, you can define the Ant targets and files under Build-Invoke Ant.
		+	**You can define some additional Post-build Actions like: run JUnit, measure Code Quality with Sonar, write some Emails.
		+	*Codemesurement with Sonar in Hudson (general installation [http://docs.codehaus.org/display/SONAR/Install+Sonar] )
		+	**To measure your code in Hudson with Sonar you have to install Sonar [http://www.sonarsource.org/].
		+	**After downloading your copy of Sonar, you have to compile it. Do so with executing the build-war file in /sonar-2.1.13.1/war/ of the downloaded ZIP-Archive. As the next step you have to deploy that WAR-File on your JEE-Server.
		+	**Now you can browse to your local Sonar installation (on e.g. http://localhost:8080/sonar).
		+	**In the next step you have to install the Sonar Plugin in your Hudson, configure the Plugin in the global hudson settings (http://localhost:8080/hudson/configure/ ) and activate that plugin for your job in Hudson.
		+	**it might be neccessary for sonar to increase the available heapspace (see next section Improvements)
		+	*Improvements
		+	**increase available Heapspace for Hudson and Sonar in Glassfish
		+	**configure Sonar with an external Database like Postgres or MySQL to gain more speed during Code measurement
		+	**secure Hudson and Sonar with username/password access

	== Send feedback to extend this scenario ==		== Send feedback to extend this scenario ==

	Please contact us if you have question concerning the usage of the services. We are also curious about new ideas for additional services and new usage scenarios. [https://sselab.de/lab1/user/messages/send/ Send us a message over the contact form] or [mailto:admin@sselab.de?subject=Scenario%20Java%20Project write us an email]		Please contact us if you have question concerning the usage of the services. We are also curious about new ideas for additional services and new usage scenarios. [https://sselab.de/lab1/user/messages/send/ Send us a message over the contact form] or [mailto:admin@sselab.de?subject=Scenario%20Java%20Project write us an email]

Robert: /* Advanced setup */

2012-02-02T13:18:58Z

Advanced setup

← Older revision		Revision as of 13:18, 2 February 2012
Line 13:		Line 13:

	* Continous Integration with Hudson		* Continous Integration with Hudson
		+	Download Hudson Web Archive from Hudson Homepage [http://hudson-ci.org/] and deploy it to your favorite Java Application Server (e.g. Glassfish).
		+
		+	Now you can configure your Hudson via the Webpage:
		+	you have to point to your local JDK installation

	== Send feedback to extend this scenario ==		== Send feedback to extend this scenario ==

	Please contact us if you have question concerning the usage of the services. We are also curious about new ideas for additional services and new usage scenarios. [https://sselab.de/lab1/user/messages/send/ Send us a message over the contact form] or [mailto:admin@sselab.de?subject=Scenario%20Java%20Project write us an email]		Please contact us if you have question concerning the usage of the services. We are also curious about new ideas for additional services and new usage scenarios. [https://sselab.de/lab1/user/messages/send/ Send us a message over the contact form] or [mailto:admin@sselab.de?subject=Scenario%20Java%20Project write us an email]

Kurpick: /* Initial setup */

2012-02-01T07:34:36Z

Initial setup

← Older revision		Revision as of 07:34, 1 February 2012
Line 10:		Line 10:
	** Create milestones for implementation of new features and releases of your software		** Create milestones for implementation of new features and releases of your software
	* Calculate various statistics of your implementation and publish it in the internal wiki for your project manager with the wikibot (advanced)		* Calculate various statistics of your implementation and publish it in the internal wiki for your project manager with the wikibot (advanced)
		+	== Advanced setup ==
		+
		+	* Continous Integration with Hudson

	== Send feedback to extend this scenario ==		== Send feedback to extend this scenario ==

	Please contact us if you have question concerning the usage of the services. We are also curious about new ideas for additional services and new usage scenarios. [https://sselab.de/lab1/user/messages/send/ Send us a message over the contact form] or [mailto:admin@sselab.de?subject=Scenario%20Java%20Project write us an email]		Please contact us if you have question concerning the usage of the services. We are also curious about new ideas for additional services and new usage scenarios. [https://sselab.de/lab1/user/messages/send/ Send us a message over the contact form] or [mailto:admin@sselab.de?subject=Scenario%20Java%20Project write us an email]

Kurpick at 11:58, 31 January 2012

2012-01-31T11:58:53Z

← Older revision		Revision as of 11:58, 31 January 2012
Line 13:		Line 13:
	== Send feedback to extend this scenario ==		== Send feedback to extend this scenario ==

-	Please contact us if you have question concerning the usage of the services. We are also ~~exited~~ about new ideas of additional services and new usage scenarios. [[]]	+	Please contact us if you have question concerning the usage of the services. We are also curious about new ideas for additional services and new usage scenarios. [https://sselab.de/lab1/user/messages/send/ Send us a message over the contact form] or [mailto:admin@sselab.de?subject=Scenario%20Java%20Project write us an email]

Kurpick at 10:28, 31 January 2012

2012-01-31T10:28:40Z

← Older revision		Revision as of 10:28, 31 January 2012
Line 10:		Line 10:
	** Create milestones for implementation of new features and releases of your software		** Create milestones for implementation of new features and releases of your software
	* Calculate various statistics of your implementation and publish it in the internal wiki for your project manager with the wikibot (advanced)		* Calculate various statistics of your implementation and publish it in the internal wiki for your project manager with the wikibot (advanced)
		+
		+	== Send feedback to extend this scenario ==
		+
		+	Please contact us if you have question concerning the usage of the services. We are also exited about new ideas of additional services and new usage scenarios. [[]]

Kurpick: /* Initial setup */

2012-01-31T10:26:03Z

Initial setup

← Older revision		Revision as of 10:26, 31 January 2012
Line 6:		Line 6:
	== Initial setup ==		== Initial setup ==

-	* Download the following template and commit it into your subversion repository
	* Use the trac to plan your software project		* Use the trac to plan your software project
	** Break your problem into several subproblems and create a ticket for each one of it		** Break your problem into several subproblems and create a ticket for each one of it
	** Create milestones for implementation of new features and releases of your software		** Create milestones for implementation of new features and releases of your software
	* Calculate various statistics of your implementation and publish it in the internal wiki for your project manager with the wikibot (advanced)		* Calculate various statistics of your implementation and publish it in the internal wiki for your project manager with the wikibot (advanced)

← Older revision		Revision as of 09:51, 10 February 2012
Line 12:		Line 12:
	== Advanced setup ==		== Advanced setup ==

-	* Continous Integration with ~~Hudson~~ (~~general installation~~ [~~http~~://wiki.~~hudson~~-ci.org/display/~~HUDSON~~/~~Installing~~+~~Hudson~~] )	+	* Continous Integration with Jenkins ( [https://wiki.jenkins-ci.org/display/JENKINS/Use+Jenkins] )
-	**~~Download Hudson Web~~ Archive ~~from Hudson Homepage~~ [~~http~~://~~hudson~~-ci.org/] and deploy it to your ~~favorite Java Application Server (e.g.~~ Glassfish).	+	**run the war Archive[https://wiki.jenkins-ci.org/display/JENKINS/Starting+and+Accessing+Jenkins] or deploy it on your Glassfish or Tomcat server.
-	**Now you can access ~~Hudson~~ via the Homepage (e.g. http://localhost:8080/~~hudson~~) configure generall settings and create your first Job. In ~~Hudson~~ a Job is a Softwareproject that should be build ~~by Hudson~~.	+	**Now you can access Jenkins via the Homepage (e.g. http://localhost:8080/jenkins) configure generall settings and create your first Job. In Jenkins a Job is a Softwareproject that should be build.
	**Choose for your Job a Name and the "Free-Style" Type of the Job. After that step a new Job is created and you can configure this Job.		**Choose for your Job a Name and the "Free-Style" Type of the Job. After that step a new Job is created and you can configure this Job.
	**For "Source-Code-Management" choose Subversion. The Repository URL is something like: sselab.de/lab2/private/svn/<SSELAB-Prjoject-Name>/trunk/.		**For "Source-Code-Management" choose Subversion. The Repository URL is something like: sselab.de/lab2/private/svn/<SSELAB-Prjoject-Name>/trunk/.
	**In the next two steps you have to configure when and how the Project should be compiled. For CI you should select "Poll SCM". If you want to compile your Sourcecode with Apache Ant, you can define the Ant targets and files under Build-Invoke Ant.		**In the next two steps you have to configure when and how the Project should be compiled. For CI you should select "Poll SCM". If you want to compile your Sourcecode with Apache Ant, you can define the Ant targets and files under Build-Invoke Ant.
	**You can define some additional Post-build Actions like: run JUnit, measure Code Quality with Sonar, write some Emails.		**You can define some additional Post-build Actions like: run JUnit, measure Code Quality with Sonar, write some Emails.
-	*Codemesurement with Sonar in ~~Hudson~~ (general installation [http://docs.codehaus.org/display/SONAR/Install+Sonar] )	+	*Codemesurement with Sonar in Jenkins (general installation [http://docs.codehaus.org/display/SONAR/Install+Sonar] )
-	**To measure your code in ~~Hudson~~ with Sonar you have to install Sonar [http://www.sonarsource.org/].	+	**To measure your code in Jenkins with Sonar you have to install Sonar [http://www.sonarsource.org/].
-	**After downloading your copy of Sonar, you ~~have~~ to compile it. Do so with executing the build-war file in /sonar-2.1.13.1/war/ of the downloaded ZIP-Archive. As the next step you have to deploy that WAR-File on your JEE-Server.	+	**After downloading your copy of Sonar, you can configure the basic sonar settings like the used DB-Server. Since the default settings meet our actual needs (and no external Database has to be configured) we can directly compile the war-Archive.
		+	**Do so with executing the build-war file in /sonar-2.1.13.1/war/ of the downloaded ZIP-Archive. As the next step you have to deploy that WAR-File on your JEE-Server. (Be advised that Glassfish and JBoss is not officially supported!)[http://docs.codehaus.org/display/SONAR/Install+Sonar#InstallSonar-SupportedPlatforms]
	**Now you can browse to your local Sonar installation (on e.g. http://localhost:8080/sonar).		**Now you can browse to your local Sonar installation (on e.g. http://localhost:8080/sonar).
-	**In the next step you have to install the Sonar Plugin in your ~~Hudson~~, configure the Plugin in the global ~~hudson~~ settings (http://localhost:8080/~~hudson~~/configure/ ) and activate that plugin for your job in ~~Hudson~~.	+	**In the next step you have to install the Sonar Plugin in your Jenkins, configure the Plugin in the global Jenkins settings (http://localhost:8080/jenkins/configure/ ) and activate that plugin for your job in Jenkins.
	**it might be neccessary for sonar to increase the available heapspace (see next section Improvements)		**it might be neccessary for sonar to increase the available heapspace (see next section Improvements)
	*Improvements		*Improvements
-	**increase available Heapspace for ~~Hudson~~ and Sonar in Glassfish	+	**increase available Heapspace for Jenkins and Sonar in Glassfish
	**configure Sonar with an external Database like Postgres or MySQL to gain more speed during Code measurement		**configure Sonar with an external Database like Postgres or MySQL to gain more speed during Code measurement
-	**secure ~~Hudson~~ and Sonar with username/password access	+	**secure Jenkins [https://wiki.jenkins-ci.org/display/JENKINS/Standard+Security+Setup] and Sonar with username/password access
		+	**all processes started during a build of Jenkins are killed by Jenkins after the build, so be careful with starting anything that should run even after the build finishes [https://wiki.jenkins-ci.org/display/JENKINS/ProcessTreeKiller]

	== Send feedback to extend this scenario ==		== Send feedback to extend this scenario ==

	Please contact us if you have question concerning the usage of the services. We are also curious about new ideas for additional services and new usage scenarios. [https://sselab.de/lab1/user/messages/send/ Send us a message over the contact form] or [mailto:admin@sselab.de?subject=Scenario%20Java%20Project write us an email]		Please contact us if you have question concerning the usage of the services. We are also curious about new ideas for additional services and new usage scenarios. [https://sselab.de/lab1/user/messages/send/ Send us a message over the contact form] or [mailto:admin@sselab.de?subject=Scenario%20Java%20Project write us an email]