<feed xmlns='http://www.w3.org/2005/Atom'>
<title>delta/buildstream.git/src/buildstream/_frontend/cli.py, branch chandan/black</title>
<subtitle>gitlab.com: buildstream/buildstream.git
</subtitle>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/buildstream.git/'/>
<entry>
<title>Use 119 line length</title>
<updated>2019-11-05T13:40:03+00:00</updated>
<author>
<name>Chandan Singh</name>
<email>csingh43@bloomberg.net</email>
</author>
<published>2019-11-05T13:40:03+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/buildstream.git/commit/?id=ab707e87f53249d7f2aac17683254b54196f90ce'/>
<id>ab707e87f53249d7f2aac17683254b54196f90ce</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Blacken codebase</title>
<updated>2019-11-05T13:00:30+00:00</updated>
<author>
<name>Chandan Singh</name>
<email>csingh43@bloomberg.net</email>
</author>
<published>2019-11-05T13:00:30+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/buildstream.git/commit/?id=e06c2295b063245dbdb2397e5bd8c4d0a79ba10d'/>
<id>e06c2295b063245dbdb2397e5bd8c4d0a79ba10d</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>frontend: Remove tracking options from `bst build`</title>
<updated>2019-11-04T11:01:14+00:00</updated>
<author>
<name>Chandan Singh</name>
<email>chandan@chandansingh.net</email>
</author>
<published>2019-10-26T18:07:03+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/buildstream.git/commit/?id=576be1fc19bb58d25309a911589ceb9f08f7812d'/>
<id>576be1fc19bb58d25309a911589ceb9f08f7812d</id>
<content type='text'>
BREAKING CHANGE: Remove all tracking related options and flags from
`bst build` command, as discussed on mailing list previously.

See
https://mail.gnome.org/archives/buildstream-list/2019-October/msg00009.html
for the original proposal, and
https://mail.gnome.org/archives/buildstream-list/2019-October/msg00024.html
for a summary.

At the same time, remove use of the removed options from our test suite.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
BREAKING CHANGE: Remove all tracking related options and flags from
`bst build` command, as discussed on mailing list previously.

See
https://mail.gnome.org/archives/buildstream-list/2019-October/msg00009.html
for the original proposal, and
https://mail.gnome.org/archives/buildstream-list/2019-October/msg00024.html
for a summary.

At the same time, remove use of the removed options from our test suite.
</pre>
</div>
</content>
</entry>
<entry>
<title>cli: BST_FORCE_START_METHOD only sets if necessary</title>
<updated>2019-10-18T13:21:17+00:00</updated>
<author>
<name>Angelos Evripiotis</name>
<email>jevripiotis@bloomberg.net</email>
</author>
<published>2019-10-17T11:10:55+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/buildstream.git/commit/?id=11cd08206eb3c4bbb5d82d6a71f7773997ded6a9'/>
<id>11cd08206eb3c4bbb5d82d6a71f7773997ded6a9</id>
<content type='text'>
Allow situations where the start method is already set, this enables us
to use this in testing situations.

Also, print a diagnostic if it's already set to something we didn't
want.

Now this block got more complex, split out into a new function.

Now we're using this string a lot, extract it to a variable, to make
sure we're spelling it correctly everywhere.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Allow situations where the start method is already set, this enables us
to use this in testing situations.

Also, print a diagnostic if it's already set to something we didn't
want.

Now this block got more complex, split out into a new function.

Now we're using this string a lot, extract it to a variable, to make
sure we're spelling it correctly everywhere.
</pre>
</div>
</content>
</entry>
<entry>
<title>cli.py: no fcntl on Windows</title>
<updated>2019-10-08T08:57:25+00:00</updated>
<author>
<name>Angelos Evripiotis</name>
<email>jevripiotis@bloomberg.net</email>
</author>
<published>2019-08-29T10:00:03+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/buildstream.git/commit/?id=4a2b573bfbeb1423a2456c5254561689c7280b9e'/>
<id>4a2b573bfbeb1423a2456c5254561689c7280b9e</id>
<content type='text'>
Work around the fact that we can't import 'fcntl' on Windows, and
confine the workaround to as small a scope as we can.

This enables us to run at least these commands on Windows:

	bst help
	bst init

We can't run any commands that require a Platform object though, which
is most commands.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Work around the fact that we can't import 'fcntl' on Windows, and
confine the workaround to as small a scope as we can.

This enables us to run at least these commands on Windows:

	bst help
	bst init

We can't run any commands that require a Platform object though, which
is most commands.
</pre>
</div>
</content>
</entry>
<entry>
<title>Do not check for casd in bash completion</title>
<updated>2019-10-02T10:37:17+00:00</updated>
<author>
<name>Tristan Maat</name>
<email>tristan.maat@codethink.co.uk</email>
</author>
<published>2019-10-02T09:58:13+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/buildstream.git/commit/?id=9cb1ad2bf413c46ad25a86534a4c4686d116c179'/>
<id>9cb1ad2bf413c46ad25a86534a4c4686d116c179</id>
<content type='text'>
This caused stacktraces when a user didn't have buildbox-casd
installed, even though it wasn't required for completion, even for
artifacts.

It does add a slightly ugly parameter to Context, long-term it might
make sense to create a special slimmed-down context for completion.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This caused stacktraces when a user didn't have buildbox-casd
installed, even though it wasn't required for completion, even for
artifacts.

It does add a slightly ugly parameter to Context, long-term it might
make sense to create a special slimmed-down context for completion.
</pre>
</div>
</content>
</entry>
<entry>
<title>_stream.py: Load the appropriate PipelineSelection in checkout</title>
<updated>2019-09-13T15:04:12+00:00</updated>
<author>
<name>James Ennis</name>
<email>james.ennis@codethink.co.uk</email>
</author>
<published>2019-09-11T16:48:49+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/buildstream.git/commit/?id=25b3f7009aacad8fcfe0364f731573acf2149ece'/>
<id>25b3f7009aacad8fcfe0364f731573acf2149ece</id>
<content type='text'>
This patch ensures checkout behaves like the rest of our
commands which support --deps options. That is, we carry
the "deps" string through to the Stream and load the
corresponding PipelineSelection.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This patch ensures checkout behaves like the rest of our
commands which support --deps options. That is, we carry
the "deps" string through to the Stream and load the
corresponding PipelineSelection.
</pre>
</div>
</content>
</entry>
<entry>
<title>cli.py: Allow checkout to handle --deps all</title>
<updated>2019-09-13T07:33:48+00:00</updated>
<author>
<name>James Ennis</name>
<email>james.ennis@codethink.co.uk</email>
</author>
<published>2019-09-11T15:07:24+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/buildstream.git/commit/?id=5a778ca352f2e1e5d4837e826656107db26cff34'/>
<id>5a778ca352f2e1e5d4837e826656107db26cff34</id>
<content type='text'>
source checkout supports --deps all, so we should be
consistent.

Additionally, a user may want to have build deps in a
potential chroot so you could rebuild any component.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
source checkout supports --deps all, so we should be
consistent.

Additionally, a user may want to have build deps in a
potential chroot so you could rebuild any component.
</pre>
</div>
</content>
</entry>
<entry>
<title>cli.py: Add --compression option to source checkout</title>
<updated>2019-09-12T15:29:13+00:00</updated>
<author>
<name>James Ennis</name>
<email>james.ennis@codethink.co.uk</email>
</author>
<published>2019-09-09T11:16:29+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/buildstream.git/commit/?id=5472d413eff709c8a1ee602ea5536ce35b3abe4b'/>
<id>5472d413eff709c8a1ee602ea5536ce35b3abe4b</id>
<content type='text'>
!1451 introduced the --compression option to bst artifact checkout.
This MR is a step towards making the commands more symmetric,
and introduces the --compression option to bst source checkout

Now we're compressing, we must explicitly close the tarball
once we're done writing to it.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
!1451 introduced the --compression option to bst artifact checkout.
This MR is a step towards making the commands more symmetric,
and introduces the --compression option to bst source checkout

Now we're compressing, we must explicitly close the tarball
once we're done writing to it.
</pre>
</div>
</content>
</entry>
<entry>
<title>cli.py: Make source checkout more consistent with artifact checkout</title>
<updated>2019-09-12T15:29:12+00:00</updated>
<author>
<name>James Ennis</name>
<email>james.ennis@codethink.co.uk</email>
</author>
<published>2019-09-06T16:53:54+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/buildstream.git/commit/?id=6cb668ade39dfe1cf5e23177b022492e1632b035'/>
<id>6cb668ade39dfe1cf5e23177b022492e1632b035</id>
<content type='text'>
This MR changes the behaviour of source checkout so that it is more
like artifact checkout. That is, a --directory option can be provided,
rather than a mandatory LOCATION.

In addition to this, the --tar option is no longer a boolean flag,
rather it expects a tarfile name (just like artifact checkout)

The appropriate tests have also been altered so that they support
the new API
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This MR changes the behaviour of source checkout so that it is more
like artifact checkout. That is, a --directory option can be provided,
rather than a mandatory LOCATION.

In addition to this, the --tar option is no longer a boolean flag,
rather it expects a tarfile name (just like artifact checkout)

The appropriate tests have also been altered so that they support
the new API
</pre>
</div>
</content>
</entry>
</feed>
