b8199586b4
fix(commit_footer_refs): dont update git submodules
...
this ci job requires only the gitlab-ci submodule with other submodules being not applicable.
!71 fixes #42 nofusscomputing/infrastructure/configuration-management/project-production!2
2023-11-12 14:30:53 +09:30
837311c022
feat(release): annotate git tag with changelog
...
!68
2023-09-02 15:28:43 +09:30
f3256c5858
feat(commit_footer_refs): only run on changes
...
!50
2023-06-03 14:22:13 +09:30
6accd8633c
fix(commit_footer_check): run on non master/dev branches only
...
!42
2023-06-02 15:50:42 +09:30
04e7e928e0
feat(ci_rules): add exists and changes for rules
...
now defined jobs check for existance of file and for changes
to launch a job
!41 #32
2023-06-02 15:26:35 +09:30
a010f7bab1
fix(jobs): jobs that occur on push should also run on 'trigger'
...
!33 #26
2023-05-28 13:23:34 +09:30
bade89c533
fix(scheduled_pipelines): if scheduled pipeline only run schedualable jobs
...
!30 fixes #29
2023-05-28 10:31:26 +09:30
088c9fb04c
feat(conventional_commits): ensure .cz.yaml exists
...
if the cz.yaml config file does not exist, dont run commitizen jobs
!24
2023-05-21 01:48:53 +09:30
18a2808787
fix(gitlab_release): allow skip on dev branch
...
!17
2023-05-15 10:25:48 +09:30
d89941df05
feat(gitlab_release): dont automagic run on dev
...
see nofusscomputing/projects/ansible/git_configuration!4 and #21
!23 #21 nofusscomputing/projects/ansible/git_configuration!4
2023-05-15 10:19:49 +09:30
e06ffef66c
feat(gitlab_release): run on merge to development
...
the dev branch will create a RC tag to denote alpha release
!21
2023-05-14 11:46:28 +09:30
199ea1f23c
feat(gitlab_release): never run on merge or git tag
...
as this job creates a release and tag don't run on those pipelines
!21
2023-05-14 11:45:24 +09:30
a745ceac5e
fix(gitlab_release): fixed rule to match nfc_bot
...
this hould have been done as part of MR !20
!21 !20
2023-05-14 11:44:20 +09:30
1fa7fec38a
refactor(gitlab_release): show debug before command
...
!21
2023-05-14 11:41:47 +09:30
e76378dd06
fix(gitlab_release): only run on master on_success
...
!21 fixes #16
2023-05-14 11:39:53 +09:30
8d512a9a4b
feat(commit_footer_refs): ability to disable job with variable
...
!21
2023-05-13 11:49:52 +09:30
a37acbfc7d
feat(gitlab_release): ability to disable job with variable
...
!21
2023-05-13 11:48:47 +09:30
9a7ae7106e
refactor: set correct commit details for nfc_bot
...
Change made so that the commits from the
bot show up in it's profile
MR !20
2022-02-12 10:27:01 +00:00
82c6c9f5d5
feat(commit_footer_refs): never run on development or master.
...
this job checks for gitlab references in the commit footer. It
has been stopped from running on dev and master as checks are already
done on the developers branch that is being worked on prior to the
merging to dev or master branches.
MR !13
2022-01-16 09:02:44 +09:30
def31ef562
style(yaml_lint): fixed yaml lint errors
...
yaml lint was producing linting errors. Amended affected lines.
#1
2021-08-11 13:47:34 +09:30
eb0bf4c174
refactor(gitlab_release): file link to be in local repository for helping fix commit footer ref check failures
...
issue #4
2021-08-08 15:18:11 +09:30
756b9406dd
feat(gitlab_release): be able to toggle commit footer check job
...
if var CHANGELOG_FOOTER_REFERENCES=False, dont conduct validation job.
issue #4
2021-08-08 15:03:12 +09:30
7cb676eb98
ci(gitlab_release): Add a validation job to check if commit messages contain a gitlab reference in the footer
...
#4
2021-08-08 14:51:57 +09:30
f76cabeeb0
fix(gitlab_release): Adjust release workflow
...
Previous release workflow only allowed version increment of RC on development brnach.
adjust to the following workflow:
master branch: automatically increment the version
development branch: option to manually increment version (RC increment only)
!2
2021-08-07 14:31:19 +09:30
3e8c3ce7cd
feat(gitlab_release): On the development brnach, releases to be 'rc' to denote considered non-stable
...
#1
2021-08-04 12:39:01 +09:30
7a69685b53
refactor(gitlab_release): Dont conduct any release, git push or tag delete if the version was not bumped
...
Without this change the job would have failed due to no actual changes being made and the logic attemping to make the same existing changes.
2021-08-04 11:29:22 +09:30
2035ed27af
refactor(gitlab_release): use 'git log' to get current commit hash
...
issue #1
2021-08-04 10:44:57 +09:30
7706085b09
fix(gitlab_release): All tasks run as part of script including user custom script
...
Job would suceed if anything failed in after_script.
#1
2021-08-04 10:43:25 +09:30
1446c28ed2
fix(gitlab_release): Use a user token to access the git repo for pushing commits back
...
#1
2021-08-04 10:40:46 +09:30
6678a3dbab
feat(git_release): Migrated from ansible-roles
...
Mibrated from
commit: 295fe5b1db#1
2021-08-03 15:48:35 +09:30
