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

Feature/eng common patch 2 #1052

Merged

Conversation

chidozieononiwu
Copy link
Member

Includes changes from #995
But with a new workflow that delays the creation of sync pull requests until test pipelines have been run successfully.

@chidozieononiwu chidozieononiwu requested a review from a team as a code owner September 28, 2020 23:45
@chidozieononiwu chidozieononiwu force-pushed the feature/eng-common-patch-2 branch 2 times, most recently from 97964d7 to c9158f8 Compare September 29, 2020 00:23
Copy link
Contributor

@mitchdenny mitchdenny left a comment

Choose a reason for hiding this comment

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

Quite a few moving parts with this one. Two comments related to security.

@chidozieononiwu chidozieononiwu force-pushed the feature/eng-common-patch-2 branch 6 times, most recently from 7772207 to 386c3e1 Compare September 29, 2020 06:48
@chidozieononiwu chidozieononiwu force-pushed the feature/eng-common-patch-2 branch from 386c3e1 to f63aeba Compare October 1, 2020 21:37

- task: PowerShell@2
displayName: Queue test pipeline
condition: and(succeeded(), ne(variables['${{repo}}-template-definition-id'], ''))
Copy link
Member

Choose a reason for hiding this comment

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

Where do these definition id's get setup? Is it only in the pipeline itself?

Should this be part of the sync-directory.yml file or the eng-common-sync.yml? It feels like it should be part of the eng-common-sync.yml file but I think we are starting to make this sync-directory.yml file be less useful for anything else so maybe it doesn't matter.

Copy link
Member Author

Choose a reason for hiding this comment

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

I did not want to dump the pipeline definition IDs in the source. I know you weren't ok with that in some of my previous work, so I put it in the pipeline via the UI.

Copy link
Member

Choose a reason for hiding this comment

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

I don't particularly like them in either location :) However I was mostly curious about where this lives. Is there a way to look up the definition id by name? So we could build a name and then try to find the associated definition.

Copy link
Member Author

Choose a reason for hiding this comment

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

It looks like one still requires the Definition ID to request information about the pipeline. https://docs.microsoft.com/en-us/rest/api/azure/devops/pipelines/pipelines/get?view=azure-devops-rest-6.1

Copy link
Contributor

Choose a reason for hiding this comment

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

Sadly the API you need is split across multiple groups of REST API, you can use this one to look up a pipeline definition by name:

https://docs.microsoft.com/en-us/rest/api/azure/devops/build/definitions/list?view=azure-devops-rest-6.1

Copy link
Member

Choose a reason for hiding this comment

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

@chidozieononiwu can you please file a follow-up item to figure out a better way to configure the list of test pipelines we want to trigger? I think I'd prefer a list of pipelines in the yml file over having them be hidden away in the variables tab in the web UI.

@azure-sdk
Copy link
Collaborator

The following pipelines have been queued for testing:

java - template
js - template
net - template
python - template

Sign off on the approval gate to test the release stage of each pipeline.

@chidozieononiwu chidozieononiwu force-pushed the feature/eng-common-patch-2 branch from a0e6990 to 30cfbd6 Compare October 6, 2020 21:26
@chidozieononiwu chidozieononiwu force-pushed the feature/eng-common-patch-2 branch from 30cfbd6 to 0690b24 Compare October 6, 2020 21:30
@azure-sdk
Copy link
Collaborator

The following pipelines have been queued for testing:
java - template
js - template
net - template
python - template
Sign off on the approval gate to test the release stage of each pipeline.

@azure-sdk
Copy link
Collaborator

The following pipelines have been queued for testing:
java - template
js - template
net - template
python - template
Sign off on the approval gate to test the release stage of each pipeline.

@chidozieononiwu
Copy link
Member Author

/check-enforcer override

@chidozieononiwu chidozieononiwu merged commit 8118626 into Azure:master Oct 7, 2020
benbp pushed a commit that referenced this pull request Dec 1, 2020
* Update Tools repo Sync to make use of patch files rather than replacing all files in the sync directory

* Update location of patch files

* Add some changes in eng/common to test things

* Update patch application logic

* Switch to pushing to upstream

* Change workflow to use upstream branches

* Add step tp delete braches after merging
sima-zhu pushed a commit to sima-zhu/azure-sdk-tools that referenced this pull request Dec 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants