summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* README.rst: Add pipeline status badgejjardon/build_badgeJavier Jardón2018-04-171-0/+3
|
* README.rst: Add coverage badgeJavier Jardón2018-04-161-0/+3
|
* .gitlab-ci.yml: Add coverage regexTristan Van Berkom2018-04-161-0/+1
|
* .gitlab-ci.yml: Perform some python code analysis with radontristan/radonTristan Van Berkom2018-04-161-0/+26
| | | | | This adds a new job in the prepare stage which can be viewed in the gitlab CI, and also produces an artifacts with the json metrics.
* _pipeline.py: Stop printing warning when a build plan does not use some ↵Tristan Van Berkom2018-04-161-17/+0
| | | | | | existing workspaces Fixes issue #360
* tests/frontend/buildcheckout.py: Added regression tests for workspaced junctionsTristan Van Berkom2018-04-161-0/+109
| | | | This guards against regressions of issue #292
* _loader.py: Use shared element instantiation codepaths for junction loading.Tristan Van Berkom2018-04-161-31/+12
| | | | | The consequently fixes issue #292, and you can now use workspaces to work on junctioned projects.
* element.py, _pipeline.py: Moved instantiation codepath to Element class methods.Tristan Van Berkom2018-04-162-54/+74
| | | | | This will allow the instantiation codepath to be shared by the Loader which also needs to instantiate elements for junctions.
* Clean up element/source instantiation code paths.Tristan Van Berkom2018-04-165-24/+16
| | | | | | This removes the extra `kind` parameter from all of the related codepaths, it is redundant since the `kind` attribute is already stored on the MetaElement and MetaSource objects.
* source.py, element.py, _pipeline.py: Streamling preflighting.Tristan Van Berkom2018-04-167-21/+30
| | | | | | | | | | | Instead of having the pipeline preflight all sources separately from elements, have the element preflight it's sources. This is in order to simplify the shared code path for the pipeline and the loader to use for instantiating elements. Also updated tests to expect the new ElementError and SourceError instead of the PipelineError which was raised for preflighting before.
* element.py: Document new BST_FORBID_SOURCES and BST_FORBID_RDEPENDS as ↵Tristan Van Berkom2018-04-161-4/+6
| | | | | | | available since 1.2 Also use any() for the check on the generators, instead of expanding the whole list exhaustively and checking if the list is not empty.
* element.py: Document new Element.prepare() method as available since 1.2Tristan Van Berkom2018-04-161-0/+2
|
* doc/source/format.rst: Some enhancements in how we document dependenciesTristan Van Berkom2018-04-162-33/+59
| | | | | | | | | | | | | | | | | | | | | | | | | | * Added link target in the project.conf documentation for the element-path * List elements in examples without the leading `elements/` path, this is misleading and predates the existence of the element-path * Specify "element path relative" instead of "project relative", this was also outdated. Use these opportunities to link back to the element path project.conf docs section * Document dependency attributes differently - Use a list of attributes - Link back to the first example when speaking of shorthand, instead of duplication the example in two places - Enhanced description of how junction attributes are used - Note that ordering in dependency declaration lists is not meaningful This is an incorporation of Javier Jardón's patch for issue #358 This fixes issue #358.
* NEWS: Adding news entry for cmake plugin enhancement.Tristan Van Berkom2018-04-151-0/+3
|
* _versions.py: Bump BST_FORMAT_VERSION for new cmake format extensionTristan Van Berkom2018-04-151-1/+1
| | | | | | | | | With commit d41940f516498f827967b8e5d311ce6accb88f56, the cmake plugin now supports a new `generator` option which allows one to specify whether to use `Unix Makefiles` (default) or `Ninja` (optional). This requires a format version bump if people want to be sure that the feature is supported.
* buildstream/plugin.py, doc/source/projectconf.rst: Changed policy for core ↵Tristan Van Berkom2018-04-152-26/+11
| | | | | | | | | | | | | | plugin format revisioning The policy for format revisioning of core plugins maintained in BuildStream now changes such that we revision all plugins under the same core format version. This means that format extensions in plugins should be revisioned in the global _versions.BST_FORMAT_VERSION along with the core format, this simplifies parameterization of project.conf for usage of core plugins. This did not really require any code support as our plugins have never been revisioned before.
* _frontend/widget.py: Adhere to policy on private symbolsTristan Van Berkom2018-04-151-269/+307
| | | | This is a part of issue #285
* _frontend/status.py: Adhere to policy on private symbolsTristan Van Berkom2018-04-151-141/+183
| | | | This is a part of issue #285
* _frontend/profile.py: Adhere to policy on private symbolsTristan Van Berkom2018-04-151-3/+3
| | | | This is a part of issue #285
* _frontend/app.py: Adhere to policy on private symbolsTristan Van Berkom2018-04-152-195/+226
| | | | This is a part of issue #285
* plugins/elements/cmake.yaml: allow using ninja instead of make (#279)abderrahim/cmake-ninjaAbderrahim Kitouni2018-04-143-8/+12
| | | | | | | This uses the build tool mode of cmake to have a single command that can call either make or ninja. I've also modified the tests to take the new commands into account
* _artifactcache/tarcache.py: Extracting a missing artifact is a bugTristan Van Berkom2018-04-141-2/+2
| | | | Raise an assertion here, not an ArtifactError.
* _artifactcache/ostreecache.py: Extracting a missing artifact is a bugTristan Van Berkom2018-04-141-2/+2
| | | | Raise an assertion here, not an ArtifactError.
* element.py: Rename _get_full_display_key() -> _get_display_key()Tristan Van Berkom2018-04-143-6/+6
| | | | | | The extra "full" was a bit redundant here, the Element does not export any "less than full" display key accessor, so lets use a more simple name for this.
* element.py: Adhere to policy on private symbolsTristan Van Berkom2018-04-141-569/+611
| | | | | | This involves a lot of reordering of function in the Element class. This is a part of issue #285
* buildelement.py: Use Element.get_variable() instead of poking at private thingTristan Van Berkom2018-04-141-2/+1
| | | | | | This is the only place where Element._get_variables() was used, which we'll now happily remove - also Element implementations in general should not have to use private API.
* source.py: Adhere to policy on private symbolsTristan Van Berkom2018-04-141-16/+17
| | | | This is a part of issue #285
* buildelement.py: Adhere to policy on private symbolsTristan Van Berkom2018-04-141-11/+10
| | | | This is a part of issue #285
* tests/format/variables.py: Ported from old style testsTristan Van Berkom2018-04-1416-79/+64
|
* tests/frontend/show.py: Removing some unused variablesTristan Van Berkom2018-04-141-2/+0
|
* Add NEWS entryelement-prepareTristan Maat2018-04-131-0/+6
|
* Update plugin documentationTristan Maat2018-04-132-3/+19
|
* tests/frontend/workspace.py: Test new workspace format versionTristan Maat2018-04-131-0/+24
|
* tests/frontend/workspace.py: Automatically update versionTristan Maat2018-04-131-5/+6
|
* integration/workspace.py: Test that configure commands run only onceTristan Maat2018-04-132-0/+55
|
* Add element.prepare methodTristan Maat2018-04-134-15/+70
| | | | This is one of the tasks of #209
* buildelement.py: Documentation improvementsTristan Van Berkom2018-04-131-73/+55
| | | | | Document here in terms of what the BuildElement does to implement the abstract Element methods.
* source.py: Enhanced documentationTristan Van Berkom2018-04-131-73/+136
| | | | | Added new Abstract Methods section here, and rearranged sources such that abstract methods are on top.
* element.py: Documentation improvementsTristan Van Berkom2018-04-131-81/+123
| | | | | Added heading section describing the abstract methods, and moving the abstract methods to the top of the class.
* plugin.py: Documentation improvements.Tristan Van Berkom2018-04-131-67/+110
| | | | | | | | Adding "Abstract Methods" section indicating what implementors have to implement. Also fixed some inconsistencies, and moved the abstract methods to the top of the class.
* .gitlab-ci.yml: Show which coverage reports are getting combined in CITristan Van Berkom2018-04-131-0/+1
| | | | | This extra line shows which reports will be combined, which helps us to more quickly debug problems in the coverage job of the .gitlab-ci.yml
* .gitlab-ci.yml: Fix coverage jobjjardon/ci_fedora_27Javier Jardón2018-04-121-4/+3
|
* .gitlab-ci.yml: Change jobs from <distro>-tests to tests-<distro>Javier Jardón2018-04-121-6/+6
| | | | So they show in order nicely in the gitlab CI UI
* .gitlab-ci.yml: Run tests in Fedora:27 as wellJavier Jardón2018-04-121-0/+5
|
* .gitlab-ci.yml: Create template for linux-tests jobJavier Jardón2018-04-121-2/+6
|
* NEWS: Mention failed job summaryRichard Maw2018-04-121-0/+4
|
* tests: Check that output includes log files of failed buildsRichard Maw2018-04-121-0/+28
|
* frontend: Redisplay failure messages in result summaryRichard Maw2018-04-121-1/+12
| | | | | It's more convenient than having to search back through all the output to find out what the cause of failure was.
* frontend: Control indentations of multi-line valuesRichard Maw2018-04-121-0/+5
|
* frontend: Summarise build log output in --no-verbose modeRichard Maw2018-04-121-10/+18
|
View Lorry Controller Status