Closed Bug 582932 Opened 15 years ago Closed 15 years ago

Hudson setup

Categories

(Input :: General, defect, P1)

defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: davedash, Assigned: davedash)

References

()

Details

We need to have Hudson setup for Input. We're running into a lot of errors (in staging) that would be caught quickly via good coverage and testing.
we already have buildbot and tinderbox, why can't you use one of those?
(In reply to comment #1) > we already have buildbot and tinderbox, why can't you use one of those? Webdev uses hudson for Continuous Integration.
https://hudson.mozilla.org/ if you're interested.
Target Milestone: --- → 1.6.1
Priority: -- → P1
Moving this to the 1.6.2 train which is being pushed out on 8/10
Target Milestone: 1.6.1 → 1.6.2
Console output: Started by an SCM change Checkout:workspace / /var/lib/hudson/jobs/input.stage.mozilla.com/workspace - hudson.remoting.LocalChannel@c26acd Last Build : #19 Last Built Revision: Revision 85e972548adf48fdb87362d64db788239d455bee (origin/master ) Checkout:workspace / /var/lib/hudson/jobs/input.stage.mozilla.com/workspace - hudson.remoting.LocalChannel@c26acd Fetching changes from the remote Git repository Fetching upstream changes from git://github.com/fwenzel/reporter.git [workspace] $ git fetch git://github.com/fwenzel/reporter.git +refs/heads/*:refs/remotes/origin/* [workspace] $ git ls-tree HEAD Fetching upstream changes from git://github.com/fwenzel/reporter.git/locale/.git [locale] $ git fetch git://github.com/fwenzel/reporter.git/locale/.git +refs/heads/*:refs/remotes/origin/* fatal: protocol error: expected sha/ref, got 'ERR fwenzel/reporter.git/locale/.git is not a valid repository name Visit http://support.github.com for help' ERROR: Problem fetching from origin - could be unavailable. Continuing anyway Seen branch in repository origin/prod-1.5 Seen branch in repository origin/master Seen branch in repository origin/prod Commencing build of Revision 5bd8427ef30a99afe66099b0900dc243d1996a67 (origin/master ) Checking out Revision 5bd8427ef30a99afe66099b0900dc243d1996a67 (origin/master ) [workspace] $ git checkout -f 5bd8427ef30a99afe66099b0900dc243d1996a67 [workspace] $ git submodule init Fetching upstream changes from git://github.com/fwenzel/reporter.git [workspace] $ git fetch git://github.com/fwenzel/reporter.git +refs/heads/*:refs/remotes/origin/* [workspace] $ git ls-tree HEAD Fetching upstream changes from git://github.com/fwenzel/reporter.git/locale/.git [locale] $ git fetch git://github.com/fwenzel/reporter.git/locale/.git +refs/heads/*:refs/remotes/origin/* fatal: protocol error: expected sha/ref, got 'ERR fwenzel/reporter.git/locale/.git is not a valid repository name Visit http://support.github.com for help' ERROR: Problem fetching from origin - could be unavailable. Continuing anyway [workspace] $ git submodule update [workspace] $ git tag -a -f -m "Hudson Build #20" hudson-input.stage.mozilla.com-20 Recording changes in branch origin/master [workspace] $ git log --numstat -M --summary --pretty=raw 85e972548adf48fdb87362d64db788239d455bee..5bd8427ef30a99afe66099b0900dc243d1996a67 [workspace] $ /bin/sh -xe /tmp/hudson6688329817248452861.sh + ./scripts/build.sh /tmp/hudson6688329817248452861.sh: line 2: ./scripts/build.sh: No such file or directory Recording test results Skipping Cobertura coverage report as build was not UNSTABLE or better ... Sending e-mails to: dd@mozilla.com IRC notifier plugin: Sending notification to: #mozwebqa IRC notifier plugin: Sending notification to: #input Finished: FAILURE ----- This is the interesting part: [locale] $ git fetch git://github.com/fwenzel/reporter.git/locale/.git +refs/heads/*:refs/remotes/origin/* fatal: protocol error: expected sha/ref, got 'ERR fwenzel/reporter.git/locale/.git is not a valid repository name Visit http://support.github.com for help' That is indeed a wrong URL. I don't know where it comes from, but the correct repository would be: git://github.com/fwenzel/reporter-locales.git This is a git submodule though, so just running ``git submodule update --init`` should probably do the right thing.
While annoying, this is not the failure reason. I need to write the build script that it's referencing.
FIXED
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
\o/
Status: RESOLVED → VERIFIED
OS: Mac OS X → All
Hardware: x86 → All
Component: Input → General
Product: Webtools → Input
You need to log in before you can comment on or make changes to this bug.