Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How do you specify the commit ID / checkout-override for a build? #65

Open
kasajian opened this issue Jan 5, 2016 · 1 comment · May be fixed by #77 or #85
Open

How do you specify the commit ID / checkout-override for a build? #65

kasajian opened this issue Jan 5, 2016 · 1 comment · May be fixed by #77 or #85

Comments

@kasajian
Copy link

kasajian commented Jan 5, 2016

When using the queue command for a build, there's no way to specify which commit ID to build. Or is there a way to specify which branch to build?

Or are we suppose to create a separate build definition for each branch?

@grawcho
Copy link
Member

grawcho commented Apr 4, 2017

this is covered in my fork grawcho
there are a few more options there to "tfx build queue" like adding queue parameters, queuing with brach / commit id, changing priority, adding demands, queuing synchronously (wait), and more.
here is the help text as reference (i'll update the docs in a few days)
Command: queue
Queue a build.

Arguments:
--project, -p Project name.
--definition-id Identifies a build definition.
--definition-name Name of a Build Definition.
--parameters Build process Parameters JSON file / string.
--priority Queue a build with priority 1 [High] - 5 [Low] default = 3 [Normal]).
--version the source version for the queued build.
--shelveset the shelveset to queue in the build.
--demands Demands string [semi-colon separator] for Queued Build [key / key -equals value].
--wait wait for the triggered build
--timeout Maximum time to wait for the build to complete (in seconds).

Enjoy.

additionally you can find this in pull requests as well (feel free to promote them):
PR 77 - nchabra
PR 85 - grawcho

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment