I'm still working on this. For some reason, things aren't being
copied from the Lucene Zone (the Hudson worker node) to the Hudson zone.
-Grant
On Jul 16, 2008, at 1:02 PM, Steven A Rowe wrote:
Hi Grant,
On 07/16/2008 at 12:39 PM, Grant Ingersoll wrote:
I did run publish-maven.sh by hand and I see the items in the
snapshot
repo.
When I look at the lucene-core directory in the snapshot repo via
the web interface, I don't see any 2.4-SNAPSHOT stuff - just the 2.3-
SNAPSHOT dir that was there before:
<http://people.apache.org/maven-snapshot-repository/org/apache/lucene/lucene-core/
>
Is the above URL correct?
Steve
On 07/16/2008 at 12:39 PM, Grant Ingersoll wrote:
OK, I think it should work now. Let's keep an eye out to make sure
the cron job runs tomorrow morning (~5am PST, I think)
I did run publish-maven.sh by hand and I see the items in the
snapshot
repo.
On Jul 16, 2008, at 12:08 PM, Grant Ingersoll wrote:
I take that back, I was looking on the wrong account. It is
running. I'll fix it.
On Jul 16, 2008, at 12:05 PM, Grant Ingersoll wrote:
On Jul 14, 2008, at 1:22 PM, Steven A Rowe wrote:
Looking into this further, I can see that the nightly jars are
being
produced properly - for example, lucene-core is labeled 2.4-
SNAPSHOT, and the files are dated today:
<http://hudson.zones.apache.org/hudson/job/Lucene-trunk/ws/mav
en_artifacts/lucene/lucene-core/
But the path in the above URL is not exactly the same as the path
being copied as part of the nightly cron job, which calls
'publish-
maven.sh' - here are its contents, from
<http://svn.apache.org/viewvc/lucene/java/nightly/publish-mave
n.sh?revision=600897&view=markup
scp -r /export/home/hudson/hudson/jobs/Lucene-Nightly/maven-
artifacts/lucene/* [EMAIL PROTECTED]:/www/
people.apache.org/maven-snapshot-repository/org/apache/lucene
So, assuming there is no path munging going on here, I think
'publish-maven.sh' needs to be changed to reflect the path in the
above hudson nightly URL. Something along the lines of (perl
regex
syntax):
s!jobs/Lucene-Nightly!job/Lucene-trunk/ws!
Could someone with access to the zones machine(s) please verify
this?
If this is the correct fix, I think that Grant would then need to
check out the fixed 'publish-maven.sh' to his home directory on
the
zones machine, since the cron job calling it is run under his
account
- from
<http://svn.apache.org/viewvc/lucene/java/nightly/nightly.cron
?revision=591125&view=markup
03 5 * * * $HOME/lucene/nightly/publish-maven.sh > $HOME/
lucene/nightly/publish-maven.log 2>&1
Hmm, this cron is not being run on my crontab anymore. Let me look
into it more.
Steve
On 07/07/2008 at 3:36 PM, Steven A Rowe wrote:
On 07/04/2008 at 3:28 PM, Karl Wettin wrote:
The snapshots seems to be built every day, but I seems to be
producing
some jars of a non-trunk revision or branch. Perhaps 2.3.2?
I looked at MANIFEST.MF from lucene-core-2.3-SNAPSHOT.jar
(the date for this file in the web page listing on the
snapshot repository is today's date), and it has the following:
Implementation-Version: 2.3-SNAPSHOT 614766 - hudson -
2008-01-24 08:3
6:15
(That "08:3 <newline> <space> 6:15" thing looks weird, but I
don't think it's pertinent to the discussion at hand.)
So it looks like the version is actually a nightly from
2008-01-24.
The nightly/nightly.sh script generates and copies the shapshots
<http://svn.apache.org/viewvc/lucene/java/nightly/nightly.sh?r
evision=629243&view=markup
#Generate the Maven snapshot
#Update the Version # when doing a release
$ANT_HOME/bin/ant -Dversion=2.4-SNAPSHOT generate-maven-artifacts
#copy the artifacts to the side so the cron job can publish them
cp -R dist/maven/org/apache/lucene ../../maven-artifacts
It appears from the above that 2.4-SNAPSHOT should be produced,
and
that the version identifier in nightly.sh was properly updated
around the time of the 2.3.0 release. However, I don't see any
2.4-SNAPSHOT directories in the snapshot repo, and the metadata
XML
file for lucene-core
<http://people.apache.org/maven-snapshot-repository/org/apache
/lucene/lucene-core/maven-metadata.xml
says that 2.3-SNAPSHOT is the only available version:
<?xml version="1.0" encoding="UTF-8"?><metadata>
<groupId>org.apache.lucene</groupId>
<artifactId>lucene-core</artifactId> <version>2.3-SNAPSHOT</
version> <versioning>
<versions>
<version>2.3-SNAPSHOT</version>
</versions>
<lastUpdated>20080124085133</lastUpdated>
</versioning>
</metadata>
So maybe the cron job that copies the maven artifacts to the
snapshot repo area is misbehaving?
Steve
--------------------------
Grant Ingersoll
http://www.lucidimagination.com
Lucene Helpful Hints:
http://wiki.apache.org/lucene-java/BasicsOfPerformance
http://wiki.apache.org/lucene-java/LuceneFAQ
--------------------------
Grant Ingersoll
http://www.lucidimagination.com
Lucene Helpful Hints:
http://wiki.apache.org/lucene-java/BasicsOfPerformance
http://wiki.apache.org/lucene-java/LuceneFAQ
--------------------------
Grant Ingersoll
http://www.lucidimagination.com
Lucene Helpful Hints:
http://wiki.apache.org/lucene-java/BasicsOfPerformance
http://wiki.apache.org/lucene-java/LuceneFAQ
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------
Grant Ingersoll
http://www.lucidimagination.com
Lucene Helpful Hints:
http://wiki.apache.org/lucene-java/BasicsOfPerformance
http://wiki.apache.org/lucene-java/LuceneFAQ
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
