From ac921e7f9d54acd60f401dfd91d35f2395b87fdf Mon Sep 17 00:00:00 2001
From: DT Netsolution GmbH <daniel.schwager@dtnet.de>
Date: Fri, 27 Jan 2012 10:08:07 +0100
Subject: [PATCH] init

---
 doc/FeatureList.txt    | 18 ++++++++++++++++++
 doc/README-builder.txt | 35 ++++++++++++++++++++++++-----------
 2 files changed, 42 insertions(+), 11 deletions(-)
 create mode 100644 doc/FeatureList.txt

diff --git a/doc/FeatureList.txt b/doc/FeatureList.txt
new file mode 100644
index 0000000..a9645f5
--- /dev/null
+++ b/doc/FeatureList.txt
@@ -0,0 +1,18 @@
+- Fri 27.01.2012 09:44, dschwager
+  - Add maven for handling all archives 
+    opsi-archive: Storing all generated opsi-packets		($OPSI_REPOS_BASE_DIR)
+      dist-private: archive for all not public installer/MSI files  ($DIST_PRIVATE_REPOS)
+
+    Advantage: maven supports all kind of fileaccess (http, sftp, webdatev, smb, ...)
+    and we have to to code the up/downloading from the artifacts.
+
+  - Add integration to jenkins (An extendable open source continuous integration server)
+    http://jenkins-ci.org/ (Old: http://hudson-ci.org/, http://java.net/projects/hudson/)
+ 	- a opsi-hudson.sh will be called as a meta builder. This will trigger the normale opsi-builder.sh
+
+  - autoamtially tagging GIT tree, if a new "release" (OPSI_STATUS==release) was created
+    - opsi-builder.cfg:
+         OPSI_STATUS=[release|beta|integration]  - tells about the build state
+	 
+    should be done. 
+  
diff --git a/doc/README-builder.txt b/doc/README-builder.txt
index 2b2046d..48f8451 100644
--- a/doc/README-builder.txt
+++ b/doc/README-builder.txt
@@ -5,25 +5,38 @@
 #    check the sample build_local.cfg located inside the itwatch project
 ##############################
 
-# requirements
+# requirements for RHEL/Centos
      yum install plowshare
      yum install ImageMagick
      yum install git
 
+
+
 # Define your local, private, individual, not-project dependent  build setup
-# in the file ~/.builder.cfg OR by using the environment variable BUILD_LOCAL_CFG
+# in the file ~/.opsi-builder.cfg OR by using the environment variable OPSI_BUILDER
 # pointing the the configuration.  
-#    export BUILD_LOCAL_CFG=/home/dschwager/work/itwatch/build_local.cfg 
-# If no files are availble, the default values will be use.
+#    export OPSI_BUILDER=/home/dschwager/work/opsi-builder.cfg
+# If no files are availble, the default values will be use 
+# from <opsi-builder-home>/conf/opsi-builder.cfg 
 
-# Start build
-  builder.sh <path-to-the-project>
-  builder.sh /home/dschwager/work/itwatch
+  cp <opsi-builder-home>/conf/opsi-builder.cfg $HOME/.opsi-builder.cfg
+  vi $HOME/.opsi-builder.cfg
+     # may you will change some locations
 
-  # Force downloading vendor files 
-  DIST_FORCE_DOWNLOAD=1 builder.sh /home/dschwager/work/itwatch
+# May you will add opsi-builder.sh to your PATH
+  export PATH=$HOME/work/devtools/bin:$PATH
+
+# Start building
+  opsi-builder.sh <path-to-the-project>
+
+  cd <path-to-the-project> ;  opsi-builder.sh
+
+  You can overwrite all variables in opsi-builder.cfg by command, e.g. by
+    # Force downloading vendor files 
+    DIST_FORCE_DOWNLOAD=1 builder.sh /home/dschwager/work/itwatch
+
+      # Force upload independent of existing OPSI-Package in repository
+    OPSI_REPOS_FORCE_UPLOAD=1 builder.sh /home/dschwager/work/itwatch
 
-  # Force upload independent of existing OPSI-Package in repository
-  OPSI_REPOS_FORCE_UPLOAD=1 builder.sh /home/dschwager/work/itwatch