QA/Execution/Web Testing/Repositories: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
Line 47: Line 47:
# Change the owner in the repository's wiki page to "Web QA (dormant)"
# Change the owner in the repository's wiki page to "Web QA (dormant)"
# Create a pull request that removes all content and adds a notice to the README ([https://github.com/mozilla/mdn-tests/commit/08aa51646e81b74e95ef796253cb2fd8b583e3ae example])
# Create a pull request that removes all content and adds a notice to the README ([https://github.com/mozilla/mdn-tests/commit/08aa51646e81b74e95ef796253cb2fd8b583e3ae example])
# Close any issues or pull requests against the repository
# Deactivate issues for the repository
# Disable Travis CI for the repository
# Disable Travis CI for the repository
# Delete any Jenkins jobs for the repository
# Delete any Jenkins jobs for the repository

Revision as of 02:12, 24 September 2015

Active Repositories

RoR Travis

{{#ask:

Has Owner::Web QA ?Is RoR = RoR format=template template=Web QA/Repositories

}}

Add a new Web QA repository to this list:

Dormant Repositories

RoR Travis

{{#ask:

Has Owner::Web QA (dormant) ?Is RoR = RoR format=template template=Web QA/Repositories

}}

Add a new Web QA repository to this list:

Creating a new repository

Follow these steps to create a new repository under the Mozilla organisation:

  1. Create a new repository in your personal GitHub account
  2. Under "Settings" find the area that allows you to transfer the repository, and click the "Transfer" button
  3. Enter the repository name (for example "treeherder-tests")
  4. Enter the organization "mozilla" - you will need to be in the appropriate GitHub team
  5. Click the "I understand" button, and in a few minutes the repository should be transferred to Mozilla

Deactivating a repository

Follow these steps to mark a repository as inactive:

  1. Change the owner in the repository's wiki page to "Web QA (dormant)"
  2. Create a pull request that removes all content and adds a notice to the README (example)
  3. Close any issues or pull requests against the repository
  4. Deactivate issues for the repository
  5. Disable Travis CI for the repository
  6. Delete any Jenkins jobs for the repository