#390 Add scenario field to the database + migration script
Merged by vmaljulin. Opened by vmaljulin.
vmaljulin/waiverdb RHELWF-1854  into  master

Download 390.patch
no initial comment
factory2jenkins commented

Build 0c6477e0d76f39302cb914bdae5ea40c13bdcfee FAILED!
Rebase or make new commits to rebuild.

Seems like the CI failed running the tests, could you check?

Is there a card for the change? If yes, could you add it to the commit message?

Add tests to get/set scenario in DB.

Shouldn't this be waiverdb/alembic?

Any reason to uncomment this? Did the default change?

Shouldn't this be waiverdb/alembic?

No, it's not working that way

Seems like the CI failed running the tests, could you check?

Some LDAP failures, not sure why (but probably related to previous change). I'll try to fix it.

rebased onto f51c7e303effc399bf273ccb30a7b866a4743072

factory2jenkins commented

Build 39d207ee05833745c90ae3c46081ee6f7512ec12 FAILED!
Rebase or make new commits to rebuild.

3 new commits added

  • Debug info for exception (temporary commit)
  • Add migration script for the scenario field
  • Add scenario field to the database
factory2jenkins commented

Build 83b39ea2453988af2de1710f33a1fc37f818e786 FAILED!
Rebase or make new commits to rebuild.

3 new commits added

  • Debug info for exception (temporary commit)
  • Add migration script for the scenario field
  • Add scenario field to the database
factory2jenkins commented

Build 00b53725606fab95f48697d37d062a04f7dc4053 FAILED!
Rebase or make new commits to rebuild.

3 new commits added

  • Debug info for exception (temporary commit)
  • Add migration script for the scenario field
  • Add scenario field to the database
factory2jenkins commented

Build 9b00adf21799645c837e30681c0f955b9c0d68ad FAILED!
Rebase or make new commits to rebuild.

3 new commits added

  • Debug info for exception (temporary commit)
  • Add migration script for the scenario field
  • Add scenario field to the database
factory2jenkins commented

Build aea2cd6aafb81456cd5516a3a53a109207f60421 FAILED!
Rebase or make new commits to rebuild.

3 new commits added

  • Debug info for exception (temporary commit)
  • Add migration script for the scenario field
  • Add scenario field to the database
factory2jenkins commented

Build b1723064fc514c261a3fbad820a0d287901e6970 FAILED!
Rebase or make new commits to rebuild.

3 new commits added

  • Debug info for exception (temporary commit)
  • Add migration script for the scenario field
  • Add scenario field to the database
factory2jenkins commented

Build c41fb7799c9ef80b31fcaffa49b4251ca4074c33 FAILED!
Rebase or make new commits to rebuild.

3 new commits added

  • Debug info for exception (temporary commit)
  • Add migration script for the scenario field
  • Add scenario field to the database

rebased onto 107190c48837e736d316d3a1f77f6f1e4be4702d

2 new commits added

  • Add migration script for the scenario field
  • Add scenario field to the database

Looks good to me +1

Pull-Request has been merged by vmaljulin

There are still no tests for the new DB field.

Metadata