Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Indigo RC3 +3 day; Status and Outlook: a long day? ...

For some reason I can't fathom, my nightly build is succeeding, but my integration build is failing. And now I'm getting the heinous sounding git error below. These are the kind of messages from the universe telling you that it's time to call it a day. So.. I've got what looks like a perfectly good nightly build and I'm tempted to use it. But as it is looking like the aggregator build is about to finish, I'm also thinking that I should let David go home. David, if you think a respin is in order I'll commit a change amp.aggr to use my nightly repos, but otherwise I'll catch up next week.



GitAPI created
Fetching changes from the remote Git repository
Fetching upstream changes from git://
[org.eclipse.amp.git] $ git fetch -t git:// +refs/heads/*:refs/remotes/origin/*
fatal: Not a git repository (or any parent up to mount parent /opt)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
ERROR: Problem fetching from origin / origin - could be unavailable. Continuing anyway
ERROR: Could not fetch from any repository
FATAL: Could not fetch from any repository
hudson.plugins.git.GitException: Could not fetch from any repository
	at hudson.plugins.git.GitSCM$2.invoke(
	at hudson.plugins.git.GitSCM$2.invoke(
	at hudson.FilePath.act(
	at hudson.FilePath.act(
	at hudson.plugins.git.GitSCM.checkout(
	at hudson.model.AbstractProject.checkout(
	at hudson.model.AbstractBuild$AbstractRunner.checkout(
	at hudson.model.AbstractBuild$
	at hudson.model.ResourceController.execute(

On Jun 1, 2011, at 1:27 PM, David M Williams wrote:

... is about to begin?

I hope not!

It has been a long time since we've had a green build. Yesterday noonish.

I think the big flood of "catch up" contributions are over ... let us know if not ... but, the latest build still failed with several "could not find artifact ... " errors. These are sometimes due to timing issues ... where someone updates their site or data while an aggregation build is running ...  so maybe this next one (already running) will do better?

But in case not, here's the plan: If you contribute something new, to fix an aggregation build problem, let me know (on this list, or IM, or email) and I can stop current build, and restart another. (And, please, no new "bug fix" builds ... we need to stabilize, even if you were down a day or two for your normal bug fix days ... please only change anything if you need to change something to fix the aggregation build). If your project's contribution breaks a build, and I don't hear anything after a reasonable period of time ... like about 5 or 10 minutes! .... I'll (temporarily) disable the failing contribution and try again ... just in an effort to get as much "green" as possible. We can re-add once we stabilize.

Keep us informed if you are having any troubles.

Much Thanks,

cross-project-issues-dev mailing list

Back to the top