2023-01-04 20:21:15 +03:00
|
|
|
# Copyright (c) 2023 Digital Asset (Switzerland) GmbH and/or its affiliates. All rights reserved.
|
2020-02-06 14:54:07 +03:00
|
|
|
# SPDX-License-Identifier: Apache-2.0
|
|
|
|
|
2019-05-14 15:25:02 +03:00
|
|
|
# Azure Pipelines file, see https://aka.ms/yaml
|
|
|
|
|
2019-06-14 02:12:06 +03:00
|
|
|
# Do not run on PRs
|
|
|
|
pr: none
|
2019-08-16 15:05:11 +03:00
|
|
|
|
2020-12-27 16:19:07 +03:00
|
|
|
# Do not run on merge to main
|
2019-06-14 02:12:06 +03:00
|
|
|
trigger: none
|
2019-08-16 15:05:11 +03:00
|
|
|
|
2019-06-14 02:12:06 +03:00
|
|
|
# Do run on a schedule (hourly)
|
2019-07-26 20:51:45 +03:00
|
|
|
#
|
2019-08-16 15:05:11 +03:00
|
|
|
# This is currently (2019-08-15) broken on Azure for GitHub-hosted repos. It
|
|
|
|
# does, however, work as expected for Azure-hosted repos. As a workaround, we
|
|
|
|
# have created a repo inside Azure that contains an `azure-pipelines.yml` file
|
|
|
|
# that just triggers this job.
|
|
|
|
#
|
|
|
|
# When the situation is resolved, delete that repo in Azure and uncomment the
|
|
|
|
# following. In the meantime, this should stay commented so we avoid running
|
|
|
|
# jobs twice when Azure fixes this issue.
|
|
|
|
#schedules:
|
|
|
|
#- cron: "0 * * * *"
|
|
|
|
# displayName: hourly cron
|
|
|
|
# branches:
|
|
|
|
# include:
|
2020-12-27 16:19:07 +03:00
|
|
|
# - main
|
2019-08-16 15:05:11 +03:00
|
|
|
# always: true
|
2019-05-14 15:25:02 +03:00
|
|
|
|
|
|
|
jobs:
|
2023-02-23 17:59:57 +03:00
|
|
|
- job: fix_bazel_cache
|
|
|
|
timeoutInMinutes: 120
|
|
|
|
pool:
|
|
|
|
name: 'ubuntu_20_04'
|
|
|
|
demands: assignment -equals default
|
|
|
|
steps:
|
|
|
|
- checkout: self
|
|
|
|
- bash: ci/dev-env-install.sh
|
|
|
|
displayName: 'Build/Install the Developer Environment'
|
2023-02-27 18:32:46 +03:00
|
|
|
- template: ci/bash-lib.yml
|
2023-02-23 17:59:57 +03:00
|
|
|
parameters:
|
|
|
|
var_name: bash-lib
|
|
|
|
- bash: |
|
|
|
|
set -euo pipefail
|
|
|
|
eval "$(dev-env/bin/dade assist)"
|
|
|
|
|
|
|
|
bazel build //ci/cron:cron
|
|
|
|
|
|
|
|
key=$(mktemp)
|
|
|
|
cleanup="rm -rf $key ~/.config/gcloud"
|
|
|
|
trap "$cleanup" EXIT
|
|
|
|
echo "$GCRED" > $key
|
|
|
|
gcloud auth activate-service-account --key-file=$key
|
|
|
|
export BOTO_CONFIG=/dev/null
|
|
|
|
./bazel-bin/ci/cron/cron bazel-cache --age 75 --delete --cache-suffix '**'
|
|
|
|
env:
|
|
|
|
GCRED: $(GOOGLE_APPLICATION_CREDENTIALS_CONTENT)
|
2023-02-27 18:32:46 +03:00
|
|
|
- template: ci/tell-slack-failed.yml
|
2022-11-15 16:07:41 +03:00
|
|
|
|
2023-11-06 19:58:23 +03:00
|
|
|
- job: docker_image
|
|
|
|
timeoutInMinutes: 60
|
|
|
|
pool:
|
|
|
|
name: 'ubuntu_20_04'
|
|
|
|
demands: assignment -equals default
|
|
|
|
steps:
|
|
|
|
- checkout: self
|
|
|
|
- bash: |
|
|
|
|
set -euo pipefail
|
|
|
|
|
|
|
|
eval "$(dev-env/bin/dade-assist)"
|
|
|
|
HEAD=$(git rev-parse HEAD)
|
|
|
|
while ! nix-build --no-out-link -A tools.sed -A tools.jq -A tools.curl -A tools.base64 nix; do :; done
|
|
|
|
|
|
|
|
trap 'rm -rf ~/.docker' EXIT
|
|
|
|
echo $DOCKER_PASSWORD | docker login --username $DOCKER_LOGIN --password-stdin
|
|
|
|
echo $DOCKER_CONTENT_TRUST_KEY | base64 -d > ~/.docker/da_automation.key
|
|
|
|
chmod 600 ~/.docker/da_automation.key
|
|
|
|
docker trust key load ~/.docker/da_automation.key --name $DOCKER_CONTENT_TRUST_USERNAME
|
|
|
|
|
|
|
|
RELEASES=$(curl https://api.github.com/repos/digital-asset/daml/releases -sSfL | jq -r '.[] | .tag_name')
|
|
|
|
DIR=$(pwd)
|
|
|
|
VERSIONS=$(curl 'https://hub.docker.com/v2/repositories/digitalasset/daml-sdk/tags/?page_size=10000' -sSfL)
|
|
|
|
# Our docker tags should be stable. Therefore, we only build the image if it has not already
|
|
|
|
# been built before and we checkout the Dockerfile for the release tag.
|
|
|
|
# We do not update docker images for older releases so only docker images for SDK releases
|
|
|
|
# >= 0.13.43 are built this way.
|
|
|
|
for version in $(echo $RELEASES | sed -e 's/ /\n/g'); do
|
|
|
|
LAST_UPDATE=$(echo $VERSIONS | jq -r '.results[] | select(.name == "'${version#v}'") | .last_updated')
|
|
|
|
if [[ -n "$LAST_UPDATE" ]]; then
|
|
|
|
echo "${version#v} already exists, skipping."
|
|
|
|
else
|
|
|
|
echo "Building version ${version#v}..."
|
|
|
|
#git checkout "$version"
|
|
|
|
cd ci/docker/daml-sdk
|
|
|
|
docker build -t digitalasset/daml-sdk:${version#v} --build-arg VERSION=${version#v} .
|
|
|
|
#git checkout Dockerfile
|
|
|
|
# Despite the name not suggesting it at all, this actually signs
|
|
|
|
# _and pushes_ the image; see
|
|
|
|
# https://docs.docker.com/engine/security/trust/#signing-images-with-docker-content-trust
|
|
|
|
docker trust sign digitalasset/daml-sdk:${version#v}
|
|
|
|
cd "$DIR"
|
|
|
|
git checkout $HEAD
|
|
|
|
echo "Done."
|
|
|
|
fi
|
|
|
|
done
|
|
|
|
env:
|
|
|
|
DOCKER_LOGIN: $(DOCKER_LOGIN)
|
|
|
|
DOCKER_PASSWORD: $(DOCKER_PASSWORD)
|
|
|
|
DOCKER_CONTENT_TRUST_KEY: $(DOCKER_CONTENT_TRUST_KEY)
|
|
|
|
DOCKER_CONTENT_TRUST_USERNAME: $(DOCKER_CONTENT_TRUST_USERNAME)
|
|
|
|
# Does not appear explicitly in the script, but is used by
|
|
|
|
# docker trust key load
|
|
|
|
DOCKER_CONTENT_TRUST_REPOSITORY_PASSPHRASE: $(DOCKER_CONTENT_TRUST_REPOSITORY_PASSPHRASE)
|
|
|
|
- template: ci/tell-slack-failed.yml
|
|
|
|
|
2019-06-27 01:48:19 +03:00
|
|
|
- job: vscode_marketplace
|
|
|
|
timeoutInMinutes: 10
|
|
|
|
pool:
|
2021-01-27 19:38:34 +03:00
|
|
|
name: 'ubuntu_20_04'
|
add default machine capability (#5912)
add default machine capability
We semi-regularly need to do work that has the potential to disrupt a
machine's local cache, rendering it broken for other streams of work.
This can include upgrading nix, upgrading Bazel, debugging caching
issues, or anything related to Windows.
Right now we do not have any good solution for these situations. We can
either not do those streams of work, or we can proceed with them and
just accept that all other builds may get affected depending on which
machine they get assigned to. Debugging broken nodes is particularly
tricky as we do not have any way to force a build to run on a given
node.
This PR aims at providing a better alternative by (ab)using an Azure
Pipelines feature called
[capabilities](https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/agents?view=azure-devops&tabs=browser#capabilities).
The idea behind capabilities is that you assign a set of tags to a
machine, and then a job can express its
[demands](https://docs.microsoft.com/en-us/azure/devops/pipelines/process/demands?view=azure-devops&tabs=yaml),
i.e. specify a set of tags machines need to have in order to run it.
Support for this is fairly badly documented. We can gather from the
documentation that a job can specify two things about a capability
(through its `demands`): that a given tag exists, and that a given tag
has an exact specified value. In particular, a job cannot specify that a
capability should _not_ be present, meaning we cannot rely on, say,
adding a "broken" tag to broken machines.
Documentation on how to set capabilities for an agent is basically
nonexistent, but [looking at the
code](https://github.com/microsoft/azure-pipelines-agent/blob/master/src/Microsoft.VisualStudio.Services.Agent/Capabilities/UserCapabilitiesProvider.cs)
indicates that they can be set by using a simple `key=value`-formatted
text file, provided we can find the right place to put this file.
This PR adds this file to our Linux, macOS and Windows node init scripts
to define an `assignment` capability and adds a demand for a `default`
value on each job. From then on, when we hit a case where we want a PR
to run on a specific node, and to prevent other PRs from running on that
node, we can manually override the capability from the Azure UI and
update the demand in the relevant YAML file in the PR.
CHANGELOG_BEGIN
CHANGELOG_END
2020-05-09 19:21:42 +03:00
|
|
|
demands: assignment -equals default
|
2019-06-27 01:48:19 +03:00
|
|
|
steps:
|
|
|
|
- checkout: self
|
|
|
|
- bash: |
|
|
|
|
set -euo pipefail
|
|
|
|
|
|
|
|
eval "$(dev-env/bin/dade-assist)"
|
|
|
|
|
|
|
|
AUTH=$(echo -n "OAuth:${MARKETPLACE_TOKEN}" | base64 -w0)
|
|
|
|
MARKET=$(curl -H "Authorization: Basic $AUTH" \
|
|
|
|
-H "Accept: application/json;api-version=5.0-preview.2" \
|
2021-05-03 16:11:30 +03:00
|
|
|
-sSfL \
|
2019-06-27 01:48:19 +03:00
|
|
|
"https://marketplace.visualstudio.com/_apis/gallery/publishers/DigitalAssetHoldingsLLC/extensions/daml?flags=1" \
|
|
|
|
| jq -r '.versions[0].version')
|
2020-04-30 16:10:30 +03:00
|
|
|
# This jq expression should ensure that we always upload the
|
|
|
|
# highest-number version. Here is how this works:
|
|
|
|
#
|
|
|
|
# 1. The GitHub API documentation does not specify the order for the
|
|
|
|
# "list releases" endpoint, but does specify that the "latest"
|
|
|
|
# endpoint returns the release that points to the most recent commit.
|
|
|
|
# Assuming the same sort order is applied for the list endpoint
|
|
|
|
# (which empirically seems to hold so far), this means that they may
|
|
|
|
# be out-of-order wrt version numbers, e.g. 1.1.0 may appear after
|
|
|
|
# 1.0.2.
|
|
|
|
# 2. The `.tag_name | .[1:] | split (".") | map(tonumber)` part will
|
|
|
|
# turn "v1.0.2" into an array [1, 0, 2].
|
|
|
|
# 3. jq documents its sort method to sort numbers in numeric order
|
|
|
|
# and arrays in lexical order (ascending in both cases).
|
|
|
|
#
|
|
|
|
# This is required because, while the VSCode Marketplace does show
|
|
|
|
# _a_ version number, it doesn't handle versions at all: we can only
|
|
|
|
# have one version on the marketplace at any given time, and any
|
|
|
|
# upload replaces the existing version.
|
2021-05-03 16:11:30 +03:00
|
|
|
GITHUB=$(curl https://api.github.com/repos/digital-asset/daml/releases -sSfL \
|
2020-04-30 17:40:08 +03:00
|
|
|
| jq -r '. | map(select(.prerelease == false)
|
2020-04-30 16:10:30 +03:00
|
|
|
| .tag_name
|
|
|
|
| .[1:]
|
|
|
|
| split (".")
|
|
|
|
| map(tonumber))
|
|
|
|
| sort
|
|
|
|
| reverse
|
|
|
|
| .[0]
|
|
|
|
| map(tostring)
|
|
|
|
| join(".")')
|
|
|
|
if [[ "$GITHUB" != "$MARKET" ]] && git merge-base --is-ancestor 798e96c9b9034eac85ace786b9e1955cf380285c v$GITHUB; then
|
2019-06-27 01:48:19 +03:00
|
|
|
echo "Publishing $GITHUB to VSCode Marketplace"
|
2020-04-30 16:10:30 +03:00
|
|
|
git checkout v$GITHUB
|
2022-01-17 16:40:42 +03:00
|
|
|
cp LICENSE compiler/daml-extension
|
|
|
|
trap "rm -rf $PWD/compiler/daml-extension/LICENSE" EXIT
|
2019-07-08 12:40:48 +03:00
|
|
|
cd compiler/daml-extension
|
2021-06-17 15:34:36 +03:00
|
|
|
sed -i "s/__VERSION__/$GITHUB/" package.json
|
2019-07-08 22:47:38 +03:00
|
|
|
# This produces out/src/extension.js
|
2022-01-17 16:40:42 +03:00
|
|
|
bazel run --run_under="cd $PWD &&" @nodejs//:yarn install
|
|
|
|
bazel run --run_under="cd $PWD &&" @nodejs//:yarn compile
|
2020-07-27 19:50:23 +03:00
|
|
|
bazel run --run_under="cd $PWD && " @daml_extension_deps//vsce/bin:vsce -- publish --yarn $GITHUB -p $MARKETPLACE_TOKEN
|
2019-06-27 01:48:19 +03:00
|
|
|
else
|
2020-04-30 16:10:30 +03:00
|
|
|
if [[ "$GITHUB" == "$MARKET" ]]; then
|
2019-06-27 01:48:19 +03:00
|
|
|
echo "Version on marketplace is already the latest ($GITHUB)."
|
|
|
|
else
|
|
|
|
echo "Latest version is not ready for marketplace publication."
|
|
|
|
fi
|
|
|
|
fi
|
|
|
|
env:
|
|
|
|
MARKETPLACE_TOKEN: $(VSCODE_MARKETPLACE_TOKEN)
|
2020-01-23 17:28:37 +03:00
|
|
|
- template: ci/tell-slack-failed.yml
|
2019-07-04 14:23:51 +03:00
|
|
|
|
|
|
|
- job: download_stats
|
|
|
|
timeoutInMinutes: 10
|
|
|
|
pool:
|
2021-01-27 19:38:34 +03:00
|
|
|
name: "ubuntu_20_04"
|
add default machine capability (#5912)
add default machine capability
We semi-regularly need to do work that has the potential to disrupt a
machine's local cache, rendering it broken for other streams of work.
This can include upgrading nix, upgrading Bazel, debugging caching
issues, or anything related to Windows.
Right now we do not have any good solution for these situations. We can
either not do those streams of work, or we can proceed with them and
just accept that all other builds may get affected depending on which
machine they get assigned to. Debugging broken nodes is particularly
tricky as we do not have any way to force a build to run on a given
node.
This PR aims at providing a better alternative by (ab)using an Azure
Pipelines feature called
[capabilities](https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/agents?view=azure-devops&tabs=browser#capabilities).
The idea behind capabilities is that you assign a set of tags to a
machine, and then a job can express its
[demands](https://docs.microsoft.com/en-us/azure/devops/pipelines/process/demands?view=azure-devops&tabs=yaml),
i.e. specify a set of tags machines need to have in order to run it.
Support for this is fairly badly documented. We can gather from the
documentation that a job can specify two things about a capability
(through its `demands`): that a given tag exists, and that a given tag
has an exact specified value. In particular, a job cannot specify that a
capability should _not_ be present, meaning we cannot rely on, say,
adding a "broken" tag to broken machines.
Documentation on how to set capabilities for an agent is basically
nonexistent, but [looking at the
code](https://github.com/microsoft/azure-pipelines-agent/blob/master/src/Microsoft.VisualStudio.Services.Agent/Capabilities/UserCapabilitiesProvider.cs)
indicates that they can be set by using a simple `key=value`-formatted
text file, provided we can find the right place to put this file.
This PR adds this file to our Linux, macOS and Windows node init scripts
to define an `assignment` capability and adds a demand for a `default`
value on each job. From then on, when we hit a case where we want a PR
to run on a specific node, and to prevent other PRs from running on that
node, we can manually override the capability from the Azure UI and
update the demand in the relevant YAML file in the PR.
CHANGELOG_BEGIN
CHANGELOG_END
2020-05-09 19:21:42 +03:00
|
|
|
demands: assignment -equals default
|
2019-07-04 14:23:51 +03:00
|
|
|
steps:
|
|
|
|
- checkout: self
|
|
|
|
- bash: |
|
|
|
|
set -euo pipefail
|
|
|
|
|
|
|
|
eval "$(dev-env/bin/dade-assist)"
|
|
|
|
|
|
|
|
STATS=$(mktemp)
|
2021-05-03 16:11:30 +03:00
|
|
|
curl https://api.github.com/repos/digital-asset/daml/releases -sSfL | gzip -9 > $STATS
|
2019-07-04 14:23:51 +03:00
|
|
|
|
|
|
|
GCS_KEY=$(mktemp)
|
2019-09-24 14:02:29 +03:00
|
|
|
cleanup () {
|
|
|
|
rm -f $GCS_KEY
|
|
|
|
}
|
|
|
|
trap cleanup EXIT
|
2019-07-04 14:23:51 +03:00
|
|
|
echo "$GOOGLE_APPLICATION_CREDENTIALS_CONTENT" > $GCS_KEY
|
|
|
|
gcloud auth activate-service-account --key-file=$GCS_KEY
|
|
|
|
BOTO_CONFIG=/dev/null gsutil cp $STATS gs://daml-data/downloads/$(date -u +%Y%m%d_%H%M%SZ).json.gz
|
|
|
|
env:
|
|
|
|
GOOGLE_APPLICATION_CREDENTIALS_CONTENT: $(GOOGLE_APPLICATION_CREDENTIALS_CONTENT)
|
2020-01-23 17:28:37 +03:00
|
|
|
- template: ci/tell-slack-failed.yml
|
2023-06-13 18:36:32 +03:00
|
|
|
|
|
|
|
- template: ci/refresh-get-daml-com.yml
|
2023-11-23 10:54:35 +03:00
|
|
|
|
|
|
|
- job: build_canton_3x_with_bazel
|
|
|
|
timeoutInMinutes: 120
|
|
|
|
pool:
|
|
|
|
name: 'ubuntu_20_04'
|
|
|
|
demands: assignment -equals default
|
|
|
|
steps:
|
|
|
|
- checkout: self
|
2023-11-27 16:08:07 +03:00
|
|
|
- bash: |
|
|
|
|
set -euo pipefail
|
2023-11-27 18:44:43 +03:00
|
|
|
git fetch
|
|
|
|
git checkout origin/main
|
2023-11-27 16:08:07 +03:00
|
|
|
ci/build-canton-3x.sh
|
2023-11-23 10:54:35 +03:00
|
|
|
env:
|
|
|
|
GITHUB_TOKEN: $(CANTON_READONLY_TOKEN)
|
|
|
|
- template: ci/tell-slack-failed.yml
|