lp:~jcsackett/charmworld/trigger-test-builds

Branch merges

Propose for merging

No branches dependent on this one.

Merged into lp:charmworld at revision 475

Juju Gui Bot: Approve (continuous-integration) on 2014-01-14

Curtis Hovey (community): Approve (code) on 2014-01-14

Diff: 146 lines (+64/-2)

4 files modified

charmworld/jobs/ingest.py (+17/-0)
charmworld/jobs/tests/test_ingest.py (+36/-2)
default.ini (+6/-0)
test-setup.ini (+5/-0)

api

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

480. By j.c.sackett on 2014-01-14

Changes to address commentar in review.

479. By j.c.sackett on 2014-01-13

Addresses comments in review.

478. By j.c.sackett on 2014-01-13

Remove token from ini. It should probably not be public.

477. By j.c.sackett on 2014-01-13

Add option to disable testing builds on ingest.

476. By j.c.sackett on 2014-01-13

Shut up, lint.

475. By j.c.sackett on 2014-01-13

Trigger test builds on new charms or new revisions of existing charms.

474. By Brad Crittenden on 2014-01-08

Add two more questions to QA assessment.

https://codereview.appspot.com/49030044/

R=bac.

Approved by Juju Gui Bot.

473. By Brad Crittenden on 2014-01-07

Fix a bug that killed the worker.

Fixed 'wait_seconds' and added missing tests.
Added stanzas for logging that are required until the production overrides in
the charm are brought in.

QA: run 'bin/ingest-queued --limit=10 --debug --run-forever' and see that it
waits before proceeding.

https://codereview.appspot.com/48540043/

R=rharding.

Approved by Juju Gui Bot.

472. By Benji York on 2014-01-06

Add docs for setting up ES and Nagios

Also fixed a branch URL in the docs that was no longer valid.

Approved by Juju Gui Bot.

471. By Brad Crittenden on 2014-01-03

Remove HTML from QA question titles.

The HTML displays properly in Charmworld. However when those titles are
displayed in the Juju GUI they are rendered as plain text.

Rather than changing the GUI it is easier to just move any HTML to the
description portion of the question, which is not displayed by the GUI.

The original changes to the QA questions have not yet been deployed on
production so no migration is necessary. Migrations 022 and 023 will need to
be run by hand on staging, however.

https://codereview.appspot.com/47490043/

R=benji.

Approved by Juju Gui Bot.