| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
Fixes:
[libdbus-c++] Starting upload
[libdbus-c++] Artifact server problem: 400
[libdbus-c++] Failed to upload libdbus-c++.joidja8
|
|\
| |
| |
| |
| | |
.gitlab-ci.yml: Remove non supported distros
See merge request !316
|
| | |
|
| | |
|
|/
|
|
|
| |
We do not actually support them: current gcc6.3 version doesnt compile
the stage1-gcc currently in definitions (5.3)
|
|\
| |
| |
| |
| | |
Add support for Git LFS repositories
See merge request !318
|
| | |
|
| | |
|
|/ |
|
|\
| |
| |
| |
| | |
Remove unused riemann functionality - depends were breaking pipelines
See merge request !312
|
|/ |
|
|\
| |
| |
| |
| | |
Tristan build sha if exists
See merge request !310
|
| |
| |
| |
| |
| |
| | |
In case it was overridden by the 'sha' field for the purpose of
building, we still want to export the original 'ref' field in
the saved target.yml
|
|/ |
|
|\
| |
| |
| |
| | |
Tristan/symlinks and staging
See merge request !308
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We use the split artifact metadata to move files from the staged
system directory into a <system>.inst/ subdirectory one file at
a time, after running system integration commands and ldconfig.
The current working assumption is that if a file was listed in
the artifact output; it will certainly exist when we try to move
it into the system install directory, but this is not true.
Running system integration commands and ldconfig can result in
removing files, one working example is when you have broken symlink
installed into an artifact inside a libdir. ldconfig will delete
dangling symlinks in it's libdirs with extreme prejudice.
It may or may not make sense to eventually turn this into an error.
|
|/
|
|
|
|
|
|
|
|
|
|
|
| |
This is important because a chunk can install a link to a
directory that does not exist; while not being responsible
for creating the symlink target directory. The result is
later failures when trying to stage files across the broken
symlink boundary.
This throws an IOError (and not a clean exit()) if a symlink
points outside of the staging area. This is because resolving
the relative symlink path is taken care of so if the error
triggers it's an internal bug (not a problem with definitions).
|
|\
| |
| |
| |
| | |
Added -m/--mode command line argument.
See merge request !307
|
|/
|
|
|
|
|
|
|
|
| |
If specified, the mode argument will override whatever mode
was loaded in the YBD installation configuration.
This is especially useful when you have one YBD installation that
you use accomplish multiple tasks, you may want to just create
a manifest and then later build; without having to modify a
configuration file.
|
|\
| |
| |
| |
| | |
splitting.py: Print a warning if stratum does not have contents
See merge request !306
|
|/
|
|
|
|
| |
This is better than crashing, but happens when a system references
a stratum that doesnt exist. This is better than the crash but
the error should be found at load time.
|
|\
| |
| |
| |
| | |
utils.py: Dont stomp on non-empty directories with symlinks
See merge request !305
|
|/ |
|
|\
| |
| |
| |
| | |
Encode the expanded repo url in the saved target yaml
See merge request !304
|
|/
|
|
| |
This is useful for external tools to operate on the generated yaml
|
|\
| |
| |
| |
| | |
requirements.freeze.txt: Require protobuf==3.0.0
See merge request !303
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently version of protobuf (3.2.0) breaks ybd:
$ ybd/ybd.py systems/build-system-x86_64-chroot.morph x86_64
Traceback (most recent call last):
File "ybd/ybd.py", line 18, in <module>
runpy.run_module('ybd')
File "/usr/lib/python2.7/runpy.py", line 182, in run_module
mod_name, loader, code, fname = _get_module_details(mod_name)
File "/usr/lib/python2.7/runpy.py", line 111, in _get_module_details
__import__(mod_name) # Do not catch exceptions initializing package
File "/builds/baserock/definitions/ybd/ybd/__init__.py", line 16, in <module>
import app
File "/builds/baserock/definitions/ybd/ybd/app.py", line 32, in <module>
from riemann_client.transport import TCPTransport
File "/usr/local/lib/python2.7/dist-packages/riemann_client/transport.py", line 12, in <module>
import riemann_client.riemann_pb2
File "/usr/local/lib/python2.7/dist-packages/riemann_client/riemann_pb2.py", line 10, in <module>
from riemann_client.riemann_pb2_py2 import (Event, Msg, Query, Attribute)
File "/usr/local/lib/python2.7/dist-packages/riemann_client/riemann_pb2_py2.py", line 32, in <module>
options=None),
File "/usr/local/lib/python2.7/dist-packages/google/protobuf/descriptor.py", line 494, in __new__
_message.Message._CheckCalledFromGeneratedFile()
TypeError: Descriptors should not be created directly, but only retrieved from their parent.
|
|\
| |
| |
| |
| | |
Fixes #247 ybd can now generate a single file containing all defs with SHAs (and build from it)
See merge request !300
|
| |
| |
| |
| |
| |
| |
| | |
Now we save the resolved definitions as ./$target.yml
And if we specify a $target.yml file when running ybd, ybd will
now parse that, instead of the morph files in the directory tree.
|
| | |
|
| |
| |
| |
| |
| | |
Also, if we set branches in the ref: fields now, these get
resolved to sha: in output $definitions.yml file
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The release-note functionality needs to explore previous version of
definitions, so we do
- git stash
- checkout the old version
- figure out what we need
- git stash pop
Git stash will fail unless user and email are configured, so we
do that here.
|
|/
|
|
|
| |
Previously if release-note: was specified, but release-command
was not, then ybd would error. Renamed to release-cmd for pep8
|
|\
| |
| |
| |
| |
| |
| | |
Fix #249 Update to artifact-version: 7, max-jobs is now in cache-key
Closes #249
See merge request !302
|
|/ |
|
|\
| |
| |
| |
| | |
Minor install_dependencies.sh fixes
See merge request !301
|
| | |
|
|/ |
|
|\
| |
| |
| |
| |
| |
| | |
.gitlab-ci.yml: Use debian:jessie instead python:2.7-slim by default
Closes #254
See merge request !294
|
|/
|
|
|
|
| |
python:2.7-slim install python in /usr/local instead /usr, which
is causing problems with our extensions that expect python to
be in /usr/bin/python
|
|\
| |
| |
| |
| |
| |
| | |
Remove system python pip and upgrade python packages if needed
Closes #253
See merge request !298
|
| | |
|
|/ |
|
|\
| |
| |
| |
| |
| |
| | |
Fix #250 - don't leak kbas user:pass in logs
Closes #250
See merge request !296
|
|/ |
|
|\
| |
| |
| |
| |
| |
| | |
Don't attempt to re-use tmpdir
Closes #252
See merge request !295
|
|/ |
|
|\
| |
| |
| |
| | |
Test build in several distros as part of the CI
See merge request !293
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This is at the moment:
- Debian jessie (stable)
- Debian stretch (testing)
- Ubuntu 16.04 LTS
- Ubuntu 16.10
- Centos 7
|
| | |
|