Skip to content

Commit

Permalink
Bugfix: add if statement to adapt to pull request from fork repo (#625)
Browse files Browse the repository at this point in the history
<!-- Please provide brief information about the PR, what it contains &
its purpose, new behaviors after the change. And let us know here if you
need any help: https://github.com/microsoft/HydraLab/issues/new -->

## Description

<!-- A few words to explain your changes -->

### Linked GitHub issue ID: #  

## Pull Request Checklist
<!-- Put an x in the boxes that apply. This is simply a reminder of what
we are going to look for before merging your code. -->

- [ ] Tests for the changes have been added (for bug fixes / features)
- [ ] Code compiles correctly with all tests are passed.
- [x] I've read the [contributing
guide](https://github.com/microsoft/HydraLab/blob/main/CONTRIBUTING.md#making-changes-to-the-code)
and followed the recommended practices.
- [x] [Wikis](https://github.com/microsoft/HydraLab/wiki) or
[README](https://github.com/microsoft/HydraLab/blob/main/README.md) have
been reviewed and added / updated if needed (for bug fixes / features)

### Does this introduce a breaking change?
*If this introduces a breaking change for Hydra Lab users, please
describe the impact and migration path.*

- [ ] Yes
- [x] No

## How you tested it
*Please make sure the change is tested, you can test it by adding UTs,
do local test and share the screenshots, etc.*


Please check the type of change your PR introduces:
- [x] Bugfix
- [ ] Feature
- [ ] Technical design
- [ ] Build related changes
- [ ] Refactoring (no functional changes, no api changes)
- [ ] Code style update (formatting, renaming) or Documentation content
changes
- [ ] Other (please describe): 

### Feature UI screenshots or Technical design diagrams
*If this is a relatively large or complex change, kick it off by drawing
the tech design with PlantUML and explaining why you chose the solution
you did and what alternatives you considered, etc...*
  • Loading branch information
zhou9584 authored Nov 28, 2023
1 parent 10228df commit 6f72893
Showing 1 changed file with 11 additions and 3 deletions.
14 changes: 11 additions & 3 deletions azure-pipelines-ci.yml
Original file line number Diff line number Diff line change
Expand Up @@ -56,7 +56,11 @@ stages:
inputs:
targetType: 'inline'
script: |
New-Item -Path common/src/test/resources -Name ".env" -ItemType "file" -Value "BLOB_CONNECTION_STRING = $(BLOB_CONNECTION_STRING)"
if(Test-Path variable:BLOB_CONNECTION_STRING){
New-Item -Path common/src/test/resources -Name ".env" -ItemType "file" -Value "BLOB_CONNECTION_STRING = $(BLOB_CONNECTION_STRING)"
}else{
Write-Host "No BLOB_CONNECTION_STRING found"
}
workingDirectory: '$(Build.Repository.LocalPath)'
condition: eq(variables.fullBuild, 'false')
- task: PowerShell@2
Expand Down Expand Up @@ -98,7 +102,11 @@ stages:
inputs:
targetType: 'inline'
script: |
Remove-Item -Path common/src/test/resources/.env -Force
if(Test-Path common/src/test/resources/.env){
Remove-Item -Path common/src/test/resources/.env -Force
}else{
Write-Host "No .env file found"
}
workingDirectory: '$(Build.Repository.LocalPath)'
condition: eq(variables.fullBuild, 'false')
- task: PublishCodeCoverageResults@1
Expand Down Expand Up @@ -173,7 +181,7 @@ stages:
SourceFolder: 'center/deploy_startup/'
Contents: '**'
TargetFolder: '$(Build.ArtifactStagingDirectory)/center_deploy/deploy_startup'
condition: eq(variables.fullBuild, 'true')
condition: eq(variables.fullBuild, 'true')
- task: CopyFiles@2
displayName: Copy deploy center files 3
inputs:
Expand Down

0 comments on commit 6f72893

Please sign in to comment.