maxmustermann/PowerShell
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity
PowerShell/.vsts-ci/templates/install-ps-phase.yml

34 lines
854 B
YAML
Raw Normal View History

Make `install-powershell.sh` autodetect if it should use `wget` or `curl` (#8225) install-powershell.sh now autodetects whether curl or wget is installed to download secondary script when it is not found locally.
2018-11-14 19:45:52 +01:00
parameters:
pool: 'Hosted Ubuntu 1604'
jobName: 'none'
scriptName: ''
Make install scripts more consistent over different operating systems (#9071) I noticed a couple of inconsistencies when reading through the install bash scripts. - Make documentation for switches consistent over all files. - Replace all `sed` implementations of `lowercase` with a more maintainable `tr` implementation. - Set the `OS` variable in every install script, making it so previously unused checks are actually used. - Exit with a non-zero exit code when the script reaches an illegal state. ## PR Context A lot of people, including myself, read the install scripts before executing them. While doing so I noticed they contained inconsistencies. For example, certain flags you can pass to the install script were either undocumented or had an incorrect description. This PR fixes some of these inconsistencies, which should make them easier to maintain and easier to read. Co-authored-by: Travis Plunk <github@ez13.net>
2019-03-08 22:00:04 +01:00
container: ''
Make `install-powershell.sh` autodetect if it should use `wget` or `curl` (#8225) install-powershell.sh now autodetects whether curl or wget is installed to download secondary script when it is not found locally.
2018-11-14 19:45:52 +01:00
jobs:
Make install scripts more consistent over different operating systems (#9071) I noticed a couple of inconsistencies when reading through the install bash scripts. - Make documentation for switches consistent over all files. - Replace all `sed` implementations of `lowercase` with a more maintainable `tr` implementation. - Set the `OS` variable in every install script, making it so previously unused checks are actually used. - Exit with a non-zero exit code when the script reaches an illegal state. ## PR Context A lot of people, including myself, read the install scripts before executing them. While doing so I noticed they contained inconsistencies. For example, certain flags you can pass to the install script were either undocumented or had an incorrect description. This PR fixes some of these inconsistencies, which should make them easier to maintain and easier to read. Co-authored-by: Travis Plunk <github@ez13.net>
2019-03-08 22:00:04 +01:00
Make `install-powershell.sh` autodetect if it should use `wget` or `curl` (#8225) install-powershell.sh now autodetects whether curl or wget is installed to download secondary script when it is not found locally.
2018-11-14 19:45:52 +01:00
- job: ${{ parameters.jobName }}
variables:
scriptName: ${{ parameters.scriptName }}
Make install scripts more consistent over different operating systems (#9071) I noticed a couple of inconsistencies when reading through the install bash scripts. - Make documentation for switches consistent over all files. - Replace all `sed` implementations of `lowercase` with a more maintainable `tr` implementation. - Set the `OS` variable in every install script, making it so previously unused checks are actually used. - Exit with a non-zero exit code when the script reaches an illegal state. ## PR Context A lot of people, including myself, read the install scripts before executing them. While doing so I noticed they contained inconsistencies. For example, certain flags you can pass to the install script were either undocumented or had an incorrect description. This PR fixes some of these inconsistencies, which should make them easier to maintain and easier to read. Co-authored-by: Travis Plunk <github@ez13.net>
2019-03-08 22:00:04 +01:00
${{ if ne(parameters.container, '') }}:
container: ${{ parameters.container }}
pool: ${{ parameters.pool }}
Make `install-powershell.sh` autodetect if it should use `wget` or `curl` (#8225) install-powershell.sh now autodetects whether curl or wget is installed to download secondary script when it is not found locally.
2018-11-14 19:45:52 +01:00
displayName: ${{ parameters.jobName }}
steps:
- powershell: |
Get-ChildItem -Path env:
displayName: Capture environment
condition: succeededOrFailed()
- powershell: Write-Host "##vso[build.updatebuildnumber]$env:BUILD_SOURCEBRANCHNAME-$env:BUILD_SOURCEVERSION-$((get-date).ToString("yyyyMMddhhmmss"))"
displayName: Set Build Name for Non-PR
condition: ne(variables['Build.Reason'], 'PullRequest')
- bash: |
$(scriptName)
displayName: Run Script - $(scriptName)
condition: succeededOrFailed()
Reference in a new issue Copy permalink