-
-
Notifications
You must be signed in to change notification settings - Fork 137
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
1.3.0 Progress - bug-fixes and enhancements (#57)
* some minor things * + Removing the disable server logic which was a bit wanky. + Removing cache by server. In DNS all servers should have the same answer for a question, no need to cache per server! + (work in progress) keep API stable (from 1.1.0 on), adding unit tests + (work in progress) query options & tests * * Added max cache timeout which can be used to set an upper limit how long any records should be cached. see #48 * Fixing a bug with non-empty OPT records, see #55. * Changing the logic which removed the EDNS opt record from the results. The record will now be in the additonal records and can have data (the raw bytes). * Added version compatibility testing to make sure I'm not breaking stuff. Optional parameters are not fun sometimes ~~ * Update azure-pipelines-ci.yml for Azure Pipelines * Update azure-pipelines-ci.yml for Azure Pipelines * cleanup * Update azure-pipelines-ci.yml for Azure Pipelines * Update azure-pipelines-ci.yml for Azure Pipelines * Update azure-pipelines-ci.yml for Azure Pipelines * trying to fix build part 10 * another build update * Readme update * Update azure-pipelines-ci.yml pack build config * trying to change nuget versioning * Update azure-pipelines-ci.yml for Azure Pipelines * Update azure-pipelines-ci.yml for Azure Pipelines * Test build pack * Test build pack - version suffix somehow teleports from one task to another? * Test build pack - version suffix somehow teleports from one task to another? * Test build pack - version suffix somehow teleports from one task to another? * Test build pack - version suffix somehow teleports from one task to another? * Test build pack - version suffix somehow teleports from one task to another? 2nd pack still doesn't work, just ignores anything passed into arguments it seems? * Test build pack - version suffix somehow teleports from one task to another? 2nd pack still doesn't work, just ignores anything passed into arguments it seems? * Test build pack - version suffix somehow teleports from one task to another? 2nd pack still doesn't work, just ignores anything passed into arguments it seems? * new pack script * new pack script - publish seems to finally work, testing publish now * changing to new icon tag * Update azure-pipelines-ci.yml for Azure Pipelines * testing multiple jobs * build configuration not working * build configuration.. * multi build * multi build * multi build targeting * disabling testing on linux for now * add master branch as trigger [skip ci]
- Loading branch information
Showing
79 changed files
with
1,645 additions
and
1,545 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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 |
---|---|---|
@@ -1,34 +1,66 @@ | ||
# ASP.NET Core (.NET Framework) | ||
# Build and test ASP.NET Core projects targeting the full .NET Framework. | ||
# Add steps that publish symbols, save build artifacts, and more: | ||
# https://docs.microsoft.com/azure/devops/pipelines/languages/dotnet-core | ||
name: '$(Date:yyyyMMdd)$(Rev:.r)' | ||
|
||
trigger: | ||
- dev | ||
- master | ||
|
||
pool: | ||
vmImage: 'windows-latest' | ||
# pool: | ||
# vmImage: 'windows-latest' | ||
|
||
variables: | ||
solution: '**/*.sln' | ||
buildPlatform: 'Any CPU' | ||
buildConfiguration: 'Release' | ||
versionSuffix: 'beta-$(Build.BuildNumber)' | ||
|
||
steps: | ||
- task: NuGetToolInstaller@1 | ||
jobs: | ||
- job: 'Linux' | ||
displayName: 'Build on Ubuntu' | ||
pool: | ||
vmImage: 'ubuntu-latest' | ||
steps: | ||
- task: DotNetCoreCLI@2 | ||
inputs: | ||
command: 'build' | ||
projects: | | ||
src/**/*.csproj | ||
arguments: '-c Release -f netstandard2.0' | ||
name: 'Build' | ||
displayName: 'build sources' | ||
|
||
- task: NuGetCommand@2 | ||
inputs: | ||
restoreSolution: '$(solution)' | ||
# TODO: re-work unit tests to run without unpredictable local DNS results or run bind on those build agents? | ||
# - task: DotNetCoreCLI@2 | ||
# inputs: | ||
# command: 'test' | ||
# projects: 'test/DnsClient.Tests/*.csproj' | ||
# publishTestResults: true | ||
# arguments: '-c Release -f netcoreapp3.0' | ||
|
||
- task: VSBuild@1 | ||
inputs: | ||
solution: '$(solution)' | ||
msbuildArgs: '' | ||
platform: '$(buildPlatform)' | ||
configuration: '$(buildConfiguration)' | ||
- job: Windows | ||
displayName: 'Build & Test on Windows' | ||
pool: | ||
vmImage: 'windows-latest' | ||
|
||
- task: VSTest@2 | ||
inputs: | ||
platform: '$(buildPlatform)' | ||
configuration: '$(buildConfiguration)' | ||
steps: | ||
- task: DotNetCoreCLI@2 | ||
inputs: | ||
command: 'build' | ||
projects: | | ||
src/**/*.csproj | ||
test/DnsClient.Tests/*.csproj | ||
arguments: '-c Release' | ||
name: 'Build' | ||
displayName: 'dotnet build' | ||
- task: DotNetCoreCLI@2 | ||
inputs: | ||
command: 'test' | ||
projects: 'test/DnsClient.Tests/*.csproj' | ||
publishTestResults: true | ||
arguments: '-c Release --no-build --no-restore' | ||
|
||
- script: 'dotnet pack src\DnsClient\DnsClient.csproj -c Release --no-build --no-restore --version-suffix $(versionSuffix) -v normal -o $(Build.ArtifactStagingDirectory)' | ||
name: 'PackBeta' | ||
displayName: 'dotnet pack for beta' | ||
- task: PublishBuildArtifacts@1 | ||
inputs: | ||
pathtoPublish: '$(Build.ArtifactStagingDirectory)' | ||
artifactName: 'beta' |
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
Oops, something went wrong.