Closed Bug 985600 Opened 8 years ago Closed 8 years ago

Stop setting JAVA_HOME in buildbot and mozharness to a dir that does not exist

Categories

(Release Engineering :: Applications: MozharnessCore, defect)

x86_64
Windows 7
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: Callek, Assigned: Callek)

References

Details

Attachments

(2 files, 1 obsolete file)

So over in Bug 971841 we found that JAVA_HOME is incorrectly set (it's set to where we used to install the jdk on old cent5 machines, pre-mock)

Now that we're using mock and configure is finding java properly, we don't need this. And in fact its mere presence breaks ant as we're trying to use it in Bug 971841.
Attachment #8393653 - Flags: review?(armenzg)
Attachment #8393653 - Flags: review?(armenzg) → review+
Attached patch [mozharness] v1 (obsolete) — Splinter Review
Attachment #8393695 - Flags: review?(armenzg)
Attachment #8393695 - Flags: review?(armenzg) → review+
Comment on attachment 8393695 [details] [diff] [review]
[mozharness] v1

Backed out due to single locale config bustage.
http://hg.mozilla.org/build/mozharness/rev/bc0240453669
Attachment #8393695 - Flags: checked-in+ → checked-in-
Attached patch [mozharness] v2Splinter Review
Not landing this tonight, fwiw.

But this rolls up last patch, and did a full search for JAVA_HOME which no longer returns anything in mozharness
Assignee: nobody → bugspam.Callek
Attachment #8393695 - Attachment is obsolete: true
Status: NEW → ASSIGNED
Attachment #8393856 - Flags: review?(aki)
Comment on attachment 8393856 [details] [diff] [review]
[mozharness] v2

I was worried about jarsigner for a bit, then remembered that we use the signing server for android apks now.
Attachment #8393856 - Flags: review?(aki) → review+
in production :)
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Component: General Automation → Mozharness
You need to log in before you can comment on or make changes to this bug.