[gnome-build-meta/alatiera/push-master: 4/14] CI: Push to the ostree repo only from the staging branch
- From: Jordan Petridis <jpetridis src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [gnome-build-meta/alatiera/push-master: 4/14] CI: Push to the ostree repo only from the staging branch
- Date: Thu, 20 Sep 2018 18:15:57 +0000 (UTC)
commit 901dc5f3e40f00ec49c853bd49ef8c9de6b86cb3
Author: Jordan Petridis <jpetridis gnome org>
Date: Mon Sep 10 21:12:46 2018 +0300
CI: Push to the ostree repo only from the staging branch
Quick workaround to allow us to move fast, and get the 3.30 release
out of the door. Ideally we would have a separate job that uses
protected branches and gitlabci `only:` conditionals
.gitlab-ci.yml | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
---
diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index be9f286..1d2d6a5 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -114,7 +114,10 @@ before_script:
# push the resulting runtimes to gbm.gnome.org
# FIXME: Only push from protected branches
- - ostree-releng-scripts/rsync-repos --src repo/ --dest gbm-builder.gnome.org:public_html/repo/
+ - |
+ if [[ ${CI_COMMIT_REF_NAME} == "staging-3-30" ]]; then
+ ostree-releng-scripts/rsync-repos --src repo/ --dest gbm-builder.gnome.org:public_html/repo/
+ fi
# Store all the downloaded git and ostree repos in the distributed cache.
# This saves us fetching them from the different repos and further afield
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]