Last modified: 2013-04-09 12:54:51 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T48861, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 46861 - Rename Bugzilla component Wikimedia > "Testing Infrastructure" to "Continuous integration"
Rename Bugzilla component Wikimedia > "Testing Infrastructure" to "Continuous...
Status: RESOLVED FIXED
Product: Wikimedia
Classification: Unclassified
Bugzilla (Other open bugs)
wmf-deployment
All All
: Normal minor (vote)
: ---
Assigned To: Krinkle
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-04-03 21:04 UTC by Krinkle
Modified: 2013-04-09 12:54 UTC (History)
5 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Krinkle 2013-04-03 21:04:10 UTC

    
Comment 1 Andre Klapper 2013-04-03 23:13:31 UTC
Thanks for the ticket, appreciated!

Chris told me a few days ago that it might be useful to distinguish between beta cluster support for outward-facing tests and Jenkins/gallium for unit-level "technology-facing" tests, hence I assume that this was the reason for renaming and this renaming had been discussed with Hashar, Chris, Zeljko, Michelle?
Comment 2 Krinkle 2013-04-04 06:48:36 UTC
(In reply to comment #1)
> Thanks for the ticket, appreciated!
> 
> Chris told me a few days ago that it might be useful to distinguish between
> beta cluster support for outward-facing tests and Jenkins/gallium [hence]
> I assume that this was the reason for renaming [..]

I don't know about that. I renamed "Testing Infrastructure" (which has always been used for our production continuous integration infrastructure) to "Continuous integration" to better reflect what it is for.

Now that you mention it, I see a fair amount of bugs filed in "Testing Infrastructure" that are not in its scope, we should create a separate component for that (or have those bugs be kept elsewhere, I recall there being a github repo where that code is maintained, perhaps they prefer to use the issue tracker attached to that instead?).

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links