IntenseWebs/veilid
3
0
Fork 0
mirror of https://gitlab.com/veilid/veilid.git synced 2024-11-22 00:47:28 -06:00
Code Issues Packages Projects Releases Wiki Activity
b4e4299e7b
veilid/.gitlab-ci.yml

46 lines
1.1 KiB
YAML
Raw Normal View History

cleanup and stats accounting organization
2021-11-26 08:54:38 -06:00
variables:
use new runner
2022-11-22 16:16:53 -06:00
NO_DOCKER: 1
FORCE_COLOR: 1
EARTHLY_EXEC_CMD: "/bin/sh"
Add submodule strategyt to build
2022-11-26 23:18:08 -06:00
GIT_SUBMODULE_STRATEGY: normal
cleanup and stats accounting organization
2021-11-26 08:54:38 -06:00
Add merge_requests as build target, split into two architectures
2023-02-20 13:14:05 -06:00
stages:
temp change to complete stuck release [skip ci]
2024-08-02 10:02:10 -05:00
#- prepare
#- test
#- build_packages
Adding release stage triggered by existence of a tag that matches the v+semver format
2023-07-31 19:59:23 -05:00
- release
Update .gitlab-ci.yml file to the intermediary package distribution pipeline.
2023-06-20 21:46:05 -05:00
- distribute
initial CI attempt
2021-11-24 15:49:13 -06:00
Refactored Earthfile to improve caching Targets have been parallelized so that initial push of the container cache should build the whole build a little quicker, plus the container should now use the cache for more of the build and so speed up normal builds to just the compilation and test of the code that has changed The `build_cache` target now builds a `build-cache:latest` container that is stored in the GitLab project Container Registry, and then used (if it exists) by the `test_build` target. The `build_cache` task runs under 3 conditions, 1. the container does not exist, 2. if scheduled, 3. if run manually from the Pipelines page in the GitLab interface. It is recommended that the build is set up to run on a weekly schedule via the `Pipeline schedules` page in GitLab with the schedule of `0 2 * * 6`.
2023-10-31 06:17:13 -05:00
Update .gitlab-ci.yml file
2023-07-16 14:18:35 -05:00
Moved crate and python publishing to a dev machine. The orchestration machine doesn't have the resources for the cargo build steps.
2024-04-04 18:22:10 -05:00
build_repositories:
stage: distribute
Fixing order of jobs. `Needs` setting of build_repositories was causing stage leap frogging.
2024-08-01 21:58:24 -05:00
#needs:
# - publish_python
Moved crate and python publishing to a dev machine. The orchestration machine doesn't have the resources for the cargo build steps.
2024-04-04 18:22:10 -05:00
tags:
- build-orchestration
Migrating CICD scripts to Veilid repo Copied CICD scripts into the repository so that the community can make contributions to the build system. Wrote a brief description of the build and distribute process. Modified the CICD config to use the repo hosted scripts. [ci skip]
2024-04-21 13:37:45 -05:00
variables:
Another tweak to GitLab secure storage
2024-07-19 15:49:29 -05:00
SECURE_FILES_DOWNLOAD_PATH: './'
Moved crate and python publishing to a dev machine. The orchestration machine doesn't have the resources for the cargo build steps.
2024-04-04 18:22:10 -05:00
script:
Further adventures in nightly release automation Pushing this up in order to end-to-end test automated nightly releases. Please enter the commit message for your changes. Lines starting
2024-07-19 14:08:25 -05:00
- curl --silent "https://gitlab.com/gitlab-org/incubation-engineering/mobile-devops/download-secure-files/-/raw/main/installer" | bash
- cp scripts/cicd/build-orchestration/rpm-repo-building/Dockerfile ~/rpm-build-container
- cp scripts/cicd/build-orchestration/rpm-repo-building/repobuild.sh ~/rpm-build-container
Adding automatic nightly release builds - Restructured linux repo directory structure to include Stable and Nightly releases - Reworked Earthfile to pass IS_NIGHTLY boolean to package build scripts for use in file names - Added nightly pipeline to CICD config yaml. Pipeline is triggered by IS_NIGHTLY variable - Two distribution scripts now exist, one for Stable and one for Nightly - Reworked RPM build spec files to create appropriate file names - Reworked debian release generation scripts - RPM repo directory structure is prepped for arm64 builds - Switched from scp to rsync for moving the completed repo from ochestration to repo server - Created schedule in Gitlab UI to trigger nightly release at 2300 Central Time
2024-07-14 17:22:50 -05:00
- cp scripts/cicd/build-orchestration/generate-stable-release.sh ~
Fixed CICD missing params
2024-07-14 22:58:26 -05:00
- bash scripts/cicd/build-orchestration/distribute-stable-packages.sh
Moved crate and python publishing to a dev machine. The orchestration machine doesn't have the resources for the cargo build steps.
2024-04-04 18:22:10 -05:00
rules:
- if: '$CI_COMMIT_TAG =~ /v\d.+/'
Update .gitlab-ci.yml file
2023-07-16 14:18:35 -05:00
deploy_repos:
stage: distribute
needs:
- build_repositories
tags:
- repo-server
script:
Calling bash explicitly The paths work now, but the scripts are not set with execute permission. I don't know if that permission will survive the transfer from my machine across the git and runner stuff so I added an explicit call for bash instead.
2024-04-28 20:39:18 -05:00
- bash scripts/cicd/repo-server/deploy-repo.sh
Update .gitlab-ci.yml file
2023-08-02 09:14:18 -05:00
rules:
- if: '$CI_COMMIT_TAG =~ /v\d.+/'
Added CICD dry run This is the first attempt at setting up a dry run pipeline to test changes to the CICD config without actually publishing the compiled binaries and packages built by the process. The dry run should be triggered by any changes to .gitlab-ci.yml or changes to any of the scripts under scripts/cicd/.
2024-04-29 14:40:07 -05:00
Reference in New Issue Copy Permalink