Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Set some custom fields when creating Test Runs #28

Closed
omaciel opened this issue Feb 18, 2016 · 4 comments
Closed

Set some custom fields when creating Test Runs #28

omaciel opened this issue Feb 18, 2016 · 4 comments
Assignees
Milestone

Comments

@omaciel
Copy link
Member

omaciel commented Feb 18, 2016

When we create a new Test Run, let's set the following custom fields:

  • Automated: True
  • Arch: x86_64
  • Variant: Server
  • Build: Satellite x.y.z Compose n - OS version

screenshot 2016-02-18 09 20 50

@elyezer
Copy link
Collaborator

elyezer commented Feb 22, 2016

We need OS to be added to the list of custom fields. I have a code for these options already.

@elyezer elyezer self-assigned this Feb 22, 2016
@elyezer elyezer modified the milestone: 0.4.0 Jul 4, 2016
@elyezer
Copy link
Collaborator

elyezer commented Jul 4, 2016

Automated flag is already added, currently missing:

  • Arch
  • Variant
  • Build

@elyezer
Copy link
Collaborator

elyezer commented Jul 5, 2016

The above variables are custom fields. That said it may differ from one project to the other and a generic way of passing that information should be created.

For example one possible solution is to expect --custom-fields option that can be specified multiple times and expect a key=value format or even a JSON dict like {"isautomated": true, "arch": "x86_64"}. The later will ensure custom field type and also the parsed information will be passed directly to the TestRun creation.

@omaciel
Copy link
Member Author

omaciel commented Jul 5, 2016

Agreed with the --custom-fields option as it will allow anyone to pass whatever values that want. Obviously it would be up to the user to pass valid values ;)

@omaciel omaciel added the ready label Jul 7, 2016
@elyezer elyezer removed the ready label Jul 8, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants