Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Extend e2e test with the remaining providers #172

Open
yitsushi opened this issue Apr 5, 2023 · 3 comments
Open

Extend e2e test with the remaining providers #172

yitsushi opened this issue Apr 5, 2023 · 3 comments
Labels
area/pipelines priority/low team/wild-watermelon testing

Comments

@yitsushi
Copy link
Contributor

yitsushi commented Apr 5, 2023

Add the following checks in the e2e test:

  • Azure DevOps
  • BitBucket

The test suit is a bit chaotic, so it may involve a "bit" of refactoring too.
@yitsushi
Copy link
Contributor Author

yitsushi commented Apr 5, 2023

Blocked by #171

@yitsushi yitsushi mentioned this issue Apr 5, 2023
Closed
3 tasks
@yiannistri yiannistri changed the title Externd e2e test with the remaining providers Extend e2e test with the remaining providers Apr 5, 2023
@lasomethingsomething
Copy link

From @yitsushi: "how stable is the e2e test? Last time I checked it felt like an abandoned "once worked" part of the code. If it's in that state, we may want to split up the work 'get a working e2e' and then we can add extra providers. Doing both in one PR can lead to long running PRs with a lot of changes and never (painful days or even weeks) gets merged."

@lasomethingsomething
Copy link

Would do this after implementing Pipelines 2.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/pipelines priority/low team/wild-watermelon testing
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@yitsushi @lasomethingsomething