Commit Graph

290 Commits

Author SHA1 Message Date
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
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
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
Gary Verhaegen
92fcbb6a3b
remove canton ee integration (#18501) 2024-02-16 13:30:55 +01:00
Gary Verhaegen
17f37c7d23
cron: new canton snapshot format (#18483) 2024-02-15 14:31:06 +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
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
Gary Verhaegen
939e2240cf
smaller title/branch name for canton update PRs (#18265) 2024-01-25 13:37:54 +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
Paul Brauner
c6cf5b787b
Only drop canton3 code into canton on main (#18204) 2024-01-17 18:38:45 +01:00
Gary Verhaegen
73f4cdd5bd
don't run update_canton on run-full-compat PRs (#18196) 2024-01-16 20:42:26 +01:00
Gary Verhaegen
1c8cbb7c05
daily: fix report (#18191) 2024-01-16 14:41:26 +00:00
Gary Verhaegen
fd0494fe41
canton bump pr: better branch name (#18190) 2024-01-16 14:06:51 +01:00
Gary Verhaegen
179d85362d
update copyright (#18167)
* update copyright

* undo hack from #18168

* update hash in platform-independence-pre-check
2024-01-15 20:27:42 +01:00
Gary Verhaegen
2e28102699
ci/cron/daily: fix typo (#18176) 2024-01-15 18:02:22 +01:00
Gary Verhaegen
1168e35455
run more things on main-2.x (#18154)
Specifically:

- m1 builds
- BlackDuck & notices bump
- daily compatibility tests
- daily compat update (if needed)
- daily perf test & report

Also, merge the canton update jobs as that makes a lot more sense at
this point. Future divergences can be expressed by changing the files in
their respective branches.

This PR will need to be backported to main-2.x to fully take effect.
2024-01-12 21:05:47 +01:00
Paul Brauner
bef1938a21
fix calls to open_pr (#18129) 2024-01-10 16:57:05 +01:00
Paul Brauner
489916a1e2
Fix the canton-2.x code drop (#18125)
When deciding whether it's worth creating a PR, diff against the main-2.x branch, not the main one.
2024-01-10 14:19:55 +00:00
Paul Brauner
2a77ae5d0d
Use different branch names for the two code drops (#18120)
The code drop task targeting main-2.x uses the same feature branch name for its PR as the task targeting main. First one wins. This PR fixes that.
2024-01-10 10:30:51 +01:00
Paul Brauner
54009a41e6
also code drop on main-2.x (#18111) 2024-01-09 18:20:53 +01:00
Gary Verhaegen
d48f3130ea
tell team-canton-notifications on canton update failures (#18086) 2024-01-04 19:07:31 +01:00
Remy
ea4085bd28
do not build canton as separate task (#18058) 2023-12-21 09:47:48 +01:00
Paul Brauner
56018b5d6e
do a proper canton 3.x code drop in the canton-3x directory (#17980)
* do a proper canton 3.x code drop in the canton-3x directory

* copy the code from canton3

* address Gary's comments

* fix canton-3x
2023-12-06 10:47:47 +01:00
Paul Brauner
1794212369
build canton 3x in the CI (#17966)
* build canton 3.x in build.yml

* Apply suggestions from code review

Co-authored-by: Gary Verhaegen <gary.verhaegen@digitalasset.com>

* Apply suggestions from code review

Co-authored-by: Gary Verhaegen <gary.verhaegen@digitalasset.com>

* apply suggestions

---------

Co-authored-by: Gary Verhaegen <gary.verhaegen@digitalasset.com>
2023-12-05 15:18:35 +00:00
Paul Brauner
ca31b1beab
restrict code drop and canton jars to 2.x (#17882) 2023-11-22 11:19:22 +01:00
Paul Brauner
f7dd1e6124
Stop downloading the canton opensource jar (#17877)
* stop downloading the canton opensource jar

* udpate obsolete README

* fix one remaining mention of @canton

* remove all mentions of canton_dep.bzlP
2023-11-22 08:36:41 +00:00
Gary Verhaegen
444536ba24
fix daily canton bump (#17781) 2023-11-08 16:30:00 +00:00
Remy
44169064ea
fix update_canton_ jobs (#17762) 2023-11-07 11:51:45 +01:00
Remy
dc0b2f71a6
mege bump_canton and update_canton_sources jobs (#17757) 2023-11-06 17:37:31 +01:00
Remy
91b965bd8c
add readme to canton code drop (#17560) 2023-10-16 12:59:20 +02:00
Gary Verhaegen
4a84d2de3c
canton_drop: fix canton credentials (#17551) 2023-10-11 16:13:26 +00:00
Remy
0823af627e
fix name of canton update job (#17544) 2023-10-11 13:12:13 +02:00
Remy
1f31feac2b
Code drop of canton community (#17540)
Co-authored-by: Gary Verhaegen <gary.verhaegen@digitalasset.com>
2023-10-10 11:29:37 +00:00
Remy
623f305e9c
Move canton directory to let place for code drop (#17506) 2023-09-29 14:37:01 +00:00
Gary Verhaegen
33929d12ae
fix canton bump (#17494)
We've got a few failures recently that report not having delete access
on GCS. This should address those.
2023-09-27 15:22:44 +02:00
azure-pipelines[bot]
7d74dc0aa9
bump canton to 2.8.0-snapshot.20230919.11183.0.v52763301 (#17457)
* bump canton to 2.8.0-snapshot.20230919.11183.0.v52763301

CHANGELOG_BEGIN
CHANGELOG_END

* fix canton url

---------

Co-authored-by: Azure Pipelines Daml Build <support@digitalasset.com>
Co-authored-by: Gary Verhaegen <gary.verhaegen@digitalasset.com>
2023-09-20 18:39:59 +02:00
Gary Verhaegen
3d08291ae6
fix typo in bump-canton job (#17435) 2023-09-19 10:36:14 +00:00
Gary Verhaegen
82655f2f29
keep stable copies of Canton artifacts (#17415) 2023-09-18 18:16:24 +02:00
Gary Verhaegen
2dbfb68080
fix BlackDuck scan (#17400)
The latest udpate of the BlackDuck script broke our run. In order to get
a successful scan tomorrow, this PR:

- Pins us back on yesterday's script version, and
- Adds an auto-update mechanism.

This way, we get to stay reasonably up-to-date with automated update
PRs, but we also get to choose when we upgrade.
2023-09-14 16:29:39 -04:00
Gary Verhaegen
675a325cd3
fix Linux cache (macOS still seems broken) (#17369) 2023-09-06 21:21:56 +02:00
Gary Verhaegen
a87818464e
fix bazel cache use on CI (#17363) 2023-09-05 16:51:18 +00:00
Gary Verhaegen
d03ffb0329
fix bump_canton (#17166) 2023-07-24 13:19:05 +02:00