-
Notifications
You must be signed in to change notification settings - Fork 4.5k
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
Split out Data Movement and WebJobs pipelines #43446
Split out Data Movement and WebJobs pipelines #43446
Conversation
Co-authored-by: Jesse Squire <jesse.squire@gmail.com>
Co-authored-by: Jesse Squire <jesse.squire@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just need the same variants of the tests.yml
file to break out the live pipelines and we should be good to do a prepare and test.
Co-authored-by: Jesse Squire <jesse.squire@gmail.com>
@jsquire all comments addressed. |
Still need the |
/azp run prepare-pipelines |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run net - storage - functions - ci |
/azp run net - storage - functions - tests |
Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
Azure Pipelines successfully started running 1 pipeline(s). |
/check-enforcer override |
@jsquire are we good to merge even though the net - storage - functions - tests pipeline appears to have a problem? |
That's your call @seanmcc-msft. I just wanted to kick off a pipeline to be sure that the prepare worked. The failures that I looked at appear to be normal transient issues. If you're comfortable, I've got no objections to merging. |
/check-enforcer override |
No description provided.