digital-asset/daml
1
1
Fork 0
mirror of https://github.com/digital-asset/daml.git synced 2024-09-19 16:57:40 +03:00
Code Issues Projects Releases Wiki Activity
a0573b1228
daml/ci/build-unix.yml

60 lines
1.9 KiB
YAML
Raw Normal View History

push releases to github (#413) Azure Pipelines has direct integration with GitHub, so we're just using that. Releases on GitHub have to target a tag, so we also need to push the tag as an intermediate step; we also need to include the platform name in the artifact to avoid overwriting from different builds. The two "GitHub release" steps depend on two Azure variables that are not defined in the pipeline script. This may look like it should not work, but in fact it does, because these variables are set by the release script. In Azure Pipelines, any build step can set variables for the next build steps by outputting specially-formatted text to stdout. This text will not appear in the build output displayed by Azure Pipelines, e.g.: ``` echo '##vso[task.setvariable variable=sauce]tomatoes' ``` would define the Azure variable `sauce` to have the string `tomatoes` as its value for the next build steps. See [0] for details. [0]: https://docs.microsoft.com/en-us/azure/devops/pipelines/process/variables?view=azure-devops&tabs=yaml%2Cbatch#set-in-script
2019-04-12 13:30:13 +03:00
parameters:
name: ''
open-sourcing daml
2019-04-04 11:33:38 +03:00
steps:
- checkout: self
ci: restore caching on non-forks
2019-04-04 14:03:56 +03:00
- bash: ci/dev-env-install.sh
Update ci/build-unix.yml Co-Authored-By: zimbatm <zimbatm@zimbatm.com>
2019-04-04 15:48:52 +03:00
displayName: 'Build/Install the Developer Environment'
open-sourcing daml
2019-04-04 11:33:38 +03:00
- bash: |
source dev-env/lib/ensure-nix
ci: restore caching on non-forks
2019-04-04 14:03:56 +03:00
ci/dev-env-push.py
displayName: 'Push Developer Environment build results'
condition: eq(variables['System.PullRequest.IsFork'], 'False')
open-sourcing daml
2019-04-04 11:33:38 +03:00
env:
# to upload to the Nix cache
GOOGLE_APPLICATION_CREDENTIALS_CONTENT: $(GOOGLE_APPLICATION_CREDENTIALS_CONTENT)
NIX_SECRET_KEY_CONTENT: $(NIX_SECRET_KEY_CONTENT)
fmt.sh: format and lint checks (#349) * load dev-env in ./build.sh one less thing for the user to do * fmt.sh: extract platform-agnostic checks
2019-04-10 15:22:35 +03:00
- bash: ./fmt.sh --test
displayName: 'Platform-agnostic lints and checks'
condition: eq(variables['Agent.OS'], 'Linux')
Windows CI (#364) * ci: remove the old Jenkins files * WORKSPACE: remove unuset this_breaks_windows * ci: add Windows builds to Azure Pipeline
2019-04-11 15:26:55 +03:00
- bash: ci/configure-bazel.sh
displayName: 'Configure Bazel'
open-sourcing daml
2019-04-04 11:33:38 +03:00
env:
Fix IS_FORK variable (#246) Without this PR, this variable ends up being set to the string "variables['System.PullRequest.IsFork']" which meant that we never uploaded to the Bazel cache.
2019-04-05 15:24:23 +03:00
IS_FORK: $(System.PullRequest.IsFork)
open-sourcing daml
2019-04-04 11:33:38 +03:00
# to upload to the bazel cache
GOOGLE_APPLICATION_CREDENTIALS_CONTENT: $(GOOGLE_APPLICATION_CREDENTIALS_CONTENT)
Windows CI (#364) * ci: remove the old Jenkins files * WORKSPACE: remove unuset this_breaks_windows * ci: add Windows builds to Azure Pipeline
2019-04-11 15:26:55 +03:00
- bash: ./build.sh "_$(uname)"
displayName: 'Build'
open-sourcing daml
2019-04-04 11:33:38 +03:00
- task: PublishBuildArtifacts@1
condition: succeededOrFailed()
inputs:
pathtoPublish: '$(Build.ArtifactStagingDirectory)'
artifactName: 'Bazel execution logs'
- bash: ci/release.sh
displayName: 'Release'
fix release pipeline (#499) 1. Only try to release if all tests have passed 2. Specifically push build product, rather than entire worktree
2019-04-15 19:01:53 +03:00
condition: and(succeeded(),
eq(variables['System.PullRequest.IsFork'], 'False'))
open-sourcing daml
2019-04-04 11:33:38 +03:00
env:
# to connect to bintray
JFROG_CONFIG_CONTENT: $(JFROG_CONFIG_CONTENT)
include artifacts in github releases (#487)
2019-04-15 15:54:04 +03:00
name: release
push releases to github (#413) Azure Pipelines has direct integration with GitHub, so we're just using that. Releases on GitHub have to target a tag, so we also need to push the tag as an intermediate step; we also need to include the platform name in the artifact to avoid overwriting from different builds. The two "GitHub release" steps depend on two Azure variables that are not defined in the pipeline script. This may look like it should not work, but in fact it does, because these variables are set by the release script. In Azure Pipelines, any build step can set variables for the next build steps by outputting specially-formatted text to stdout. This text will not appear in the build output displayed by Azure Pipelines, e.g.: ``` echo '##vso[task.setvariable variable=sauce]tomatoes' ``` would define the Azure variable `sauce` to have the string `tomatoes` as its value for the next build steps. See [0] for details. [0]: https://docs.microsoft.com/en-us/azure/devops/pipelines/process/variables?view=azure-devops&tabs=yaml%2Cbatch#set-in-script
2019-04-12 13:30:13 +03:00
- bash: |
include artifacts in github releases (#487)
2019-04-15 15:54:04 +03:00
set -euo pipefail
ARTIFACT=daml-sdk-$(release_tag)-${{ parameters.name }}
cp bazel-genfiles/release/sdk-release-tarball.tar.gz $(Build.StagingDirectory)/$ARTIFACT
echo "##vso[task.setvariable variable=artifact;isOutput=true]$ARTIFACT"
name: publish
condition: eq(variables['release.has_released'], 'true')
- task: PublishPipelineArtifact@0
condition: eq(variables['release.has_released'], 'true')
push releases to github (#413) Azure Pipelines has direct integration with GitHub, so we're just using that. Releases on GitHub have to target a tag, so we also need to push the tag as an intermediate step; we also need to include the platform name in the artifact to avoid overwriting from different builds. The two "GitHub release" steps depend on two Azure variables that are not defined in the pipeline script. This may look like it should not work, but in fact it does, because these variables are set by the release script. In Azure Pipelines, any build step can set variables for the next build steps by outputting specially-formatted text to stdout. This text will not appear in the build output displayed by Azure Pipelines, e.g.: ``` echo '##vso[task.setvariable variable=sauce]tomatoes' ``` would define the Azure variable `sauce` to have the string `tomatoes` as its value for the next build steps. See [0] for details. [0]: https://docs.microsoft.com/en-us/azure/devops/pipelines/process/variables?view=azure-devops&tabs=yaml%2Cbatch#set-in-script
2019-04-12 13:30:13 +03:00
inputs:
fix release pipeline (#499) 1. Only try to release if all tests have passed 2. Specifically push build product, rather than entire worktree
2019-04-15 19:01:53 +03:00
targetPath: $(Build.StagingDirectory)/$(publish.artifact)
include artifacts in github releases (#487)
2019-04-15 15:54:04 +03:00
artifactName: $(publish.artifact)
Reference in New Issue Copy Permalink