New answers tagged continuous-deployment
1
Key issue with this approach is that applying commits selectively is extremely problematic. Basically, how do you know whether commits are dependent or independent?
As you correctly mentioned, this is one of the issues with Gitflow itself, so the solution is shifting methodologies. Preferred way today is Trunk-Based Development (TBD) - https://...
1
Yes, you can use the rules syntax. You can use this in combination with regex for commit message, ci_pipeline_source or any other available CI variables.
job1:
script:
- do something on schedule only
rules:
- if: '"$CI_PIPELINE_SOURCE" == "schedule"'
when: always
job2:
script:
- runs on Merge request pipeline
...
0
I guess you can do it via rules keyword. It has multiple condition with environment variables or branch name or schedules. If you add detail about you want to do, i try to
Gitlab CI Rules
2
I don't think you are missing any easy solutions because
the easy solutions probably rely on you having full access to the webserver -- which you don't have? The challenge is what is the best you can do given limited server access.
FTP does not have a reliable, built-in way to only upload changed files.
I think:
your only solution for problem 1 is to ...
Top 50 recent answers are included
Related Tags
continuous-deployment × 107continuous-integration × 48
deployment × 23
gitlab × 17
continuous-delivery × 16
jenkins × 14
git × 13
docker × 12
cicd × 11
gitlab-ci-runner × 8
kubernetes × 7
amazon-web-services × 7
azure-devops × 6
github × 6
yaml × 5
amazon-ec2 × 4
python × 4
build-pipeline × 4
release-management × 4
travis-ci × 4
jenkins-pipeline × 3
docker-compose × 3
azure × 3
terminology × 3
configuration-management × 3