digital-asset/daml
1
1
Fork 0
mirror of https://github.com/digital-asset/daml.git synced 2024-11-09 15:37:05 +03:00
Code Issues Projects Releases Wiki Activity
d54971aacd
daml/ci/cron/tuesday.yml

36 lines
1.0 KiB
YAML
Raw Normal View History

update copyright (#18167) * update copyright * undo hack from #18168 * update hash in platform-independence-pre-check
2024-01-15 22:27:42 +03:00
# Copyright (c) 2024 Digital Asset (Switzerland) GmbH and/or its affiliates. All rights reserved.
announce release rotation on Tuesday (#7151) It's been pointed out to me that some people actually plan their work, and for them, it would be useful to know at least a day in advance that they will be doing a release. This PR attempts to accommodate that. Note: this will run as a new, separate cron. I'll do the Azure setup after this gets approved. CHANGELOG_BEGIN CHANGELOG_END
2020-08-17 14:42:35 +03:00
# SPDX-License-Identifier: Apache-2.0
pr: none
trigger: none
schedules:
- cron: "0 6 * * Tue"
displayName: Tuesday
branches:
include:
rename master to main (#8245) As we strive for more inclusiveness, we are becoming less comfortable with historically-charged terms being used in our everyday work. This is targeted for merge on Dec 26, _after_ the necessary corresponding changes at both the GitHub and Azure Pipelines levels. CHANGELOG_BEGIN - DAML Connect development is now conducted from the `main` branch, rather than the `master` one. If you had any dependency on the digital-asset/daml repository, you will need to update this parameter. CHANGELOG_END
2020-12-27 16:19:07 +03:00
- main
announce release rotation on Tuesday (#7151) It's been pointed out to me that some people actually plan their work, and for them, it would be useful to know at least a day in advance that they will be doing a release. This PR attempts to accommodate that. Note: this will run as a new, separate cron. I'll do the Azure setup after this gets approved. CHANGELOG_BEGIN CHANGELOG_END
2020-08-17 14:42:35 +03:00
always: true
jobs:
- job: announce_rotation
timeoutInMinutes: 60
pool:
Drop dependency on hosted nodes (#12901) This should hopefully get CI working again. There are two changes in here: 1. We can no longer change our patched Bazel. I didn’t switch away from the current patched version for now (we upload it to gcp bucket so it still works fine even if we cannot build it) but if we upgrade, we need to go to an unpatched version for now. 2. We need to get `az` from dev-env. I tested the self service compat job stuff and it works fine with this but there is a chance other parts don’t. changelog_begin changelog_end
2022-02-14 04:49:38 +03:00
name: 'ubuntu_20_04'
demands: assignment -equals default
announce release rotation on Tuesday (#7151) It's been pointed out to me that some people actually plan their work, and for them, it would be useful to know at least a day in advance that they will be doing a release. This PR attempts to accommodate that. Note: this will run as a new, separate cron. I'll do the Azure setup after this gets approved. CHANGELOG_BEGIN CHANGELOG_END
2020-08-17 14:42:35 +03:00
steps:
- checkout: self
persistCredentials: true
- template: ../bash-lib.yml
parameters:
var_name: bash_lib
- bash: |
set -euo pipefail
move to subdir 3.0 (#18520) * move most files * update CI configuration
2024-03-22 04:27:46 +03:00
cd sdk
Drop dependency on hosted nodes (#12901) This should hopefully get CI working again. There are two changes in here: 1. We can no longer change our patched Bazel. I didn’t switch away from the current patched version for now (we upload it to gcp bucket so it still works fine even if we cannot build it) but if we upgrade, we need to go to an unpatched version for now. 2. We need to get `az` from dev-env. I tested the self service compat job stuff and it works fine with this but there is a chance other parts don’t. changelog_begin changelog_end
2022-02-14 04:49:38 +03:00
eval "$(./dev-env/bin/dade-assist)"
announce release rotation on Tuesday (#7151) It's been pointed out to me that some people actually plan their work, and for them, it would be useful to know at least a day in advance that they will be doing a release. This PR attempts to accommodate that. Note: this will run as a new, separate cron. I'll do the Azure setup after this gets approved. CHANGELOG_BEGIN CHANGELOG_END
2020-08-17 14:42:35 +03:00
source "$(bash_lib)"
test release rotation: factor out selection (#11161) CHANGELOG_BEGIN CHANGELOG_END
2021-10-07 15:46:55 +03:00
RELEASE_MANAGER=$(next_in_rotation_slack)
announce release rotation on Tuesday (#7151) It's been pointed out to me that some people actually plan their work, and for them, it would be useful to know at least a day in advance that they will be doing a release. This PR attempts to accommodate that. Note: this will run as a new, separate cron. I'll do the Azure setup after this gets approved. CHANGELOG_BEGIN CHANGELOG_END
2020-08-17 14:42:35 +03:00
add release instructions to release notification (#13160) Because we can't expect people to magically know where to find them. CHANGELOG_BEGIN CHANGELOG_END
2022-03-04 14:33:15 +03:00
tell_slack "$(echo -e "Hi <@$RELEASE_MANAGER>! According to the <https://github.com/digital-asset/daml/blob/main/release/rotation|rotation>, you are in charge of the release tomorrow. Please make sure you plan accordingly, or find a replacement. See the <https://github.com/digital-asset/daml/blob/main/release/RELEASE.md|release instructions> for details.")"
Reference in New Issue Copy Permalink