Maniphest T185462

Run CirrusSearch integration tests from jenkins
Open, MediumPublic
Actions

Assigned To

None

Authored By

	dcausse
	Jan 22 2018, 10:11 AM

Tags

Referenced Files

None

Subscribers

Description

Currently we run our integration tests from a machine in clouds (cindy).
A script runs on every unmerged commit marked as V+2.
We have done this way because there was no way to setup the proper env in jenkins to run the integration tests.
We could investigate the feasability to setup a docker image with the appropriate env to run them :

MW with CirrusSearch and its dependencies
elasticsearch
elasticsearch plugins

Related Objects
Search...

		Status	Subtype	Assigned	Task
		Open		None	T295735 Decide on the future of Cirrus development/integration environment
		Open		None	T185462 Run CirrusSearch integration tests from jenkins

Event Timeline

dcausse created this task.Jan 22 2018, 10:11 AM

Restricted Application added a project: Discovery-ARCHIVED. · View Herald TranscriptJan 22 2018, 10:11 AM

Restricted Application added a subscriber: Aklapper. · View Herald Transcript

dcausse updated the task description. (Show Details)Jan 22 2018, 10:11 AM

dcausse mentioned this in T185191: Investigate browser tested search results.Jan 22 2018, 10:27 AM

zeljkofilipin subscribed.Jan 22 2018, 10:52 AM

Needs a docker container to support our needs, so we're blocked on this for the moment

• EBjune moved this task from needs triage to search-icebox on the Discovery-Search board.Mar 1 2018, 6:29 PM

Gehel added a parent task: T295735: Decide on the future of Cirrus development/integration environment.Mar 18 2022, 10:42 AM

Umherirrender mentioned this in T311370: Positive test reports by Cindy-the-browser-test-bot should not result in setting Attention to the patch owner.Jun 26 2022, 9:28 PM

WMDE-leszek subscribed.Mar 24 2025, 7:39 PM