Skip to content

Commit 2ab472e

Browse files
committed
Problem: manual release OBS trigger is flaky
Solution: use workflow instead
1 parent e9e01fa commit 2ab472e

File tree

2 files changed

+10
-8
lines changed

2 files changed

+10
-8
lines changed

.obs/workflows.yml

+10
Original file line numberDiff line numberDiff line change
@@ -4,3 +4,13 @@ workflow:
44
source_project: network:messaging:zeromq:git-draft
55
source_package: libzmq
66
target_project: network:messaging:zeromq:ci
7+
release:
8+
steps:
9+
- trigger_services:
10+
project: network:messaging:zeromq:release-stable
11+
package: libzmq
12+
- trigger_services:
13+
project: network:messaging:zeromq:release-draft
14+
package: libzmq
15+
filters:
16+
event: tag_push

ci_deploy.sh

-8
Original file line numberDiff line numberDiff line change
@@ -15,14 +15,6 @@ if [[ $BUILD_TYPE == "default" && $CURVE == "libsodium" && -z $DRAFT ]]; then
1515
md5sum *.zip *.tar.gz > MD5SUMS
1616
sha1sum *.zip *.tar.gz > SHA1SUMS
1717
cd -
18-
19-
# Trigger source run on new tag on OBS. The latest tag will be fetched.
20-
if [ -n "${OBS_STABLE_TOKEN}" ]; then
21-
curl -H "Authorization: Token ${OBS_STABLE_TOKEN}" -X POST https://api.opensuse.org/trigger/runservice
22-
fi
23-
if [ -n "${OBS_DRAFT_TOKEN}" ]; then
24-
curl -H "Authorization: Token ${OBS_DRAFT_TOKEN}" -X POST https://api.opensuse.org/trigger/runservice
25-
fi
2618
else
2719
export LIBZMQ_DEPLOYMENT=""
2820
fi

0 commit comments

Comments
 (0)