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

Default to release/1.1 branch for conn test pipeline resources #5566

Merged

Conversation

nlcamp
Copy link
Contributor

@nlcamp nlcamp commented Sep 23, 2021

Manually triggered connectivity test pipeline runs on release/1.1 are defaulting to artifacts from the master branch for Build Images and Edgelet Packages. This is a mistake and they should be using artifacts from release/1.1 by default.

@nlcamp
Copy link
Contributor Author

nlcamp commented Sep 23, 2021

Any thoughts on enabling scheduled runs of the connectivity test pipeline on release/1.1? They're currently only scheduled for release/1.2 and master.

Copy link
Member

@damonbarry damonbarry left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I assume we want scheduled triggers, but @and-rewsmith or @yophilav can confirm. And that can be added separately. At least this should ensure that manual builds pick the right branch by default.

@@ -9,10 +9,10 @@ resources:
pipelines:
- pipeline: images
source: 'Azure-IoT-Edge-Core Build Images'
branch: 'master'
branch: 'release/1.1'
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You may want to point out in the PR description that this is for manual builds only (and scheduled, but as you pointed out, scheduled triggers aren't set up in this branch).

@kodiakhq kodiakhq bot merged commit b4f79ac into Azure:release/1.1 Sep 24, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants