-
Notifications
You must be signed in to change notification settings - Fork 719
Pipeline to facilitate Roslyn Copilot publish #8508
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
Open
AbhitejJohn
wants to merge
5
commits into
dotnet:main
Choose a base branch
from
AbhitejJohn:publishpipeline
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+58
−0
Open
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
05f54b4
Adding back the publish pipeline
AbhitejJohn d44aee0
Merge branch 'main' of https://github.com/dotnet/vscode-csharp into p…
AbhitejJohn a0e0456
Parameterizing the values
AbhitejJohn 5ce9917
Updating to publish the contents instead
AbhitejJohn 3da524d
Merge branch 'main' into publishpipeline
AbhitejJohn File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,58 @@ | ||
| trigger: none | ||
| pr: none | ||
|
|
||
| resources: | ||
| repositories: | ||
| - repository: 1ESPipelineTemplates | ||
| type: git | ||
| name: 1ESPipelineTemplates/1ESPipelineTemplates | ||
| ref: refs/tags/release | ||
| pipelines: | ||
| - pipeline: CI | ||
| project: DevDiv | ||
| source: VisualStudio.Conversations | ||
| branch: main | ||
| extends: | ||
| template: v1/1ES.Official.PipelineTemplate.yml@1ESPipelineTemplates | ||
| parameters: | ||
| pool: | ||
| name: AzurePipelines-EO | ||
| image: 1ESPT-Windows2022 | ||
| os: windows | ||
| stages: | ||
| - stage: Upload | ||
| jobs: | ||
| - job: UploadToServer | ||
| displayName: Upload to server | ||
| pool: | ||
| name: AzurePipelines-EO | ||
| image: 1ESPT-Windows2022 | ||
| os: windows | ||
| templateContext: | ||
| type: releaseJob | ||
| isProduction: false #change this | ||
| inputs: | ||
| - input: pipelineArtifact | ||
| pipeline: CI | ||
| artifactName: partnerDeployables-Windows | ||
| destinationPath: $(Pipeline.Workspace)/artifacts | ||
|
|
||
| steps: | ||
| - checkout: none | ||
|
|
||
| - task: CopyFiles@2 | ||
| displayName: 'Copy files from Zip folder to staging directory' | ||
| inputs: | ||
| SourceFolder: '$(Pipeline.Workspace)/' | ||
| Contents: '**/*Roslyn.LanguageServer*.zip' | ||
| TargetFolder: '$(Build.ArtifactStagingDirectory)/staging' | ||
| CleanTargetFolder: true | ||
|
|
||
| - task: AzureFileCopy@6 | ||
| displayName: "Copy the zip to Azure Storage" | ||
| inputs: | ||
| SourcePath: '$(Build.ArtifactStagingDirectory)/staging/*' | ||
| azureSubscription: "$(AzSubscription)" | ||
| Destination: "AzureBlob" | ||
| storage: "$(AzStorage)" | ||
| ContainerName: "$(AzContainerName)" | ||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Kind of a meta question here. Should this pipeline even be in this repo? Would conversations be a better place?
For example if you want to change the folder name where it finds the conversations build artifacts to upload. Now you have to make the change across two repos. If this was in conversations you just updated both at the same time.
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.
Good question, my thinking was having this closer to the component that actually needs it. The conversations repo has a slightly different set of processes tied to build and release pipelines which are tied to VS. Having it here gives us the freedom to iterate on this quicker. It also keeps this in our teams cross hairs a little more working with the processes we have - its been hard figuring out where things exist, so trying to keep some of the infra pieces atleast in fewer places.