Building and running?
So the README.txt is obviously out of date. What's the status on building and starting up a continuum server? -David
Re: distributed continuum
On Sep 24, 2006, at 11:41 PM, Jason van Zyl wrote: On 25 Sep 06, at 1:44 AM 25 Sep 06, Brett Porter wrote: Cool bananas. Welcome David! Yah, I know from David that's it's been working for quite a while so I figured let David and Kevan work on it in the trunk where it will get some visibility and help. I'm sure that lots of people are going to be interested in this feature. Coupled with build parallelization and some staged commit capabilities this will be quite an amazing new feature. Thanks for the welcome guys. Going to try and get myself familiar with trunk again. Last time I looked at it heavily was Oct, Nov, Dec. Just off the top of my head, I know there's been tons of work in security and the webwork stuff. Do you guys think it's unreasonable to try and put up an install of Continuum trunk to run a few projects? Is trunk basically functional at this point? -David On 25/09/2006, at 7:37 AM, Jason van Zyl wrote: Howdy, As we discussed some time ago, I was going to check in the distributed continuum once it built and it does with trunk. So I checked it in so that David Blevins can help me with some tests. David now has access as we agreed some time ago. Jason. Jason van Zyl [EMAIL PROTECTED] Jason van Zyl [EMAIL PROTECTED]
html export of projects
Figured I'd share this little bit of bash I hacked up to help in
upgrading continuum. Sucks down all the project defs so you can see
exactly how to re-setup everything.
--get_project_defs.sh--
#!/bin/bash
wget -O projects.html http://ci.gbuild.org/continuum/servlet/continuum
for n in $(egrep 'fid.*/id/' projects.html | perl -pe
's/.*href="|;jsession.*//g'); do
id=${n/*id\//}
wget -O $id.html $n
done
perl -i.bak -pe 's,http://[^<>]+/id/([0-9]+),$1.html,g' projects.html
# then just open projects.html
---
-David
Re: Non-public projects
Sure, was thinking more high-level. Last I knew 1.1 was torn up and at the beginning of a webwork (or something) conversion. I guess the better phrasing is what state is 1.1 in these days? -David On Apr 13, 2006, at 12:38 PM, Emmanuel Venisse wrote: 1.1 development is suspended until the release of 1.0.3 in few days. We don't have for the moment a release date for 1.1 Emmanuel David Blevins a écrit : Woohoo. So what's the status of 1.1 these days? -David On Apr 13, 2006, at 12:08 PM, Emmanuel Venisse wrote: Yes, it will be in 1.1. Emmanuel Carlos Sanchez a écrit : I think this is what it's planned for 1.1 by adding security through Acegi On 4/13/06, David Blevins <[EMAIL PROTECTED]> wrote: There is a new feature I need and I'd like to get feedback from the group on how it may be implemented. Don't know if I'll end up writing, but at least I'd like to get some discussion going for now. We at Geronimo desperately need to be able to setup a couple projects in continuum that aren't public -- they're tck related. So basically, we need some way to mark a project as viewable by only logged in individuals in a specific group. Having them listed on the main page with the other projects is ok, just clicking on anything there should require you to be properly authenticated and authorized to do so. This is a big new can of worms for Continuum, so what does everyone think? Good feature/bad feature? Any thought's on what'd be required to implement it? -David -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride
Re: Non-public projects
Woohoo. So what's the status of 1.1 these days? -David On Apr 13, 2006, at 12:08 PM, Emmanuel Venisse wrote: Yes, it will be in 1.1. Emmanuel Carlos Sanchez a écrit : I think this is what it's planned for 1.1 by adding security through Acegi On 4/13/06, David Blevins <[EMAIL PROTECTED]> wrote: There is a new feature I need and I'd like to get feedback from the group on how it may be implemented. Don't know if I'll end up writing, but at least I'd like to get some discussion going for now. We at Geronimo desperately need to be able to setup a couple projects in continuum that aren't public -- they're tck related. So basically, we need some way to mark a project as viewable by only logged in individuals in a specific group. Having them listed on the main page with the other projects is ok, just clicking on anything there should require you to be properly authenticated and authorized to do so. This is a big new can of worms for Continuum, so what does everyone think? Good feature/bad feature? Any thought's on what'd be required to implement it? -David -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride
Non-public projects
There is a new feature I need and I'd like to get feedback from the group on how it may be implemented. Don't know if I'll end up writing, but at least I'd like to get some discussion going for now. We at Geronimo desperately need to be able to setup a couple projects in continuum that aren't public -- they're tck related. So basically, we need some way to mark a project as viewable by only logged in individuals in a specific group. Having them listed on the main page with the other projects is ok, just clicking on anything there should require you to be properly authenticated and authorized to do so. This is a big new can of worms for Continuum, so what does everyone think? Good feature/bad feature? Any thought's on what'd be required to implement it? -David
Re: Creating a notifier for Confluence
On Apr 5, 2006, at 8:23 PM, David Blevins wrote: On Apr 5, 2006, at 7:29 AM, Emmanuel Venisse wrote: I think the best way it to create a wrapper on it like we do it for irc (with plexus-irc) and jabber (with plexus-jabber) and use use the wrapper in the notifier. But perhaps, it isn't necessary, i didn't look at swizzle. http://docs.codehaus.org/display/SWIZZLE/Swizzle+Confluence That just shows reading from a space, but you can add/update pages too. Here is some javadoc: http://swizzle.codehaus.org/swizzle-confluence/ -David
Re: Creating a notifier for Confluence
On Apr 5, 2006, at 7:29 AM, Emmanuel Venisse wrote: I think the best way it to create a wrapper on it like we do it for irc (with plexus-irc) and jabber (with plexus-jabber) and use use the wrapper in the notifier. But perhaps, it isn't necessary, i didn't look at swizzle. Done. Haven't hooked up a confluenza site yet, so the wiki will have to do. It's basically the client APIs for Confluence and Jira, so you can write apps to poke at either of them without having to hurtle that first "how do I talk to confluence" step. It always kind of bugged me that there was a standard API for Confluence, but no standard client -- you have to make your own. So I decided to suck down the API info and hacked a Perl script to create the related Java code. Here is some example code and it's related output: http://docs.codehaus.org/display/SWIZZLE/Swizzle+Confluence That just shows reading from a space, but you can add/update pages too. -David Emmanuel Mang Jun Lau a écrit : Great thanks :), I don't have to struggle with implementing it then. How do I use this with Continuum? _Mang Lau David Blevins <[EMAIL PROTECTED]> 04/05/2006 05:14 AM Please respond to continuum-dev@maven.apache.org To continuum-dev@maven.apache.org cc Subject Re: Creating a notifier for Confluence FYI, I have a library available for manipulating Confluence via XML-RPC http://cvs.codehaus.org/viewrep/swizzle/swizzle/swizzle- confluence/ src/main/java/org/codehaus/swizzle/confluence You are unlikely to find anything more complete. I have another one for Jira as well. Binaries are available here: http://snapshot.repository.codehaus.org/org/codehaus/swizzle/ Can put out a final if you like. -David On Apr 5, 2006, at 12:39 AM, Emmanuel Venisse wrote: Yes, you need to extends AbstractContinuumNotifier. You can look at MailContinuumNotifier, IrcContinuumNotifier, JabberContinuumNotifier and MsnContinuumNotifier for samples When your notifier will be implemented, do you want to donate it to us? Emmanuel Mang Jun Lau a écrit : Hi, Our company uses Atlassian Confluence as a wiki. I want to try to create a notifier so that after a build, the notification is sent as a message to post on a Confluence page. Since you can post to Confluence via SOAP web services calls, I think may be straightforward to create a notifier. Where do I look to start and what are some of the requirements? Do I simply extend AbstractContinuumNotifier or what? Any direction would help. Thanks. _Mang Lau
Re: Creating a notifier for Confluence
FYI, I have a library available for manipulating Confluence via XML-RPC http://cvs.codehaus.org/viewrep/swizzle/swizzle/swizzle-confluence/ src/main/java/org/codehaus/swizzle/confluence You are unlikely to find anything more complete. I have another one for Jira as well. Binaries are available here: http://snapshot.repository.codehaus.org/org/codehaus/swizzle/ Can put out a final if you like. -David On Apr 5, 2006, at 12:39 AM, Emmanuel Venisse wrote: Yes, you need to extends AbstractContinuumNotifier. You can look at MailContinuumNotifier, IrcContinuumNotifier, JabberContinuumNotifier and MsnContinuumNotifier for samples When your notifier will be implemented, do you want to donate it to us? Emmanuel Mang Jun Lau a écrit : Hi, Our company uses Atlassian Confluence as a wiki. I want to try to create a notifier so that after a build, the notification is sent as a message to post on a Confluence page. Since you can post to Confluence via SOAP web services calls, I think may be straightforward to create a notifier. Where do I look to start and what are some of the requirements? Do I simply extend AbstractContinuumNotifier or what? Any direction would help. Thanks. _Mang Lau
Re: Rss notifier
On Mar 27, 2006, at 12:25 AM, Adam Leggett wrote: Im working on an Rss notifier for continuum. Ive added a comment to CONTINUUM-418 to see if this would be a useful contrib. In the meantime prior to submitting any patch or feature I have to decide which baselined version of the source to use to incorporate the feature in the short term (rather than the current trunk). Ive looked around for a source distribution for 1.0.2/3 but cannot find it. So Ive used tags from svn. Which tag/branch/source distribution would anyone recommend I use as a baseline? The 1.0.3 branch lives here http://svn.apache.org/repos/asf/maven/ continuum/branches/continuum-1.0.x Can't wait to see some RSS ability in Continuum! -David
Re: Distributed Continuum (GBuild)
Nice diagram! Minus javaspaces and JMS in it's place, that's pretty much what we've got. -David On Mar 24, 2006, at 8:49 AM, Vincent Massol wrote: Big +1 too. I've also been waiting for it, see http://tinyurl.com/ 42zc7 :-) Thanks -Vincent -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: mercredi 22 mars 2006 22:13 To: continuum-dev@maven.apache.org Subject: Re: Distributed Continuum (GBuild) +1. I've been really looking forward to it. Jason van Zyl wrote: Hi, I have been talking with David Blevins about moving the GBuild code from Geronimo over to Continuum proper. GBuild is a version of Continuum that works in a distributed fashion. GBuild was created to test the Geronimo TCK across many different platforms with many different configurations and have the results all aggregated back on a master machine. So what I would like to propose is to move the code from GBuild over into Continuum proper and give David Blevins and Kevan Miller commit access. They are both committers on the Geronimo project and are familiar with this distributed code and will continue to work on the code once in Continuum. This is very exciting! Here's my +1 Jason van Zyl
Re: jdk 1.4 and 1.5 in same install?
Sounds like a scary m1-style hack ... not going there. Second install it is -David On Feb 8, 2006, at 1:34 PM, Carlos Sanchez wrote: What about compiler and test plugins options like fork, executable, ... On 2/8/06, David Blevins <[EMAIL PROTECTED]> wrote: So i find myself needing jdk 1.4 for 90% of what i have in the geronimo continuum install, some of those actually can't compile with 1.5 because of corba/vm ties. But alas I do need 1.5 now for at least two projects. Do i pretty much have to setup another continuum install for this? -David
Re: gbuild: maven scm updater issue
On Jan 17, 2006, at 9:11 AM, Emmanuel Venisse wrote: I've never seen this error before. How do you have updated your continuum to continuum-1.0.2? My pom.xml lists a handful of continuum artifacts as deps, all 1.0.2. Do you have all lib? I assume the libs are correct as i use the assembly plugin to build the binaries and it's all worked for a month or so, but there are snapshots involved which adds a wildcard. The jars I have are also listed below. a valid application.xml for 1.0.2? My application.xml only overrides gbuild components, no continuum stuff is referenced. Anyway, if nothing jumps out, then clearly I've got some funky state in my repo and will have to nail this myself. Going to do a brute force search for the InvalidVersionSpecificationException and see if I can't at least find where it should be. -David Emmanuel David Blevins a écrit : I seem to have gotten a bad snapshot on my last build and now all the gbuild agents fail on scm update. I was using an old continuum-1.1- SNAPSHOT but started running into this issue and changed it to continuum-1.0.2 for sanity sake, but still get the same issue. Seems to all be triggered by a NoClassDefFoundError for "org/ apache/ maven/artifact/versioning/ InvalidVersionSpecificationException" Not sure where this is coming from or why this isn't getting sucked in transitively. Any ideas? -David 2006-01-16 21:27:29,143 [Thread-2] INFO ScmManager - Executing: svn --non-interactive update 2006-01-16 21:27:29,144 [Thread-2] INFO ScmManager - Working directory: /home/ dblevins/ gbuild-agent-1.0-SNAPSHOT/bin/linux/../../apps/gbuild- agent/agent/ work/51 2006-01-16 21:27:30,100 [Thread-130] DEBUG ScmManager - At revision 1131. - this realm = plexus.application.gbuild-agent urls[0] = file:/home/dblevins/gbuild-agent-1.0-SNAPSHOT/bin/ linux/../../apps/gbuild-agent/lib/maven-model-2.0.jar urls[1] = file:/home/dblevins/gbuild-agent-1.0-SNAPSHOT/bin/ linux/../../apps/gbuild-agent/lib/maven-artifact-manager-2.0.jar urls[2] = file:/home/dblevins/gbuild-agent-1.0-SNAPSHOT/bin/ linux/../../apps/gbuild-agent/lib/ognl-2.6.7.jar urls[3] = file:/home/dblevins/gbuild-agent-1.0-SNAPSHOT/bin/ linux/../../apps/gbuild-agent/lib/continuum-store-1.0.2.jar urls[4] = file:/home/dblevins/gbuild-agent-1.0-SNAPSHOT/bin/ linux/../../apps/gbuild-agent/lib/backport-util- concurrent-2.0_01_pd.jar urls[5] = file:/home/dblevins/gbuild-agent-1.0-SNAPSHOT/bin/ linux/../../apps/gbuild-agent/lib/maven-settings-2.0.jar urls[6] = file:/home/dblevins/gbuild-agent-1.0-SNAPSHOT/bin/ linux/../../apps/gbuild-agent/lib/commons-cli-1.0.jar urls[7] = file:/home/dblevins/gbuild-agent-1.0-SNAPSHOT/bin/ linux/../../apps/gbuild-agent/lib/commons-pool-1.2.jar urls[8] = file:/home/dblevins/gbuild-agent-1.0-SNAPSHOT/bin/ linux/../../apps/gbuild-agent/lib/jca-1.0.0.jar urls[9] = file:/home/dblevins/gbuild-agent-1.0-SNAPSHOT/bin/ linux/../../apps/gbuild-agent/lib/maven-scm-api-1.0-beta-2.jar urls[10] = file:/home/dblevins/gbuild-agent-1.0-SNAPSHOT/bin/ linux/../../apps/gbuild-agent/lib/plexus-velocity-1.1.2.jar urls[11] = file:/home/dblevins/gbuild-agent-1.0-SNAPSHOT/bin/ linux/../../apps/gbuild-agent/lib/maven-artifact-2.0-alpha-2.jar urls[12] = file:/home/dblevins/gbuild-agent-1.0-SNAPSHOT/bin/ linux/../../apps/gbuild-agent/lib/jpox-dbcp-1.1.0-beta-4.jar urls[13] = file:/home/dblevins/gbuild-agent-1.0-SNAPSHOT/bin/ linux/../../apps/gbuild-agent/lib/doxia-sink-api-1.0-alpha-4.jar urls[14] = file:/home/dblevins/gbuild-agent-1.0-SNAPSHOT/bin/ linux/../../apps/gbuild-agent/lib/maven-repository-metadata-2.0.jar urls[15] = file:/home/dblevins/gbuild-agent-1.0-SNAPSHOT/bin/ linux/../../apps/gbuild-agent/lib/jaas-1.0.1.jar urls[16] = file:/home/dblevins/gbuild-agent-1.0-SNAPSHOT/bin/ linux/../../apps/gbuild-agent/lib/commons-logging-api-1.0.4.jar urls[17] = file:/home/dblevins/gbuild-agent-1.0-SNAPSHOT/bin/ linux/../../apps/gbuild-agent/lib/plexus-action-1.0-alpha-6.jar urls[18] = file:/home/dblevins/gbuild-agent-1.0-SNAPSHOT/bin/ linux/../../apps/gbuild-agent/lib/continuum-api-1.0.2.jar urls[19] = file:/home/dblevins/gbuild-agent-1.0-SNAPSHOT/bin/ linux/../../apps/gbuild-agent/lib/maven-scm-provider-svn-1.0- beta-2.jar urls[20] = file:/home/dblevins/gbuild-agent-1.0-SNAPSHOT/bin/ linux/../../apps/gbuild-agent/lib/maven-plugin-parameter- documenter-2.0.jar urls[21] = file:/home/dblevins/gbuild-agent-1.0-SNAPSHOT/bin/ linux/../../apps/gbuild-agent/lib/continuum-notifier-api-1.0.2.jar urls[22] = file:/home/dblevins/gbuild-agent-1.0-SNAPSHOT/bin/ linux/../../apps/gbuild-agent/lib/commons-collections-2.0.jar urls[23] = file:/home/dblevins/gbuild-agent-1.0-SNAPSHOT/bin/ linux/../../apps/gbuild-agent/lib/plexus-jdo2-1.0-alpha-3.jar urls[24] = file:/home/dbl
gbuild: maven scm updater issue
I seem to have gotten a bad snapshot on my last build and now all the gbuild agents fail on scm update. I was using an old continuum-1.1- SNAPSHOT but started running into this issue and changed it to continuum-1.0.2 for sanity sake, but still get the same issue. Seems to all be triggered by a NoClassDefFoundError for "org/apache/ maven/artifact/versioning/InvalidVersionSpecificationException" Not sure where this is coming from or why this isn't getting sucked in transitively. Any ideas? -David 2006-01-16 21:27:29,143 [Thread-2] INFO ScmManager - Executing: svn --non-interactive update 2006-01-16 21:27:29,144 [Thread-2] INFO ScmManager - Working directory: /home/dblevins/ gbuild-agent-1.0-SNAPSHOT/bin/linux/../../apps/gbuild-agent/agent/ work/51 2006-01-16 21:27:30,100 [Thread-130] DEBUG ScmManager - At revision 1131. - this realm = plexus.application.gbuild-agent urls[0] = file:/home/dblevins/gbuild-agent-1.0-SNAPSHOT/bin/ linux/../../apps/gbuild-agent/lib/maven-model-2.0.jar urls[1] = file:/home/dblevins/gbuild-agent-1.0-SNAPSHOT/bin/ linux/../../apps/gbuild-agent/lib/maven-artifact-manager-2.0.jar urls[2] = file:/home/dblevins/gbuild-agent-1.0-SNAPSHOT/bin/ linux/../../apps/gbuild-agent/lib/ognl-2.6.7.jar urls[3] = file:/home/dblevins/gbuild-agent-1.0-SNAPSHOT/bin/ linux/../../apps/gbuild-agent/lib/continuum-store-1.0.2.jar urls[4] = file:/home/dblevins/gbuild-agent-1.0-SNAPSHOT/bin/ linux/../../apps/gbuild-agent/lib/backport-util-concurrent-2.0_01_pd.jar urls[5] = file:/home/dblevins/gbuild-agent-1.0-SNAPSHOT/bin/ linux/../../apps/gbuild-agent/lib/maven-settings-2.0.jar urls[6] = file:/home/dblevins/gbuild-agent-1.0-SNAPSHOT/bin/ linux/../../apps/gbuild-agent/lib/commons-cli-1.0.jar urls[7] = file:/home/dblevins/gbuild-agent-1.0-SNAPSHOT/bin/ linux/../../apps/gbuild-agent/lib/commons-pool-1.2.jar urls[8] = file:/home/dblevins/gbuild-agent-1.0-SNAPSHOT/bin/ linux/../../apps/gbuild-agent/lib/jca-1.0.0.jar urls[9] = file:/home/dblevins/gbuild-agent-1.0-SNAPSHOT/bin/ linux/../../apps/gbuild-agent/lib/maven-scm-api-1.0-beta-2.jar urls[10] = file:/home/dblevins/gbuild-agent-1.0-SNAPSHOT/bin/ linux/../../apps/gbuild-agent/lib/plexus-velocity-1.1.2.jar urls[11] = file:/home/dblevins/gbuild-agent-1.0-SNAPSHOT/bin/ linux/../../apps/gbuild-agent/lib/maven-artifact-2.0-alpha-2.jar urls[12] = file:/home/dblevins/gbuild-agent-1.0-SNAPSHOT/bin/ linux/../../apps/gbuild-agent/lib/jpox-dbcp-1.1.0-beta-4.jar urls[13] = file:/home/dblevins/gbuild-agent-1.0-SNAPSHOT/bin/ linux/../../apps/gbuild-agent/lib/doxia-sink-api-1.0-alpha-4.jar urls[14] = file:/home/dblevins/gbuild-agent-1.0-SNAPSHOT/bin/ linux/../../apps/gbuild-agent/lib/maven-repository-metadata-2.0.jar urls[15] = file:/home/dblevins/gbuild-agent-1.0-SNAPSHOT/bin/ linux/../../apps/gbuild-agent/lib/jaas-1.0.1.jar urls[16] = file:/home/dblevins/gbuild-agent-1.0-SNAPSHOT/bin/ linux/../../apps/gbuild-agent/lib/commons-logging-api-1.0.4.jar urls[17] = file:/home/dblevins/gbuild-agent-1.0-SNAPSHOT/bin/ linux/../../apps/gbuild-agent/lib/plexus-action-1.0-alpha-6.jar urls[18] = file:/home/dblevins/gbuild-agent-1.0-SNAPSHOT/bin/ linux/../../apps/gbuild-agent/lib/continuum-api-1.0.2.jar urls[19] = file:/home/dblevins/gbuild-agent-1.0-SNAPSHOT/bin/ linux/../../apps/gbuild-agent/lib/maven-scm-provider-svn-1.0-beta-2.jar urls[20] = file:/home/dblevins/gbuild-agent-1.0-SNAPSHOT/bin/ linux/../../apps/gbuild-agent/lib/maven-plugin-parameter- documenter-2.0.jar urls[21] = file:/home/dblevins/gbuild-agent-1.0-SNAPSHOT/bin/ linux/../../apps/gbuild-agent/lib/continuum-notifier-api-1.0.2.jar urls[22] = file:/home/dblevins/gbuild-agent-1.0-SNAPSHOT/bin/ linux/../../apps/gbuild-agent/lib/commons-collections-2.0.jar urls[23] = file:/home/dblevins/gbuild-agent-1.0-SNAPSHOT/bin/ linux/../../apps/gbuild-agent/lib/plexus-jdo2-1.0-alpha-3.jar urls[24] = file:/home/dblevins/gbuild-agent-1.0-SNAPSHOT/bin/ linux/../../apps/gbuild-agent/lib/regexp-1.3.jar urls[25] = file:/home/dblevins/gbuild-agent-1.0-SNAPSHOT/bin/ linux/../../apps/gbuild-agent/lib/jpox-1.1.0-beta-4.jar urls[26] = file:/home/dblevins/gbuild-agent-1.0-SNAPSHOT/bin/ linux/../../apps/gbuild-agent/lib/concurrent-1.3.4.jar urls[27] = file:/home/dblevins/gbuild-agent-1.0-SNAPSHOT/bin/ linux/../../apps/gbuild-agent/lib/maven-plugin-descriptor-2.0.jar urls[28] = file:/home/dblevins/gbuild-agent-1.0-SNAPSHOT/bin/ linux/../../apps/gbuild-agent/lib/gbuild-agent-1.0-SNAPSHOT.jar urls[29] = file:/home/dblevins/gbuild-agent-1.0-SNAPSHOT/bin/ linux/../../apps/gbuild-agent/lib/derby-10.1.1.0.jar urls[30] = file:/home/dblevins/gbuild-agent-1.0-SNAPSHOT/bin/ linux/../../apps/gbuild-agent/lib/maven-reporting-api-2.0.jar urls[31] = file:/home/dblevins/gbuild-agent-1.0-SNAPSHOT/bin/ linux/../../apps/gbuild-agent/lib/maven-scm-provider-cvs-1.0-beta-1- SNAPSHOT.jar urls[32] = f
Re: Security in Continuum
On Jan 12, 2006, at 2:25 PM, Emmanuel Venisse wrote: David Blevins a écrit : On Jan 11, 2006, at 10:13 AM, Emmanuel Venisse wrote: Hi, In 1.1, we have decided to rework all security features. I tried to use osuser but this framework is crappy : [...] I looked at seraph too. This project seems to be interesting, it's used by confluence and jira. It seems we have all we need in it but it require to be used in a web app environment, so i think we can't use it if we want to use security framework in a standalone app in future. Interesting, if you look at the dependencies for seraph, it's clearly using osuser. - http://opensource.atlassian.com/seraph/dependencies.html osuser is use only for the DefaultAuthenticator, if you don't use it, you don't need osuser. Wonder if "writing our own" option couldn't mean writing our own wrapper for osuser. not exactly. osuser would can be supported by a provider of our own. But if we decide to write it, it must be extensible with providers like other framework(osuser, seraph...) and ldap, jaas... I can't believe i forgot about this. http://jpam.sourceforge.net/documentation/ Then we could do real security and not java-toy security only usable by continuum. I've got a shared LDAP directory up on ci.gbuild.org right now which we use instead of /etc/passwd files for logging into the various gbuild machines. There is a j2eetck group that we put people in if they are allowed to see tck related stuff. Would be excellent if we could use that exact setup in continuum to lock off certain projects to only be visible to that or other groups. I've had to setup cron jobs to build the various things that are tck private -- made an attempt to put up a non-public continuum install for that, but it was too much of a pain. -David Emmanuel
Re: gbuild: dream to reality
Ok, here are some of the details I promised. Cc'ing Continuum as as
much of this code as possible is destined to them. The idea is that
we only should need to maintain a few extensions (which I spelled as
extention in the code, oops) for the things that are specific to us
or they don't want.
BASIC PARTS
--
Executing Agent (runs builds)
Producing Agent (creates builds)
Results Agent (aggregates build results)
Each agent consumes or produces on a queue or topic (or both). You
can have as many of each as you need or what. They can run in the
same process or separate processes.
All messages are Maps that are serialized to ObjectMessages onto
either the BUILD.TASKS queue or the BUILD.RESULTS topic.
Excecuting Agent
---
Runs continuums various continuum componentry and "update-from-scm"
and "execute-builder" actions. When this is done, the code has been
updated and built. Has extendible pre and post checking of incoming
builds and outgoing build results. Specifically there is a
BuildAgentExtension (when spelling is fixed) that has a pre(Map
incoming) method and a post(Map incoming, Map outgoing) method.
Implemented Extensions so far:
- FileIncludeExtension: Checks the build request for a
configurable header format. Any headers matching that format are
assumed to point to files that should be read in and included as text
in the response. The file must be one under the project's work
directory.
- HeaderIncludeExtension: Any headers that match the configured
pattern are copied as-is from the build request to the response message.
Producing Agent
---
Scans a directory for properties files that define builds to add to
the build queue. This part could use some work. The implementation
that uses properties files is fine for shoving lots of work onto a
queue in a really easy way, but this is where we also need some more
integration with continuum as a frontend. An implementation of A
Producing Agent could be an alternate implementation of the Continuum
build queue that just turns the build tasks into items that go onto
the jms build queue. Once you do something like that, you need to
consider how things work in Continuum in regards to it's single
threaded nature that seems to be assumed in places of the code.
Results Agent
---
Very bare bones agent that consumes from teh BUILD.RESULTS topic and
invokes BuildResultsExtensions (when spelling is fixed). Performs no
other work aside from invoking the extensions. We can really go nuts
with extensions here. No limit to the ones we can creat to log,
track, compile, report, analyze or otherwise process the results data
in various ways.
The only BuildResultsExtension so far is one that scans for entries
in the results map matching a regex ("^include.*" is the standard).
It takes the value of that entry and writes it into a file. The name
of the file can be created using entries in the map as well. So for
example:
{project.id}/{build.name}-{date}.properties
Some things we could add or do
- System status topic and agent
- A page to display system status (the status of machines online)
- Notification topic and agent that delegates to the notification
manager
- Something to browse the queue and displays the contents
- A results extension to record how long each build took (data
already available)
- Something to use the average time for a build definition and the
work in the queue and estimates the total hours of work to be done
the divides it by the number of machines online and estimates a
completion time.
- Make client connection a component so it can easily be shared
between agents
- Security: maybe ssh-keys for all agents. use SignedObject and
SealedObject for message integrity and host verification.
- Sort properties files when creating build definitions.
- Have DirectoryMonitor file updated events add definitions to the
queue. Allows for builds to be in tasks dir and us to just exec
'touch foo.properties' to queue up the builds inside.
- Add gbuild agent version to message headers
That's all I have time for now. Hope this can get some conversations
started on where to go from here.
-David
On Nov 22, 2005, at 2:44 AM, David Blevins wrote:
On Oct 26, 2005, at 2:01 AM, David Blevins wrote:
When I close my eyes and think big, I see a large federation
consisting of smaller groups of machines from individuals and
companies sharing some common building/testing infrastructure,
open to and co-maintained by members of the community projects,
building all our code all the time and testing it on every variety
of OS, VM and Database imaginable
I'm happy to say...I so nailed this. We've got it, it works, it
rocks. It&#x
[jira] Updated: (CONTINUUM-439) Change scope on get methods in AbstractContinuumAction
[ http://jira.codehaus.org/browse/CONTINUUM-439?page=all ] David Blevins updated CONTINUUM-439: Attachment: AbstractContinuumAction.java.patch > Change scope on get methods in AbstractContinuumAction > > > Key: CONTINUUM-439 > URL: http://jira.codehaus.org/browse/CONTINUUM-439 > Project: Continuum > Type: Improvement > Versions: 1.0 > Reporter: David Blevins > Priority: Minor > Attachments: AbstractContinuumAction.java.patch > > > I am subclassing AbstractContinuumAction in gbuild and need access to these > methods. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (CONTINUUM-439) Change scope on get methods in AbstractContinuumAction
Change scope on get methods in AbstractContinuumAction Key: CONTINUUM-439 URL: http://jira.codehaus.org/browse/CONTINUUM-439 Project: Continuum Type: Improvement Versions: 1.0 Reporter: David Blevins Priority: Minor I am subclassing AbstractContinuumAction in gbuild and need access to these methods. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CONTINUUM-419) Can't click to see the latest build results from the main page
[ http://jira.codehaus.org/browse/CONTINUUM-419?page=comments#action_49865 ] David Blevins commented on CONTINUUM-419: - Super. I'd want to use if for "In progress" builds too. > Can't click to see the latest build results from the main page > -- > > Key: CONTINUUM-419 > URL: http://jira.codehaus.org/browse/CONTINUUM-419 > Project: Continuum > Type: Improvement > Components: continuum-web > Versions: 1.0 > Reporter: David Blevins > Priority: Trivial > > > When you are at the projects page (Summary.vm/fid/continuumProject) it's > really annoying you can't just click somewhere and see the latest build > results. You have to click "Build History" then the top "results" item, > which is a big of traveling. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (CONTINUUM-420) Can't go directly to the "Builds" screen to view build history when at a results page
Can't go directly to the "Builds" screen to view build history when at a results page - Key: CONTINUUM-420 URL: http://jira.codehaus.org/browse/CONTINUUM-420 Project: Continuum Type: Improvement Components: continuum-web Versions: 1.0 Reporter: David Blevins Priority: Trivial It's really odd as the build results page takes over the 'Build' tab. It's fine if you clicked on the results link *from* the build history page, then you can just hit the browser back button (which is still mildly annoying). But if you clicked to the results page from a build email or something you are a few clever clicks away from getting that "Builds" tab to list the history again. You have to click on "Info" or "Working Copy" then click to return to the "Builds" tab which will now be the history page rather than the results you were looking at. Very strange. Consider a "Results" tab that could be a fourth tab on the top. Or a "Build History" link inside the results page. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (CONTINUUM-419) Can't click to see the latest build results from the main page
Can't click to see the latest build results from the main page -- Key: CONTINUUM-419 URL: http://jira.codehaus.org/browse/CONTINUUM-419 Project: Continuum Type: Improvement Components: continuum-web Versions: 1.0 Reporter: David Blevins Priority: Trivial When you are at the projects page (Summary.vm/fid/continuumProject) it's really annoying you can't just click somewhere and see the latest build results. You have to click "Build History" then the top "results" item, which is a big of traveling. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (CONTINUUM-418) RSS feed for build status
RSS feed for build status - Key: CONTINUUM-418 URL: http://jira.codehaus.org/browse/CONTINUUM-418 Project: Continuum Type: Wish Versions: 1.0 Reporter: David Blevins Priority: Minor Lyndon Samson suggested on the Geronimo dev list that an rss feed for reporting build status would be a really great way to report build status. A neat application of that feature would be the ability to include continuum data on a confluence page. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (CONTINUUM-416) A button I could click on the login page to remember me and automatically log me in next time
A button I could click on the login page to remember me and automatically log me in next time - Key: CONTINUUM-416 URL: http://jira.codehaus.org/browse/CONTINUUM-416 Project: Continuum Type: Wish Components: continuum-web Versions: 1.0 Reporter: David Blevins A button I could click on the login page to remember me and automatically log me in next time. Something similar to JIRA or Confluence. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (CONTINUUM-412) Add a "Build Now" link after each build definition
Add a "Build Now" link after each build definition -- Key: CONTINUUM-412 URL: http://jira.codehaus.org/browse/CONTINUUM-412 Project: Continuum Type: Wish Components: continuum-web Versions: 1.0 Reporter: David Blevins Priority: Minor It would be great to have a "Build Now" link on the same line as each build definition on a project's "Info" screen. Then it would be possible to force a build of a specific build definition in a project. This also solves another thing that I found it was oddly not possible to kick off a build from any of the project detail screens (Info, Builds, Working Copy). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Build schedules
I have a hard time understanding what exactly build schedules are supposed to do affect. The default schedule is hourly, but this doesn't cause builds to be kicked off hourly. What is the deal here? -David
[jira] Created: (CONTINUUM-409) Email notifications could still include build stats when includeBuildResult is false
Email notifications could still include build stats when includeBuildResult is false Key: CONTINUUM-409 URL: http://jira.codehaus.org/browse/CONTINUUM-409 Project: Continuum Type: Wish Versions: 1.0 Reporter: David Blevins I really like the "Build statistics" and "Changes" sections continuum creates in the emails and definitely want them in every email. It's really just the section that contains the output generated from the build itself that I don't want as that will consistently be several megs of text for our project. Basically, I assumed 'includeBuildResults=false' would just exclude out everything after these lines Output: I really don't care what the option is called as long as I can get an email as described. Maybe you want to do something like this true true false -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CONTINUUM-408) Description for DEFAULT_SCHEDULE is wrong
[ http://jira.codehaus.org/browse/CONTINUUM-408?page=comments#action_49723 ] David Blevins commented on CONTINUUM-408: - Never mind, I didn't realize the syntax was different that vixie cron > Description for DEFAULT_SCHEDULE is wrong > - > > Key: CONTINUUM-408 > URL: http://jira.codehaus.org/browse/CONTINUUM-408 > Project: Continuum > Type: Bug > Components: continuum-web > Versions: 1.0 > Reporter: David Blevins > Priority: Trivial > > > Description for DEFAULT_SCHEDULE says hourly, when "0 0 * * *" is daily. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (CONTINUUM-408) Description for DEFAULT_SCHEDULE is wrong
Description for DEFAULT_SCHEDULE is wrong - Key: CONTINUUM-408 URL: http://jira.codehaus.org/browse/CONTINUUM-408 Project: Continuum Type: Bug Components: continuum-web Versions: 1.0 Reporter: David Blevins Priority: Trivial Description for DEFAULT_SCHEDULE says hourly, when "0 0 * * *" is daily. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (CONTINUUM-406) irc notifications: support for registered nicks
irc notifications: support for registered nicks --- Key: CONTINUUM-406 URL: http://jira.codehaus.org/browse/CONTINUUM-406 Project: Continuum Type: Improvement Versions: 1.0 Reporter: David Blevins Priority: Minor It seems IRC notifications don't work on irc.freenode.net. i assume it's due to them removing anonymous msg'ing. Probably need to set it up to use a registered nick, and do the /msg identify thing first -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (CONTINUUM-363) Some URLs incorrect when behind httpd with mod_proxy
Some URLs incorrect when behind httpd with mod_proxy Key: CONTINUUM-363 URL: http://jira.codehaus.org/browse/CONTINUUM-363 Project: Continuum Type: Bug Components: continuum-web Versions: 1.0-beta-1 Reporter: David Blevins Given a mod_proxy setup like: [...] RewriteEngine on RewriteRule ^/(.*)$ http://localhost:8080/$1 [p] ProxyPassReverse / http://localhost:8080/ All the URLs but the various icon_foo_sml.gif icons will be hardcoded to the localhost:8080 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
