ReleaseEngineering/Applications/RelengAPI: Difference between revisions
Jump to navigation
Jump to search
(Shrunk in deference to the README) |
No edit summary |
||
| Line 13: | Line 13: | ||
* Code: https://github.com/mozilla/build-relengapi | * Code: https://github.com/mozilla/build-relengapi | ||
* Deployment: https://api.pub.build.mozilla.org (production) or https://api-pub-build.allizom.org (staging) | * Deployment: https://api.pub.build.mozilla.org (production) or https://api-pub-build.allizom.org (staging) | ||
* Documentation: https://api.pub.build.mozilla.org/docs | |||
* Bugs/RFE's: Use GitHub issues for minor issues; for major work that must be tracked within Mozilla, file bugs in "Release Engineering: Other", cc :dustin | |||
Revision as of 19:20, 4 April 2014
As ReleaseEngineering/Applications attests, releng has a lot of apps, and many of them have APIs. But these APIs are all bespoke implementations, and are not tied to a single endpoint, authentication scheme, etc. RelengAPI aims to be the glue that binds all of these apps together, makes it easy to add new ones, and makes it easy for others to build tools that consume releng's APIs.
Goals
- Simple self-service usage for consumers
- Simple, rapid implementation of new apps
- Operations-friendly
See README.md for more
Links
- Code: https://github.com/mozilla/build-relengapi
- Deployment: https://api.pub.build.mozilla.org (production) or https://api-pub-build.allizom.org (staging)
- Documentation: https://api.pub.build.mozilla.org/docs
- Bugs/RFE's: Use GitHub issues for minor issues; for major work that must be tracked within Mozilla, file bugs in "Release Engineering: Other", cc :dustin