Custom Query (159 matches)

pb should be able to run the whole process cms2vm and test2vm without any gui and user interaction (if ssh is configured correctly by the user).

For example:

We use Project-Builder to run tests during the night on different distributions (results: softqa.engsas.de/meganizer). This test are run by cron without gui and any interaction.

1. Problem gui less:

We discussed some points concerning making pb guiless on the mailing list, if there are no changes right now, i've appended the patch, which I suggested there. The patch assumes, that the user wants to access the VM only if he launches launchvm. All other launches are done by pb and therefore I assume, that the user does not interact with VM manually.

We started to discuss some other possible solutions, which may be better. This ticket should be ment as a remind, to go on with that discussion.

2. Sometimes the vm hangs:

Sometimes, the VM hangs (randomly, don't know why), but pb does not detect it, so I suggest to let the user define a default max time per vm, after that time, the vm is halted or killed if halt is not working. This does not solve the problem with the vm, but the process isn't stopped completly and the following vm's are at least processed.

Hi,

Newer source format packages (quilt) 3.0 cannot be processed by pb correctly. For example we have the following tree:

~/pb/graphite/pbconf/graphite/deb$ tree
.
|-- changelog
|-- compat
|-- conf
|   `-- apache2.conf
|-- control
|-- copyright
|-- dirs
|-- install
|-- links
|-- patches
|   |-- install-path.diff
|   |-- series
|   `-- storage-path.diff
|-- postinst
|-- postrm
|-- pycompat
|-- pyversions
|-- rules
|-- source
|   `-- format
`-- watch

As a cms2build result we will have source, patches, and conf directories created as files:

tar tzf /home/pb/pb/graphite/delivery/graphite-0.9.6.pbconf.tar.gz
graphite-0.9.6/pbconf/
graphite-0.9.6/pbconf/debian-5.0-x86_64/
graphite-0.9.6/pbconf/debian-5.0-x86_64/pyversions
graphite-0.9.6/pbconf/debian-5.0-x86_64/postrm
graphite-0.9.6/pbconf/debian-5.0-x86_64/source
graphite-0.9.6/pbconf/debian-5.0-x86_64/links
graphite-0.9.6/pbconf/debian-5.0-x86_64/rules
graphite-0.9.6/pbconf/debian-5.0-x86_64/dirs
graphite-0.9.6/pbconf/debian-5.0-x86_64/postinst
graphite-0.9.6/pbconf/debian-5.0-x86_64/watch
graphite-0.9.6/pbconf/debian-5.0-x86_64/patches
graphite-0.9.6/pbconf/debian-5.0-x86_64/changelog
graphite-0.9.6/pbconf/debian-5.0-x86_64/compat
graphite-0.9.6/pbconf/debian-5.0-x86_64/pycompat
graphite-0.9.6/pbconf/debian-5.0-x86_64/conf
graphite-0.9.6/pbconf/debian-5.0-x86_64/install
graphite-0.9.6/pbconf/debian-5.0-x86_64/control
graphite-0.9.6/pbconf/debian-5.0-x86_64/copyright

​http://wiki.debian.org/Projects/DebSrc3.0

Actually keeping the vm's (and ve's) up to date is very time consuming. It may be more easy, if a target exists, which starts all vm's after each other and installs all available updates.