dotnet
/
vscode-dotnet-runtime
зеркало из https://github.com/dotnet/vscode-dotnet-runtime.git
1
0
Форкнуть 0
Код Задачи Пакеты Проекты Релизы Вики Активность
vscode-dotnet-runtime/1es-azure-pipeline.yml

92 строки
2.3 KiB
YAML
Исходник Обычный вид История

Migrate to 1ES Pipeline (#1679) * Migrate pipeline to 1es * Clean up changes made from migration tool * Separate pipeline out into many yaml files so we can have 2 pipelines without code duplication due to new internal requirement * remove unncessary pipeline backup * Remove pipeline from 1es for public as it is not going to be added to the organization in public * Update yaml loop logic Remove devcontainer as it is out of compliance and not used by anyone * fix mappping by adding body to the loop with indentation: * add a 1es repository * Create a separate 1es pipeline * use self to search in the correct repository * migrate to self on 1es * use folder name pipeline-templates over templates * use yaml over yml * temporarily move jobs into one os * split pools * Move the loop to out of the job * move the task into steps instead of a job as u cant do a job in a job * remove template keyword * dont call steps template in job outside of steps * use yaml instead of yml * add sdl * use unique names for jobs * use _ instead of space * Use azure pipelines name to conform to style * give image to each parameter * make it 1 os for 1 os job and use different pool * Call pool explicyk * try to fix names * Use different source for mac instead of 1es * Update get-func-name * Update public PR pipeline * use public pool as thats what the name param is for * give image name instead of vmimage as it snot used * try to switch to a better pool * try using internal pool on public as external is not available * Publish logs to os specific folder * condition steps so they are skipped if not needed per os * dont care if it succeeded * add paran * remove paran * use parameter pools instead of agent os * move to 7.0 instead of 6 bc six is broken in the cache online maybe * switch to 1es pool * try using public pool * See if mac pipeline has a mirror in svc * use image names from open * Use vm image in the image * Use vm image in the image * update vm image * try to condition the pool * code cleanup now that everything was working * fix whitespace * Update vscode-test * Update vscode-test to the new name * respond to most pr feedback * rename the file as I cannot change the pipeline name while its in main maybe
2024-03-15 01:09:21 +03:00
# Name: dotnet.vscode-dotnet-runtime
# URL: https://dev.azure.com/dnceng/internal/_build?definitionId=656
trigger:
batch: true
branches:
include:
- main
tags:
include:
- SDK-v*
- Runtime-v*
pr:
autoCancel: false
branches:
include:
- '*'
variables:
- name: is-runtime-release
value: $[startsWith(variables['Build.SourceBranch'], 'refs/tags/Runtime-v')]
- name: is-sdk-release
value: $[startsWith(variables['Build.SourceBranch'], 'refs/tags/SDK-v')]
- name: Codeql.Enabled
value: true
resources:
repositories:
- repository: 1esPipelines
type: git
name: 1ESPipelineTemplates/1ESPipelineTemplates
ref: refs/tags/release
parameters:
- name: pools
type: object
default:
- name: NetCore1ESPool-Internal
image: 1es-ubuntu-2204
os: linux
- name: Azure Pipelines
image: macOS-latest
os: macOS
- name: NetCore1ESPool-Internal
image: 1es-windows-2022
os: windows
extends:
Use official templates so we get counted on the internal pie chart (#1713) The migration tool and doc examples all use the unofficial one ecks dee Also create a dupe of the PR pipeline so we can migrate main to that file once it is checked in and then delete the other one to rename it to a more descriptive name.
2024-03-20 01:32:11 +03:00
template: v1/1ES.Official.PipelineTemplate.yml@1esPipelines
Migrate to 1ES Pipeline (#1679) * Migrate pipeline to 1es * Clean up changes made from migration tool * Separate pipeline out into many yaml files so we can have 2 pipelines without code duplication due to new internal requirement * remove unncessary pipeline backup * Remove pipeline from 1es for public as it is not going to be added to the organization in public * Update yaml loop logic Remove devcontainer as it is out of compliance and not used by anyone * fix mappping by adding body to the loop with indentation: * add a 1es repository * Create a separate 1es pipeline * use self to search in the correct repository * migrate to self on 1es * use folder name pipeline-templates over templates * use yaml over yml * temporarily move jobs into one os * split pools * Move the loop to out of the job * move the task into steps instead of a job as u cant do a job in a job * remove template keyword * dont call steps template in job outside of steps * use yaml instead of yml * add sdl * use unique names for jobs * use _ instead of space * Use azure pipelines name to conform to style * give image to each parameter * make it 1 os for 1 os job and use different pool * Call pool explicyk * try to fix names * Use different source for mac instead of 1es * Update get-func-name * Update public PR pipeline * use public pool as thats what the name param is for * give image name instead of vmimage as it snot used * try to switch to a better pool * try using internal pool on public as external is not available * Publish logs to os specific folder * condition steps so they are skipped if not needed per os * dont care if it succeeded * add paran * remove paran * use parameter pools instead of agent os * move to 7.0 instead of 6 bc six is broken in the cache online maybe * switch to 1es pool * try using public pool * See if mac pipeline has a mirror in svc * use image names from open * Use vm image in the image * Use vm image in the image * update vm image * try to condition the pool * code cleanup now that everything was working * fix whitespace * Update vscode-test * Update vscode-test to the new name * respond to most pr feedback * rename the file as I cannot change the pipeline name while its in main maybe
2024-03-15 01:09:21 +03:00
parameters:
sdl:
sourceAnalysisPool:
name: NetCore1ESPool-Internal
image: 1es-windows-2022
os: windows
Enable Policheck 🌎 per Compliance to Scan for Offensive Terms (#1811) * Enable Policheck * Remove the old pipeline We probably should have done this post 1ES Migration * azdo is being buggy and not letting me move from 1 to another so undo this and do it in another pr Revert "Remove the old pipeline" This reverts commit 3c4cc97fa09273a48c115f85997e59d0bcede8e6. * azdo is buggy no more Revert "azdo is being buggy and not letting me move from 1 to another" This reverts commit 012133fd34a3d948ca051b166ffee3dda3ffb0ac.
2024-05-28 19:38:53 +03:00
policheck:
enabled: true
exclusionsFile: $(System.DefaultWorkingDirectory)\PoliCheckExclusions.xml
Migrate to 1ES Pipeline (#1679) * Migrate pipeline to 1es * Clean up changes made from migration tool * Separate pipeline out into many yaml files so we can have 2 pipelines without code duplication due to new internal requirement * remove unncessary pipeline backup * Remove pipeline from 1es for public as it is not going to be added to the organization in public * Update yaml loop logic Remove devcontainer as it is out of compliance and not used by anyone * fix mappping by adding body to the loop with indentation: * add a 1es repository * Create a separate 1es pipeline * use self to search in the correct repository * migrate to self on 1es * use folder name pipeline-templates over templates * use yaml over yml * temporarily move jobs into one os * split pools * Move the loop to out of the job * move the task into steps instead of a job as u cant do a job in a job * remove template keyword * dont call steps template in job outside of steps * use yaml instead of yml * add sdl * use unique names for jobs * use _ instead of space * Use azure pipelines name to conform to style * give image to each parameter * make it 1 os for 1 os job and use different pool * Call pool explicyk * try to fix names * Use different source for mac instead of 1es * Update get-func-name * Update public PR pipeline * use public pool as thats what the name param is for * give image name instead of vmimage as it snot used * try to switch to a better pool * try using internal pool on public as external is not available * Publish logs to os specific folder * condition steps so they are skipped if not needed per os * dont care if it succeeded * add paran * remove paran * use parameter pools instead of agent os * move to 7.0 instead of 6 bc six is broken in the cache online maybe * switch to 1es pool * try using public pool * See if mac pipeline has a mirror in svc * use image names from open * Use vm image in the image * Use vm image in the image * update vm image * try to condition the pool * code cleanup now that everything was working * fix whitespace * Update vscode-test * Update vscode-test to the new name * respond to most pr feedback * rename the file as I cannot change the pipeline name while its in main maybe
2024-03-15 01:09:21 +03:00
stages:
- stage: Internal
jobs:
- ${{ each image in parameters.pools }}:
- template: pipeline-templates/build-test.yaml@self
parameters:
pool:
name: ${{ image.name }}
image: ${{ image.image }}
os: ${{ image.os }}
useOneEngineeringPool: true
- template: pipeline-templates/upstream-verify.yaml@self
parameters:
pool:
name: NetCore1ESPool-Internal
image: 1es-windows-2022
os: windows
useOneEngineeringPool: true
- template: pipeline-templates/lint.yaml@self
parameters:
pool:
name: NetCore1ESPool-Internal
image: 1es-windows-2022
os: windows
useOneEngineeringPool: true
- template: pipeline-templates/package-vsix.yaml@self
parameters:
pool:
name: NetCore1ESPool-Internal
image: 1es-windows-2022
os: windows
useOneEngineeringPool: true