addressing:
Error running command: /usr/bin/spectool --list-files '/tmp/tito-build/rpmbuild-ruby193-d6e54d8c72c34196a4f51ac134c4172b44d9eccae0bLpW/SOURCES/ruby193-1/ruby193.spec' | awk '{print $2}' |xargs -l1 basename
Status code: 31488
Command output: basename: missing operand
Try 'basename --help' for more information.
Traceback (most recent call last):
File "/usr/bin/tito", line 23, in <module>
CLI().main(sys.argv[1:])
File "/usr/lib/python2.7/site-packages/tito/cli.py", line 94, in main
return module.main(argv)
File "/usr/lib/python2.7/site-packages/tito/cli.py", line 401, in main
return builder.run(self.options)
File "/usr/lib/python2.7/site-packages/tito/builder.py", line 194, in run
self.srpm()
File "/usr/lib/python2.7/site-packages/tito/builder.py", line 228, in srpm
self.tgz()
File "/usr/lib/python2.7/site-packages/tito/builder.py", line 479, in tgz
result = run_command(cmd)
File "/usr/lib/python2.7/site-packages/tito/common.py", line 217, in run_command
raise Exception("Error running command")
Exception: Error running command
Add a command-line option of --scratch to perform a scratch
build in Koji. This is easier to use than always setting
the environment variable of SCRATCH=1.
scripted DistGit commits and koji/brew chain-builds
Needs testing.
pep8 cleanup from my changes
switch --no_build to --no-build for consistency
scope matters ... should pay attention to that
Travis[1] runs continuous integration for Open Source projects. With
github, it will run the configured tests and tag pull requests as passing
or failing. This commit adds a Travis configuration.
Since Travis hosts run debian/ubuntu, and execute tests in virtualenv,
getting access to `rpm` and `python-rpm` is impossible, or nontrivial,
at least. For now, ignore the functional tests. To support running the
BuildTargetParser tests, pull that class out into its own module, and
away from release.py, which imports `rpm`.
To configure travis, go to the website, log in with your github account,
then sync your repos under the account tab below your name. Then just
switch the repo to 'on' and it should be all set up.
[1]: http://travis-ci.org
The refactoring of YumRepoReleaser into RsyncReleaser and
YumRepoReleaser caused a regression that didn't allow multiple rsync
locations to be defined and sync'd properly.
Moved a bunch of code around and adding of method variables to
allow multiple rsync and tempdirs to be used.
Use regular expression to extract the SHA1 from the `git ls-remote` call
response. The reason is that there might be some messages in the
response going to stderr, that are captured when using run_command,
e.g.:
```
Could not chdir to home directory /home/johndoe: No such file or directory
fe87e2b75ed1850718d99c797cc171b88bfad5ca refs/tags/my-awesome-lib-1.0.1-1
```
I used 30 and more characters for the regular expression because I was
not sure the SHA1 is always shown as 40 characters. However we can be
quite certain that the word of 30 and more [0-9a-f] characters is a
SHA1.
RsyncReleaser takes an optional argument "filetypes" from releasers.conf
which specifies what type of packages should be rsynced
[rsync_test-example]
releaser = tito.release.RsyncReleaser
builder = tito.builder.MockBuilder
builder.mock = fedora-16-x86_64
filetypes = tgz rpm srpm
rsync = /tmp/rsync_repo/
in case of YumRepoReleaser default filetypes is of course only rpm.
Tito only supported the default build target when releasing,
however, in some cases it was necessisary to change it (building
for zstream for example).
By default, the build target is the same as the branch. With this
change, you can specify a build target on a per branch basis by
adding a 'build_targets' property in the releasers.conf file.
This property takes on the following format:
build_targets = <branch>:<build_target> <branch>:<build_target> ...
An example configuration could be:
[project-x.y.z]
releaser = tito.release.DistGitReleaser
branches = project-x.y
build_targets = project-x.y:project-x.y.z-candidate
Running:
tito release project-x.y.z
would instruct the build system to build with the target
'project-x.y.z-candidate' when building from the project-x.y
branch (i.e rhpkg build --no-wait --target project-x.y.z-candidate).
For releasers copying into a build system SCM, we now extract the
SourceX filenames from the spec file, and anything we see in the
relative directory matching those exactly will be copied. (i.e. if you
store additional sources for your package at the same level as your spec
file, these will now be copied)
MockBuilder was assuming your package would build fine with the normal
builder, anything using NoTgzBuilder (or others likely) would break.
Now we will instantiate a builder internally, whatever the package would
use by default, and use this to build just the srpm before handing it
off to mock.
