I think you're going to the wrong link for docs, you're going to the service url. Try: http://140.221.84.191/services/docs/userandjobstate<http://140.221.84.191/services/user_and_job_state/> ---- Daniel Murphy-Olson Systems Administrator Mathematics & Computer Science Division Argonne National Laboratory 630-252-0055<callto:630-252-0055> ________________________________ From: Michael Sneddon [[email protected]] Sent: Monday, November 04, 2013 5:13 PM To: Murphy-Olson, Daniel E. Cc: [email protected] Subject: Re: [Release-team] Deployment of userandjobstate Hi Dan, I just ran through these tests, and the results are below and in the spreadsheet. On Mon, Nov 4, 2013 at 1:59 PM, Murphy-Olson, Daniel E. <[email protected]<mailto:[email protected]>> wrote: Hi all, user_and_job_state has been deployed, and tested in the test environment. We're ready for the following steps: pass script standards pass - there are no scripts; This is a check to make sure that scrips (if they exist) properly return a help message when '-h' or '--help' are passed, and the correct error code. We'll also use this on new modules to ensure script naming conventions and other standards are met (described here: https://docs.google.com/document/d/1bwXes9-f99Hr8EknQ8nrL0UfYpB0rlYVKsSxvE9u...) pass initial doc qc fail, docs are not appearing here: http://140.221.84.191/services/user_and_job_state/ (although it seems they are properly deployed to /kb/deployment/services/userandjobstate/webroot) This test is to ensure API documentation exists, is generated, is deployed to the proper webroot directory, and appears here: http://140.221.84.191/services/. We also conduct a basic read through to make sure the documentation actually 'seems' to make sense and are mostly complete. If other technical docs appear in webroot, we take a look as well to make sure the docs seem to make sense. pass final doc qc I believe this column is there if the initial doc qc failed, the developer checked in changes to correct the documentation problems, and the documentation team takes a second look. Since it looks like in the new spreadsheet format we are creating a new row every time a service is redeployed, do we still need this column? I propose that we get rid of it... release notes updated pass - this is a simple test to make sure a Release Notes file exists, and has minimal documentation on what is new in this release. Do we have each of these documented? I would like to know what our criteria and pass/fail logic is for each of these. ---- Daniel Murphy-Olson Systems Administrator Mathematics & Computer Science Division Argonne National Laboratory 630-252-0055<tel:630-252-0055> _______________________________________________ Release-team mailing list [email protected]<mailto:[email protected]> https://lists.kbase.us/mailman/listinfo/release-team