ReleaseEngineering/Applications/RelengAPI: Difference between revisions

adding obsolete warning
No edit summary
(adding obsolete warning)
 
(4 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{Obsolete RelEng Page|Future development of RelEng applications was moved to https://docs.mozilla-releng.net}}
As [[ReleaseEngineering/Applications]] attests, releng has a lot of apps, and many of them have APIs.
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.
But these APIs are all bespoke implementations, and are not tied to a single endpoint, authentication scheme, etc.
Line 14: Line 16:
* 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
* Documentation: https://api.pub.build.mozilla.org/docs
* [[ReleaseEngineering/How_To/Update_RelengAPI|How To: Update RelengAPI]]


= Getting Involved =
= Getting Involved =
Line 19: Line 22:
* IRC: #releng, look for dustin
* IRC: #releng, look for dustin
* Patches: releng and relops can push directly for now; GitHub pull requests are welcome from others
* Patches: releng and relops can push directly for now; GitHub pull requests are welcome from others
* 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
* Bugs/RFE's: Use [https://github.com/mozilla/build-relengapi/issues GitHub issues] for minor issues; for major work that must be tracked within Mozilla, file bugs in "Release Engineering: Other", cc :dustin
14

edits