Re: cvs commit: gump/project avalon-excalibur.xml
On Wednesday 03 March 2004 23:23, Stefan Bodewig wrote: Niclas, I assume you are not subscribed to [EMAIL PROTECTED] so I keep you CCed. Correct. On Wed, 3 Mar 2004, Niclas Hedhman [EMAIL PROTECTED] wrote: What _we_ (as in Avalon) should do is getting our shit together and unify all the divergent build organizations, if nothing else to simplify Gump builds. I'm not sure. Avalon is a complex beast and so it doesn't come as a surprise that it is difficult to describe. It doesn't need to be, but too many chef's has been cooking this soup. A unified build system would save us all a lot of white hair. How much of Avalon is using Ant to build and how much uses Maven? By now, I think all is built with Maven. Another thing to consider is that Gump descriptors for the various parts of Avalon are scattered into different modules. Yes, I have noticed that. -- +-//---+ | http://www.bali.ac | | http://niclas.hedhman.org | +--//--+ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: gump/python/gump engine.py
ajack 2004/03/03 12:32:14
Modified:python/gump engine.py
Log:
1) More formatting for 'results on other servers'.
2) Exclude gumpy.lock and gumpy.log
3) Tweaks to gumpy.py (i.e. add --check)
Revision ChangesPath
1.72 +10 -5 gump/python/gump/engine.py
Index: engine.py
===
RCS file: /home/cvs/gump/python/gump/engine.py,v
retrieving revision 1.71
retrieving revision 1.72
diff -u -r1.71 -r1.72
--- engine.py 3 Mar 2004 01:02:25 - 1.71
+++ engine.py 3 Mar 2004 20:32:14 - 1.72
@@ -762,17 +762,20 @@
def checkModules(self,run):
# Check all the modules
-for module in run.getGumpSet().getModules():
+list=run.getGumpSet().getModules()
+moduleCount=len(list)
+moduleNo=1
+for module in list:
+
+log.info(' -- Module: #[' + `moduleNo` + '] of [' + `moduleCount` +
'] : ' + module.getName())
+
module.changeState(STATE_SUCCESS)
+moduleNo+=1
def checkProjects(self,run):
list=run.getGumpSet().getProjects()
# Check all projects
-log.debug('Total Project CheckList:');
-for p in list:
-log.debug(' To Check : ' + p.name)
-
projectCount=len(list)
projectNo=1
for project in list:
@@ -788,6 +791,8 @@
if not project.okToPerformWork():
log.warn('Failed to check project #[' + `projectNo` + '] [' +
project.getName() + '], state:' \
+ project.getStateDescription())
+
+projectNo+=1
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Developing Gump (in Python)
As we get more folks tinkering with Gump Python code (and I love how Stefan's first foray find standard Python things that I've missed) it is time to mature the codebase [comments/structuring], and start some development documentation. I started to create a development tab for this topic in the site xdocs, but I figured that might be a bit too formal I wanted to convey as much information as possible w/ the minimum of hassle. Also, we can all contribute to the wiki it get's updated more frequently. http://wiki.apache.org/gump/GumpDevelopment Let me know what things you'd like to see in here, either by adding questions/starting sections, or replying to this mail. regards, Adam -- Experience the Unwired Enterprise: http://www.sybase.com/unwiredenterprise Try Sybase: http://www.try.sybase.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Developing Gump (in Python)
Adam R. B. Jack wrote: As we get more folks tinkering with Gump Python code (and I love how Stefan's first foray find standard Python things that I've missed) it is time to mature the codebase [comments/structuring], and start some development documentation. I started to create a development tab for this topic in the site xdocs, but I figured that might be a bit too formal I wanted to convey as much information as possible w/ the minimum of hassle. Also, we can all contribute to the wiki it get's updated more frequently. http://wiki.apache.org/gump/GumpDevelopment Let me know what things you'd like to see in here, either by adding questions/starting sections, or replying to this mail. questions I don't know how to answer but I will need answered pretty soon: - what do I need installed on the machine in order to run gump - dummy step-by-step instructions on how to see a gump hello world - how to add stuff to my local gump installation step by step - how to fine tune it/configure it - what's left to be done, what's in the queue, what'd be cool to have thanks -- Stefano. smime.p7s Description: S/MIME Cryptographic Signature
Re: #Servers
Adam, Just a quick note. Saw httpunit fail on a prereq. I wrote the java version of LocalCheck (which checks if the downloaded prereqs are al present), is there a replacement for this already ? It is very usefull when setting up gump :) mvgr, Martin On Thu, 2004-03-04 at 00:32, Adam R. B. Jack wrote: I don't think I really have the cause to be as happy with this as I am: http://gump.try.sybase.com/httpunit/httpunit.html#Servers ... but it really tickles me. It isn't important, it isn't earth shaking, and most users will probably overlook it care less. Perhaps, for those reasons alone, I like that it exists. I need to make the presentation prettier, and add information (like time of last builds, sequence in state, etc) but it is a start. Each Gump reads the last results.xml of the others (if it exists) and hence knows the 'latest news' per module/project from the other Gumps. (I suspect, more than anything, it'll help Gump admins identify an issue in one servers environment.) Our public Gumps are starting to talking to each other. Perhaps this is the first small step in them forming their own community... ;-) regards, Adam Some reference: http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]msgId=1332722 http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]msgId=1185988 -- Experience the Unwired Enterprise: http://www.sybase.com/unwiredenterprise Try Sybase: http://www.try.sybase.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Mvgr, Martin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
LocalCheck (was Re: #Servers)
Martin, Just a quick note. Saw httpunit fail on a prereq. I wrote the java version of LocalCheck (which checks if the downloaded prereqs are al present), is there a replacement for this already ? It is very usefull when setting up gump :) Hmm, I don't think I ever knew of LocalCheck (until I just did a search) and I really could have used it back when I suffered trying to manually trim my descriptors and install packages for some local Gumps. I did gen after gen after gen, much to my misery... There are far more Gumpy scripts, heck -- even a GUI that needs some love -- that do lots of stuff. If one doesn't exist for what you say, one could be written without much issue, I feel. Let me think on this one overnight, and do a search in the morning, I fear that if I answered it now I'd miss the full answer. BTW: Would you be game to add this feature, if required? I agree folks need as much help as possible with shrinking profiles down to a bear minimum. regards, Adam - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (GUMP-19) Support encoding of international characters in nag mail headers
The following comment has been added to this issue: Author: Stefan Bodewig Created: Wed, 3 Mar 2004 8:27 AM Body: I was sure that something as common as MIME encoding must have been done by somebody - and it turns out the email module offers everything we need. I've committed a change that should turn Ceki's name into an accepted header part, but right now iso-8859-1 is hardcoded (bad) and it looks fairly incomplete to me. It seems the email module has more to offer, in particular we should be wrapping the body into a MIMEText object to get it properly escaped as well (for example if author names get visible in the output). - View this comment: http://nagoya.apache.org/jira/secure/ViewIssue.jspa?key=GUMP-19page=comments#action_20950 - View the issue: http://nagoya.apache.org/jira/secure/ViewIssue.jspa?key=GUMP-19 Here is an overview of the issue: - Key: GUMP-19 Summary: Support encoding of international characters in nag mail headers Type: Bug Status: Unassigned Priority: Major Project: Gump Components: Python Versions: unspecified Assignee: Reporter: Stefan Bodewig Created: Wed, 3 Mar 2004 12:32 AM Updated: Wed, 3 Mar 2004 8:27 AM Description: As wittnessed by the failing nag mails to log4j. Escaping of non-ASCII characters is well defined, sounds like a rather simple fix that might make a good candidate fix for somebody with a very low working knowledge of Python. Read, I'll look into it unless anybody beats me. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://nagoya.apache.org/jira/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Gump Wiki] New: GumpDevelopment
Date: 2004-03-03T13:39:58
Editor: AdamJack [EMAIL PROTECTED]
Wiki: Gump Wiki
Page: GumpDevelopment
URL: http://wiki.apache.org/gump/GumpDevelopment
First whack
New Page:
= Gump Development =
Gump development is primarily in Python, see GumpPython.
Gump use Python 2.2, not 2.3, which means a set of features are not available.
= Debugging =
Gump uses the standard Python 'logging' package (bundled in 2.3) but has a copy of it
[under python/] for 2.2. Typically the command line options of ''--debug'' and
''--verbose'' turn this on. Gump code current uses a single log instance (not one per
package/module).
Write to the log using log.debug( )
A very useful feature in exception cases is the following, the exc_info=1 (there is no
True in Pythong 2.2) logs a stack trace. The details object is often informative also.
try:
...
except Exception, details:
log.error('Problems problems...' + str(details), \
exc_info=1)
= Testing =
Unit tests (not yet converted to the real pyunit, a knock off but similar) are run
using:
python gump/test/pyunit.py
One can run a single test (or set of tests) by passing a wildcarded (filename-like not
regexp) expression. e.g. *Nag for all nag tests. This matches the method (test) name,
not test suite name.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[PATCH] please update logging/build.xml for the sake of gump !!!
Hi,
The gump build of jakarta-commons/logging is failing. [1]
I have attached a patch for the build.xml [2]
Thanks in advance for submitting it quickly, so that it is OK in the
next Gump run.
Antoine
Footnotes :
[1] http://lsd.student.utwente.nl/gump/jakarta-commons/commons-logging.html
[2] http://cvs.apache.org/viewcvs.cgi/jakarta-commons/logging/build.xml
Index: build.xml
===
RCS file: /home/cvspublic/jakarta-commons/logging/build.xml,v
retrieving revision 1.42
diff -u -r1.42 build.xml
--- build.xml 2 Mar 2004 21:02:51 - 1.42
+++ build.xml 3 Mar 2004 13:22:27 -
@@ -418,8 +418,6 @@
todir=${dist.home}/
copy file=RELEASE-NOTES.txt
todir=${dist.home}/
-copy file=usersguide.html
- todir=${dist.home}/
copy file=${build.home}/commons-${component.name}.jar
tofile=${dist.home}/commons-${component.name}.jar /
copy file=${build.home}/commons-${component.name}-api.jar
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
