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

Add 'latest' query route #815

Merged
merged 1 commit into from Aug 2, 2016

Conversation

Projects
None yet
3 participants
@okurz
Copy link
Member

commented Aug 2, 2016

Should always refer to most recent job for the specified scenario.

  • have the same link for test development, i.e. if one retriggers tests, the
    person has to always update the URL. If there would be a static URL even the
    browser can be instructed to reload the page automatically
  • for linking to the always current execution of the last job within one
    scenario, e.g. to respond faster to the standard question in bug reports "does
    this bug still happen?"
@coolo

This comment has been minimized.

Copy link
Contributor

commented Aug 2, 2016

LGTM

@coolo

This comment has been minimized.

Copy link
Contributor

commented Aug 2, 2016

travis da bitch!

@okurz okurz force-pushed the okurz:feature/latest_query branch from c1d7e2e to 4d71e53 Aug 2, 2016

@coveralls

This comment has been minimized.

Copy link

commented Aug 2, 2016

Coverage Status

Coverage increased (+0.06%) to 70.438% when pulling 4d71e53 on okurz:feature/latest_query into a207698 on os-autoinst:master.

@okurz

This comment has been minimized.

Copy link
Member Author

commented Aug 2, 2016

fix'd!

Add 'latest' query route
Should always refer to most recent job for the specified scenario.

* have the same link for test development, i.e. if one retriggers tests, the
person has to always update the URL. If there would be a static URL even the
browser can be instructed to reload the page automatically

* for linking to the always current execution of the last job within one
scenario, e.g. to respond faster to the standard question in bug reports "does
this bug still happen?"

@okurz okurz force-pushed the okurz:feature/latest_query branch from 4d71e53 to 1497238 Aug 2, 2016

@coveralls

This comment has been minimized.

Copy link

commented Aug 2, 2016

Coverage Status

Coverage increased (+0.06%) to 70.438% when pulling 1497238 on okurz:feature/latest_query into a207698 on os-autoinst:master.

@coolo coolo merged commit b10067b into os-autoinst:master Aug 2, 2016

1 check passed

continuous-integration/travis-ci/pr The Travis CI build passed
Details

@okurz okurz deleted the okurz:feature/latest_query branch Aug 2, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.