scripts/master/buildbucket/__init__.py - Issue 968053003: BuildBucket-based build triggering

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Unified Diff: scripts/master/buildbucket/init.py

Issue 968053003: BuildBucket-based build triggering (Closed) Base URL: svn://svn.chromium.org/chrome/trunk/tools/build

Patch Set: Created 5 years, 10 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

Index: scripts/master/buildbucket/__init__.py

diff --git a/scripts/master/buildbucket/__init__.py b/scripts/master/buildbucket/__init__.py

index 4739b8797492945353fc4f65f52253eb35ba3c5e..78b7cfac89ef146fc1f56265395f533e89f7a518 100644

--- a/scripts/master/buildbucket/__init__.py

+++ b/scripts/master/buildbucket/__init__.py

@@ -25,6 +25,7 @@ from .integration import BuildBucketIntegrator

from .poller import BuildBucketPoller

from .status import BuildBucketStatus

from . import client

+from . import trigger

ghost stip (do not use) 2015/03/04 23:07:30 have we always used relative imports here? seems w

nodir 2015/03/04 23:52:09 I understand why using absolute imports is better:

def setup(

« no previous file with comments | « no previous file | scripts/master/buildbucket/trigger.py » ('j') | no next file with comments »