Gary Verhaegen
f31b183447
[release] experiment with faster Windows too ( #18869 )
2024-03-26 14:04:46 +01:00
Gary Verhaegen
5e4615bf7c
[release] fix release detection logic ( #18867 )
2024-03-26 12:38:03 +01:00
Gary Verhaegen
acdb297096
[release] fix next step in release ( #18849 )
2024-03-24 18:35:27 +01:00
Gary Verhaegen
6a978927f5
[3.0] fix split_release job ( #18848 )
2024-03-23 14:50:08 +00:00
Gary Verhaegen
d0b5a13c0b
fix release process ( #18829 )
2024-03-23 11:19:52 +01:00
Gary Verhaegen
483bfc9a1c
fix hourly cron: docker ( #18830 )
2024-03-23 11:08:46 +01:00
Gary Verhaegen
e33114bd4e
[cron] fix daily for subdir move ( #18819 )
2024-03-22 23:47:52 +01:00
Gary Verhaegen
dd4c6ba9ad
[release] faster releases - experiment ( #18831 )
...
When we build a release, it is always a "past" commit - typically, one
that has already been tested twice: once when the corresponding PR was
run, and then again as a "main"-branch commit.
Release branches don't run, but their protection rules enforce linear
merges.
Either way, we know we're building a _good_ commit, and, assuming our
builds and tests are hermetic, testing that commit again when we make a
release is a pure waste of time and CPU resources.
The other case, where we make an ad-hoc release from a branch that has
not been merged, has a similar issue: we do not necessarily want to run
the full test suite, because part of the reason we need that commit may
be that it doesn't succeed as is.
Based on that observation, I wondered what might be the minimal set of
things we actually need to build when making a release. This PR is an
experiment in trying to find that out.
2024-03-22 23:47:34 +01:00
Gary Verhaegen
5d0d5027ff
cleanup: remove unused credentials ( #18814 )
2024-03-22 16:43:39 +01:00
Gary Verhaegen
77e7258ac1
subdir: fix hourly cron ( #18826 )
2024-03-22 16:12:33 +01:00
Gary Verhaegen
e40aad897f
move to subdir 3.0 ( #18520 )
...
* move most files
* update CI configuration
2024-03-22 02:27:46 +01:00
Gary Verhaegen
17119166ab
[release] tell commit sha to canton ( #18800 )
2024-03-20 15:45:54 +00:00
Gary Verhaegen
41d0265f16
[sync] fix canton pull ( #18789 )
2024-03-19 10:40:56 +01:00
Gary Verhaegen
e0963a7cd4
[sync] fix canton pull ( #18781 )
2024-03-18 18:17:52 +00:00
Gary Verhaegen
b08c7b2bb4
[sync] any canton we want ( #18780 )
...
This PR moves the whole "update canton" logic to a script anyone can run
locally, and changes it to be able to get any canton commit we want, or
possibly any dirty local workdir.
2024-03-18 17:17:20 +01:00
Stefano Baghino
0d8b4d8553
Remove @stefanobaghino-da ( #18758 )
2024-03-15 08:56:09 +00:00
Gary Verhaegen
55a5b6d18c
[daily] fix compatibility matrix update ( #18752 )
2024-03-14 16:16:25 +00:00
Gary Verhaegen
3071720dfe
[release] update check-releases to work with ARM workaround ( #18749 )
2024-03-14 16:52:06 +01:00
Moisés Ackerman
dca4b98ddf
Switch {akrmn=>moisesackerman-da} github user ( #18730 )
2024-03-13 13:17:14 +01:00
Gary Verhaegen
1938d516c0
[release] try to fix 2.x arm again ( #18710 )
2024-03-11 23:58:00 +01:00
Gary Verhaegen
4c82f93a5f
[release] fix split-release step name ( #18707 )
2024-03-11 14:36:21 +00:00
Gary Verhaegen
504b2c1cac
[release] skip arm on 2.8 and earlier ( #18705 )
2024-03-11 14:52:53 +01:00
Gary Verhaegen
1e671b6356
try to fix release branches ( #18693 )
...
Right now building Linux/ARM fails on release branches. This is because:
- Release branches do not support Linux/ARM.
- Releases are built from `main`, using `main`'s version of YAML files.
This should skip over the Linux/ARM build when running on release
branches.
2024-03-11 12:16:33 +01:00
Gary Verhaegen
5a85f72b09
re-enable macOS ( #18700 )
...
This reverts commit 8f2e425b0b
2024-03-11 10:58:22 +01:00
Gary Verhaegen
8f2e425b0b
disable macOS over the weekend ( #18659 )
2024-03-08 19:15:31 +01:00
Gary Verhaegen
b978f97970
fix check-protobuf-stability ( #18682 )
...
Currently fails in the presence of release candidates.
2024-03-08 18:22:09 +01:00
azure-pipelines[bot]
6b63b00786
bump blackduck script to 13991807 ( #18676 )
...
Co-authored-by: Azure Pipelines Daml Build <support@digitalasset.com>
2024-03-08 15:36:54 +01:00
Moisés Ackerman
41e4848eb1
Make CI steps 'publish_npm_mvn', 'publish' and 'PublishPipelineArtifact@0' only run on 'main{,-2.x}' ( #18620 )
...
This is a partial revert of https://github.com/digital-asset/daml/pull/18597 , which removed the condition 'in(variables['Build.SourceBranchName'], 'main', 'main-2.x')' from those steps
2024-03-01 15:19:21 +01:00
Gary Verhaegen
8b8e95d0e0
[release] push to maven again ( #18597 )
2024-02-28 17:37:30 +01:00
Gary Verhaegen
888a639953
fix release script again ( #18582 )
2024-02-27 01:08:15 +01:00
Gary Verhaegen
ecea0e12a4
try to fix release script for arm addition ( #18577 )
2024-02-26 15:17:33 +01:00
Gary Verhaegen
261a405b50
build on linux arm ( #18484 )
2024-02-25 15:43:12 +01:00
Gary Verhaegen
39f0c5c6c8
fix blackduck script update ( #18557 )
...
This job runs on both `main` and `main-2.x`, and generates the same
branch name. This results in only the first of the two that runs
generating a PR.
With this change the branch name will be different so when an update is
needed we'll update both on the same day.
2024-02-22 19:03:04 +01:00
Gary Verhaegen
92fcbb6a3b
remove canton ee integration ( #18501 )
2024-02-16 13:30:55 +01:00
Remy
190eefe266
rationalize transaction proto ( #18490 )
2024-02-16 08:49:00 +01:00
Gary Verhaegen
17f37c7d23
cron: new canton snapshot format ( #18483 )
2024-02-15 14:31:06 +01:00
Gary Verhaegen
b9b3c16fbf
check if m1 became more stable ( #18476 )
2024-02-15 12:00:15 +01:00
Gary Verhaegen
ce46fec9ac
remove infra folder ( #18378 )
...
Moved to DACH-NY/daml-ci.
2024-02-02 14:51:21 +01:00
Paul Brauner
d18d501204
fix dangling curly brace in code drop code, remove call to function that doesn't exist anymore ( #18347 )
2024-01-31 14:13:44 +00:00
Paul Brauner
9c4cccc9d3
add copy canton script ( #18329 )
...
* add copy canton script
* cleanup
* remove old comments
* make sure the script runs from anywhere
2024-01-31 13:03:39 +00:00
Gary Verhaegen
6207e2ef80
tweak release notification ( #18343 )
2024-01-31 12:55:06 +01:00
Gary Verhaegen
c720361b7b
check-releases: fix typo ( #18324 )
2024-01-30 10:31:30 +01:00
Gary Verhaegen
5f7f9784a4
check-releases: record verified releases ( #18313 )
...
With the current setup, every single day we download every single
artifact of evry single release we've ever made on GitHub, twice (once
from GitHub, once from GCS). Then we check signatures and compare the
two.
With this change, we save a representation of the state of both GCS and
GitHub, and if that representation hasn't changed, we assume the
artifacts haven't changed either. The assumption seems reasonable to me
as the representation includes platform timestamps, which no user can
tamper with as far as I'm aware.
Note: we do not save the entire GitHub release representation, and
instead just save relevant metadata for the associated artifacts. The
goal of this job is to verify that the artifacts haven't changed; it is
acceptable (and even expected in routine circumstances) that the
release description will change, as well as its "prerelease" and "latest
release" flags.
2024-01-29 16:18:37 +01:00
Gary Verhaegen
c590c6c942
fix daily report ( #18309 )
...
broken by #18203
2024-01-29 12:24:18 +00:00
azure-pipelines[bot]
e82166fe7b
bump blackduck script to 745a1566 ( #18292 )
...
Co-authored-by: Azure Pipelines Daml Build <support@digitalasset.com>
2024-01-26 09:55:37 +01:00
Gary Verhaegen
939e2240cf
smaller title/branch name for canton update PRs ( #18265 )
2024-01-25 13:37:54 +01:00
azure-pipelines[bot]
7ec33db439
update canton to 20240123.12376.0.vce2030db/3.0.0-snapshot.20240123.12376.0.vce2030db ( #18256 )
...
* update canton to 20240123.12376.0.vce2030db/3.0.0-snapshot.20240123.12376.0.vce2030db
tell-slack: canton
* Resolve import warnings
* Add ledger-api v2 experimental_features proto
to adapt to https://github.com/DACH-NY/canton/pull/16603/files#diff-3b3a96cb2f2ad9cfe33444f1327479d8d0ca48663fb7dd0a6a5e53c5d86afede
* Removing compatiblity_target_protobuf
as the corresponding compatibility change would move into the
canton repo as per https://github.com/DACH-NY/canton/issues/16637
---------
Co-authored-by: Azure Pipelines Daml Build <support@digitalasset.com>
Co-authored-by: oliverse-da <oliver.seeliger@digitalasset.com>
2024-01-24 14:26:56 +01:00
Gary Verhaegen
0b9c7faad2
fix external PRs ( #18251 )
2024-01-23 17:42:31 +01:00
Paul Brauner
6393fd084c
Remove LF1 in the compiler ( #18203 )
...
* make lf v2 and daml3-script the default
* delete V1 integration tests
* Remove LF major version V1 from the compiler
run-all-tests: true
* fix security evidence
* fix //compiler/damlc/tests:damlc-test
* fix //compiler/damlc/tests:data-dependencies
* fix //compiler/damlc/tests:integration-v2*
* fix //compiler/damlc/tests:packaging
* fix //compiler/damlc/tests:platform-independence-dar-hash-file-matches
* fix //compiler/damlc/tests:stable-packages
* fix DarReaderTest.scala
* fix DecodeCommonSpec.scala
* fix //daml-lf/archive:proto_immutability_check
* fix DamlLfEncoderTest.scala
* fix //language-support/java/codegen:test
* fix //daml-assistant/integration-tests:integration-tests
* fix artifacts.yaml
run-all-tests: true
run-full-compat: true
* Disable scenario-perf for now
See https://github.com/digital-asset/daml/pull/18217 .
run-all-tests: true
run-full-compat: true
* restore explicit target version in docs template
run-all-tests: true
run-full-compat: true
* Restore DamlLfEncoderTest.scala.
Introduce a ENGINE_LF_VERSIONS constant in daml-lf.bzl instead.
run-all-tests: true
run-full-compat: true
* delete daml-lf/scenario-interpreter/src/perf
run-all-tests: true
run-full-compat: true
* Address review comments.
* Apply
Co-authored-by: Moisés Ackerman <6054733+akrmn@users.noreply.github.com>
* Restore golden/BUILD.bazel and port to 2.1
run-all-tests: true
run-full-compat: true
---------
Co-authored-by: Moisés Ackerman <6054733+akrmn@users.noreply.github.com>
2024-01-19 15:19:34 +00:00
Gary Verhaegen
39ea58901e
fix daily test report ( #18215 )
2024-01-18 14:05:27 +00:00
