Please add the Fundraising Tech team to the integration project, so we can help administer our dedicated integration instance.
Members' wikitech logins are:
- andyrussg
- awight
- eeggleston
- khorn
- ssmith
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Declined | None | T90630 Recurring Payments Reporting | |||
| Resolved | • mepps | T97372 Enable ability to look up contacts by phone number | |||
| Resolved | None | T77910 [epic] Upgrade Civi to 4.6 & integrate new reporting | |||
| Resolved | Ejegg | T89404 Create unit and integration tests for Fundraising extensions to identify breaking MediaWiki changes | |||
| Resolved | awight | T78100 Continuous integration - CiviCRM | |||
| Resolved | awight | T86103 CI for Civi: provision and run tests under Jenkins/Zuul | |||
| Resolved | awight | T86374 Deploy CiviCRM integration job to WMF integration server | |||
| Invalid | awight | T89894 Create and provision CI slave instance for CiviCRM testing | |||
| Resolved | awight | T90472 Add Fundraising Tech team to the labs Integration project |
Event Timeline
Comment Actions
I have added all accounts as members of the project.
I have created a sudo policy Fundraising tech team. That gives you all root access on integration-puppetmaster which is the local puppet master. It will let you cherry pick patches there and reload/debug puppetmaster whenever needed.
When the instance is created (T89894), we will need to update that sudo policy to grant you root access on it.
Comment Actions
And I have made Awight a project admin. That should not be needed, but in case it is you will not be blocked :)