Closed Bug 842189 Opened 11 years ago Closed 8 years ago

Work out how git will interact with tbpl

Categories

(Release Engineering :: General, defect)

Product:
Release Engineering
Component:
General
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: hwine, Unassigned)

References

Details

(Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/2858] ) 

When we have builds being triggered via gittool, how will tbpl be populated?

This affects how we name tbpl branches for the temporary integration/gaia-* hg repos.
Blocks: 842095
Summary: Work out how gittool will interact with tbpl → Work out how git will interact with tbpl
Product: mozilla.org → Release Engineering
Is this still pertinent, or are we firm on hg being the single source of truth now?
Component: Other → General Automation
QA Contact: catlee
I believe the scope has changed. hg is the SSOT, but we'd like to provide the ability for devs to easily see (and link to) the git commit as well.

As a first step, this requires that 'mapper' data be accessible publicly, so adding bug 962853 as blocker.

Secondly, whether tighter integration with tbpl or treeherder should be done is, I believe, up to those systems. If they desire that integration, they'll also need access to 'mapper' data.
Blocks: 962853
Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/2851]
Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/2851] → [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/2856]
Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/2856] → [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/2858]
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.