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.

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

CI Task: feature branch specific CI pipeline #9150

Open
sklam opened this issue Aug 22, 2023 · 1 comment
Open

CI Task: feature branch specific CI pipeline #9150

sklam opened this issue Aug 22, 2023 · 1 comment
Assignees
Labels

Comments

@sklam
Copy link
Member

sklam commented Aug 22, 2023

I have used git tricks to preserve history for azure ci changes. For example: 0fc40ca. This can be confusing. Instead, we can explore branch specific CI pipeline that only triggers for the feature branch so that we don't need to modify the default testing scripts.

If this doesn't work as nicely as we hoped, we will go for a two branches approach:

  • one branch for changes merge-able to main
  • one branch for testing
@sklam sklam added the Task label Aug 22, 2023
@sklam sklam self-assigned this Aug 22, 2023
@sklam
Copy link
Member Author

sklam commented Aug 23, 2023

Just did the experiment on my fork.

I have two azure pipelines with different triggers.

Screenshot 2023-08-23 at 11 55 00 AM

This is very doable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant