Re: User id that runs Gump on moof (and LSD...)
Adam R. B. Jack wrote: Since I have LSD running under 'ajack' as are gump.try.sybase.com and gump.dotnot.org, I think we need somebody else's id to run the Apache Python Gump on moof. This is especially important with me going away next week. Seems my orig email didn't make it to the list... what we could also do is create a 'gump' user, and give multiple people the password. Alternatively, we don't give out the password, but add multiple people's keys to the authorized_keys file. The former has the advantage that you could 'su gump', the latter is probably a little safer. I don't like the single point of failure we have now at all. As far as lsd goes, I'm familiar with the setup, and I'm root so I can 'su ajack' all I want. The same goes for Stefano on moof, I think. I'm also supposed to be catching a train in five mins so I don't have time to change anything over there right now. -- cheers, - Leo Simons --- Weblog -- http://leosimons.com/ IoC Component Glue -- http://jicarilla.org/ Articles Opinions -- http://articles.leosimons.com/ --- We started off trying to set up a small anarchist community, but people wouldn't obey the rules. -- Alan Bennett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: gump/project jakarta-jmeter.xml
sebb2004/03/20 03:20:01 Modified:project jakarta-jmeter.xml Log: Changing version to jmeter.version in line with build.xml Revision ChangesPath 1.86 +9 -9 gump/project/jakarta-jmeter.xml Index: jakarta-jmeter.xml === RCS file: /home/cvs/gump/project/jakarta-jmeter.xml,v retrieving revision 1.85 retrieving revision 1.86 diff -u -r1.85 -r1.86 --- jakarta-jmeter.xml19 Mar 2004 13:23:53 - 1.85 +++ jakarta-jmeter.xml20 Mar 2004 11:20:01 - 1.86 @@ -28,7 +28,7 @@ packageorg.apache.jmeter/package ant target=gump-compile - property name=version value=@@DATE@@/ + property name=jmeter.version value=@@DATE@@/ property name=gump.run value=true/ !-- The version of this file -- property name=version.projectfile value=$Revision$/ @@ -90,7 +90,7 @@ packageorg.apache.jmeter/package ant target=gump-build - property name=version value=@@DATE@@/ + property name=jmeter.version value=@@DATE@@/ property name=gump.run value=true/ !-- The version of this file -- property name=version.projectfile value=$Revision$/ @@ -160,7 +160,7 @@ project name=jakarta-jmeter-test packageorg.apache.jmeter/package ant target=gump-test - property name=version value=@@DATE@@/ + property name=jmeter.version value=@@DATE@@/ property name=gump.run value=true/ !-- The version of this file -- property name=version.projectfile value=$Revision$/ @@ -221,7 +221,7 @@ project name=jakarta-jmeter-javadoc packageorg.apache.jmeter/package ant target=gump-javadoc - property name=version value=@@DATE@@/ + property name=jmeter.version value=@@DATE@@/ property name=gump.run value=true/ !-- The version of this file -- property name=version.projectfile value=$Revision$/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: gump/project jakarta-jmeter.xml
sebb2004/03/20 06:01:06 Modified:project jakarta-jmeter.xml Log: Add mkdirs to ensure work dirs are not dropped Revision ChangesPath 1.88 +34 -9 gump/project/jakarta-jmeter.xml Index: jakarta-jmeter.xml === RCS file: /home/cvs/gump/project/jakarta-jmeter.xml,v retrieving revision 1.87 retrieving revision 1.88 diff -u -r1.87 -r1.88 --- jakarta-jmeter.xml20 Mar 2004 11:52:57 - 1.87 +++ jakarta-jmeter.xml20 Mar 2004 14:01:06 - 1.88 @@ -51,6 +51,19 @@ depend property=jdom.jar project=jdom/ depend property=js.jar project=rhino/ depend property=soap.jar project=ws-soap/ + + !-- Ensure work directories don't get dropped from classpath -- + mkdir dir=build/core/ + mkdir dir=build/htmlparser/ + mkdir dir=build/jorphan/ + + !-- Allow http to build: -- + mkdir dir=build/components/ + + !-- Allow Monitor to build -- + mkdir dir=build/protocol/http/ + mkdir dir=build/monitor/model/ + /ant depend project=ant / @@ -97,6 +110,18 @@ !-- The version of this file -- property name=version.projectfile value=$Revision$/ property name=date.projectfile value=$Date$/ + + !-- Ensure work directories don't get dropped from classpath -- + mkdir dir=build/core/ + mkdir dir=build/htmlparser/ + mkdir dir=build/jorphan/ + + !-- Allow http to build: -- + mkdir dir=build/components/ + + !-- Allow Monitor to build -- + mkdir dir=build/protocol/http/ + mkdir dir=build/monitor/model/ /ant depend project=ant / - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: User id that runs Gump on moof (and LSD...)
what we could also do is create a 'gump' user, and give multiple people the password. Alternatively, we don't give out the password, but add multiple people's keys to the authorized_keys file. I've always frowned on shared user ids (assuming they were excuses for not getting group permissions right) but that isn't the case here, we are working around an SVN bug. [If the bug really does only have a life expectancy of a few weeks, the rollout might take longer.] As such +1 to this idea. So long as gump is a member of the gump group, that we all have ids within, then it can be easily obsoleted once unecessary. I don't like the single point of failure we have now at all. 100% agreed. Anybody know how to do a share cronjob any other way? I'm also supposed to be catching a train in five mins so I don't have time to change anything over there right now. I agree, it'd be daft to do a quick transition without everybody around. That said, what I am really hoping for is: 1) Grant folks access to live/working Gumps so they can do 'quick runs' (like python gump/debug.py xmlunit --debug --quick, to test properties, etc.) 2) Grant folks access to live/working Gumps to spread the knowledge, and get more input/opinions on how to install this nicely. 3) Get documentation for the installs into the wiki, and that documentation come from somebody unfamiliar with the config, so they explain it better. I hope that we can still get these. regards Adam - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: User id that runs Gump on moof (and LSD...)
I am also +1 I am also +1 on the idea of the gump user. Impersonal users are often used by organizations setting up automated jobs. I have seen impersonal users used for : - running application servers in a bank, - running builds in a large software house, The impersonal user is a good medium to make sure that an application will go on running, whoever takes care of managing it, and whatever the vagaries of personal turnover in open source organizations or in for-profit companies. Adam R. B. Jack wrote: what we could also do is create a 'gump' user, and give multiple people the password. Alternatively, we don't give out the password, but add multiple people's keys to the authorized_keys file. I've always frowned on shared user ids (assuming they were excuses for not getting group permissions right) but that isn't the case here, we are working around an SVN bug. [If the bug really does only have a life expectancy of a few weeks, the rollout might take longer.] As such +1 to this idea. So long as gump is a member of the gump group, that we all have ids within, then it can be easily obsoleted once unecessary. I don't like the single point of failure we have now at all. 100% agreed. Anybody know how to do a share cronjob any other way? No. I do not know how to share a cronjob without an impersonal user. Also, one can only control (kill) the processes of one's own UNIX user. I'm also supposed to be catching a train in five mins so I don't have time to change anything over there right now. I agree, it'd be daft to do a quick transition without everybody around. That said, what I am really hoping for is: 1) Grant folks access to live/working Gumps so they can do 'quick runs' (like python gump/debug.py xmlunit --debug --quick, to test properties, etc.) 2) Grant folks access to live/working Gumps to spread the knowledge, and get more input/opinions on how to install this nicely. 3) Get documentation for the installs into the wiki, and that documentation come from somebody unfamiliar with the config, so they explain it better. I hope that we can still get these. regards Adam5o Cheers, Antoine - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: gump/profile minimal-profile.xml
sebb2004/03/20 09:03:46 Modified:profile minimal-profile.xml Log: Remove Werken as there is no corresponding respository entry Revision ChangesPath 1.6 +1 -1 gump/profile/minimal-profile.xml Index: minimal-profile.xml === RCS file: /home/cvs/gump/profile/minimal-profile.xml,v retrieving revision 1.5 retrieving revision 1.6 diff -u -r1.5 -r1.6 --- minimal-profile.xml 27 Feb 2004 08:56:57 - 1.5 +++ minimal-profile.xml 20 Mar 2004 17:03:46 - 1.6 @@ -70,7 +70,7 @@ repository href=repository/mozilla.xml/ repository href=repository/tigris.xml/ repository href=repository/sourceforge.xml/ -repository href=repository/werken.xml/ +!--repository href=repository/werken.xml/-- repository href=repository/whichever.xml/ repository href=repository/xml.xml/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Gump Wiki] Updated: GumpScripts
Date: 2004-03-20T09:20:08 Editor: 80.176.146.62 Wiki: Gump Wiki Page: GumpScripts URL: http://wiki.apache.org/gump/GumpScripts Put examples on separate lines (lines with leading spaces seem to be merged) Change Log: -- @@ -19,6 +19,6 @@ e.g. - -w ../gump.xml jakarta-* + -w ../gump.xml jakarta-* [[BR]] -w ../gump.xml all --debug - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Gump Wiki] Updated: GumpPython
Date: 2004-03-20T09:42:51 Editor: 80.176.146.62 Wiki: Gump Wiki Page: GumpPython URL: http://wiki.apache.org/gump/GumpPython Does this gen.py exist? Fixed strong markup. Change Log: -- @@ -70,12 +70,12 @@ }}} Note: There are similar tools w/ similar command line arguments: - * check.py -- check a workspace - * gen.py -- check plus more - * update.py -- update project(s) from source control - * integrate.py -- does the works check/update/build/statistics/document/nag + * gump/check.py -- check a workspace + * gen.py -- check plus more '''*** does not exist - should this be gumpy.py ? ''' + * gump/update.py -- update project(s) from source control + * gump/integrate.py -- does the works check/update/build/statistics/document/nag -Note: The command line arguments accept a regular expression that resolves over project names strongNOT/strong module names. all is converted to the regular expression *. This is a new feature in Python Gump, and a mild divergence from traditional gump usage. When (say) updating a list of modules the utilities calculate the modules containing the requests projects, and hence translates for the user. +Note: The command line arguments accept a regular expression that resolves over project names '''NOT''' module names. all is converted to the regular expression *. This is a new feature in Python Gump, and a mild divergence from traditional gump usage. When (say) updating a list of modules the utilities calculate the modules containing the requests projects, and hence translates for the user. == Automating the integration process using integrate.py == @@ -136,17 +136,17 @@ For more details see gump/context.py -NOTE: The attempt here is to strongNOT polute the object model/strong with runtime information. +NOTE: The attempt here is to '''NOT polute the object model''' with runtime information. == 3) Statistics == A simple DBM database of statistics (per project name) is kept containing: - * Number of strongSuccessful/strong builds - * Number of strongFailed/strong builds - * Number of builds not attempted due to strongPrerequisite/strong failed builds. - * strongFirst date/strong of first successful build. - * strongLast date/strong of last (latest) successful build. + * Number of '''Successful''' builds + * Number of '''Failed''' builds + * Number of builds not attempted due to '''Prerequisite''' failed builds. + * '''First date''' of first successful build. + * '''Last date''' of last (latest) successful build. For more details see gump/statistics.py - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: gump/python/gump/model project.py workspace.py
ajack 2004/03/20 10:37:40
Modified:python/gump/model project.py workspace.py
Log:
Trying to make artifact ids from jar basenames (removing -@@DATE@@ and .jar)
Need to add ids manually.
Revision ChangesPath
1.68 +12 -2 gump/python/gump/model/project.py
Index: project.py
===
RCS file: /home/cvs/gump/python/gump/model/project.py,v
retrieving revision 1.67
retrieving revision 1.68
diff -u -r1.67 -r1.68
--- project.py19 Mar 2004 18:19:18 - 1.67
+++ project.py20 Mar 2004 18:37:40 - 1.68
@@ -420,8 +420,18 @@
for jar in self.getJars():
if not jar.hasId():
basename=os.path.basename(jar.getPath())
-self.addWarning('Jar [' + jar.getPath() + '] identifier set
to jar basename: [' + basename + ']')
-jar.setId(basename)
+newId=basename
+# Strip off .jar
+if newId.endswith('.jar'):
+newId=newId[:-4]
+# Strip off -@@DATE@@
+datePostfix='-' + str(default.date)
+if newId.endswith(datePostfix):
+reduction=-1 * len(datePostfix)
+newId=newId[:reduction]
+# Assign...
+self.addWarning('Jar [' + basename + '] identifier set to
jar basename: [' + newId + ']')
+jar.setId(newId)
# Grab all the work
for w in self.xml.work:
1.37 +1 -1 gump/python/gump/model/workspace.py
Index: workspace.py
===
RCS file: /home/cvs/gump/python/gump/model/workspace.py,v
retrieving revision 1.36
retrieving revision 1.37
diff -u -r1.36 -r1.37
--- workspace.py 19 Mar 2004 23:11:47 - 1.36
+++ workspace.py 20 Mar 2004 18:37:40 - 1.37
@@ -38,7 +38,7 @@
from gump.utils.listener import Listener, Event
#
-# :TODO: Need to createa GumpEnvironment to move these to..
+#
#
class Workspace(NamedModelObject, PropertyContainer, Statable, Resultable):
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: gump/project depot.xml
ajack 2004/03/20 11:14:28 Modified:project depot.xml Log: Renamed 'Ruper' to 'Update'. Revision ChangesPath 1.14 +12 -12gump/project/depot.xml Index: depot.xml === RCS file: /home/cvs/gump/project/depot.xml,v retrieving revision 1.13 retrieving revision 1.14 diff -u -r1.13 -r1.14 --- depot.xml 2 Mar 2004 16:28:37 - 1.13 +++ depot.xml 20 Mar 2004 19:14:28 - 1.14 @@ -71,13 +71,13 @@ /project -project name=depot-ruper fullname=Depot Ruper +project name=depot-update fullname=Depot Update -packageorg.apache.ruper/package +packageorg.apache.update/package !-- Work dirs to be included in classpath -- -work nested=ruper/target/classes/ -home nested=ruper/target/dist/ +work nested=update/target/classes/ +home nested=update/target/dist/ depend inherit=runtime project=ant/ depend project=depot-version/ @@ -85,9 +85,9 @@ depend project=commons-httpclient/ depend project=commons-vfs/ -jar name=jars/apache-depot-ruper-@@DATE@@.jar/ +jar name=jars/apache-depot-update-@@DATE@@.jar/ -ant basedir=ruper buildfile=build.xml target=gump vm=1.4 +ant basedir=update buildfile=build.xml target=gump vm=1.4 property name=ant.home project=ant reference=home / property name=DATE_STAMP value=@@DATE@@/ /ant @@ -98,19 +98,19 @@ /project -project name=depot-ruper-test fullname=Depot Ruper Test +project name=depot-update-test fullname=Depot Update Test -packageorg.apache.ruper.test/package +packageorg.apache.update.test/package !-- Work dirs to be included in classpath -- -work nested=ruper/target/unit/classes/ -home nested=ruper/dist/ +work nested=update/target/unit/classes/ +home nested=update/dist/ -depend project=depot-ruper inherit=all/ +depend project=depot-update inherit=all/ depend project=ant-testutil/ depend project=junit/ -ant basedir=ruper buildfile=build.xml target=test vm=1.4 +ant basedir=update buildfile=build.xml target=test vm=1.4 property name=ant.home project=ant reference=home / /ant - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
