Closed
Bug 823330
Opened 13 years ago
Closed 13 years ago
Set up 'ash' to use a user mozharness repo
Categories
(Release Engineering :: Applications: MozharnessCore, defect)
Release Engineering
Applications: MozharnessCore
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: mozilla, Assigned: mozilla)
Details
(Whiteboard: [mozharness])
Attachments
(2 files, 3 obsolete files)
|
7.51 KB,
patch
|
bhearsum
:
review+
mozilla
:
checked-in+
|
Details | Diff | Splinter Review |
|
7.62 KB,
patch
|
bhearsum
:
review+
mozilla
:
checked-in+
|
Details | Diff | Splinter Review |
Based off m-c.
* what user repo to use?
** Currently guessing users/asasaki/ash-mozharness, can use something else
* what should we have building/testing? (e.g. mozharness unit tests+talos like Cedar, or buildbot-based like m-c?)
** Currently guessing the former
I'd like to have this live by EOW.
Comment 1•13 years ago
|
||
(In reply to Aki Sasaki [:aki] from comment #0)
> Based off m-c.
>
> * what user repo to use?
> ** Currently guessing users/asasaki/ash-mozharness, can use something else
That's fine with me.
> * what should we have building/testing? (e.g. mozharness unit tests+talos
> like Cedar, or buildbot-based like m-c?)
> ** Currently guessing the former
I agree, since we only intend to use this to test mozharness changes, we don't need to run anything not using mozharness.
>
> I'd like to have this live by EOW.
| Assignee | ||
Comment 2•13 years ago
|
||
Testing in staging.
| Assignee | ||
Comment 3•13 years ago
|
||
| Assignee | ||
Comment 4•13 years ago
|
||
Without these changes, MBF clones ash-mozharness into ash-mozharness/ and then calls the script from mozharness/.
This patch hardcodes the mozharness/ directory name, since we're hardcoding it elsewhere.
Attachment #694206 -
Attachment is obsolete: true
| Assignee | ||
Comment 5•13 years ago
|
||
mozilla-tests mozharness_repo is the full url.
Attachment #694205 -
Attachment is obsolete: true
| Assignee | ||
Comment 6•13 years ago
|
||
Needed since mozilla-tests looks at mozharness_repo and mozilla looks at mozharness_repo_path.
| Assignee | ||
Updated•13 years ago
|
Attachment #694228 -
Flags: review?(bhearsum)
| Assignee | ||
Updated•13 years ago
|
Attachment #694248 -
Attachment is obsolete: true
| Assignee | ||
Updated•13 years ago
|
Attachment #694467 -
Flags: review?(bhearsum)
| Assignee | ||
Comment 7•13 years ago
|
||
Ben: we're doing this so we have a short-term solution for mozharness-try (land experimental changes to user repo mozharness, try running builds/tests on Ash, once verified we can land to mozharness proper).
Updated•13 years ago
|
Attachment #694228 -
Flags: review?(bhearsum) → review+
Updated•13 years ago
|
Attachment #694467 -
Flags: review?(bhearsum) → review+
| Assignee | ||
Comment 8•13 years ago
|
||
Comment on attachment 694467 [details] [diff] [review]
(configs) also add mozharness_repo to project_branches
http://hg.mozilla.org/build/buildbot-configs/rev/eef94e5b1385
Attachment #694467 -
Flags: checked-in+
| Assignee | ||
Comment 9•13 years ago
|
||
Comment on attachment 694228 [details] [diff] [review]
(custom) fix mozharness steps in MBF
http://hg.mozilla.org/build/buildbotcustom/rev/5fdb7166002b
Attachment #694228 -
Flags: checked-in+
| Assignee | ||
Updated•13 years ago
|
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Updated•13 years ago
|
Product: mozilla.org → Release Engineering
Updated•12 years ago
|
Component: General Automation → Mozharness
You need to log in
before you can comment on or make changes to this bug.
Description
•