infrastructure/gitlab-ci
2
0
Fork 0
Code Issues 17 Pull Requests 1 Actions Projects Releases 21 Wiki Activity

feat(automation): job to run ansible playbooks #79

Merged
jon_nfc merged 6 commits from restructure into development 2023-05-27 05:57:14 +00:00
Conversation 20 Commits 6 Files Changed 4 +103 -1
jon_nfc commented 2023-05-26 07:00:38 +00:00 (Migrated from gitlab.com)
Copy Link

nofusscomputing/projects/ansible/execution_environment!8 nofusscomputing/projects/ansible-roles!25 nofusscomputing/projects/ansible/git_configuration#5

related to nofusscomputing/projects/ansible/execution_environment#7

nofusscomputing/projects/ansible/execution_environment!8 nofusscomputing/projects/ansible-roles!25 nofusscomputing/projects/ansible/git_configuration#5 related to nofusscomputing/projects/ansible/execution_environment#7
jon_nfc commented 2023-05-26 07:00:55 +00:00 (Migrated from gitlab.com)
Copy Link

assigned to @jon_nfc

assigned to @jon_nfc
jon_nfc commented 2023-05-27 02:16:07 +00:00 (Migrated from gitlab.com)
Copy Link

changed the description

changed the description
jon_nfc commented 2023-05-27 04:12:19 +00:00 (Migrated from gitlab.com)
Copy Link

mentioned in commit nofusscomputing/projects/ansible/git_configuration@54a9d588c2250076de053d4ba1d8e8e655e5811e

mentioned in commit nofusscomputing/projects/ansible/git_configuration@54a9d588c2250076de053d4ba1d8e8e655e5811e
jon_nfc commented 2023-05-27 04:12:54 +00:00 (Migrated from gitlab.com)
Copy Link

mentioned in merge request nofusscomputing/projects/ansible/git_configuration!14

mentioned in merge request nofusscomputing/projects/ansible/git_configuration!14
jon_nfc commented 2023-05-27 04:34:29 +00:00 (Migrated from gitlab.com)
Copy Link

mentioned in commit 1f6ee9ea27

mentioned in commit 1f6ee9ea27824df1c82bf85e1e239f57f2145bdf
jon_nfc commented 2023-05-27 04:34:30 +00:00 (Migrated from gitlab.com)
Copy Link

added 1 commit

  • 1f6ee9ea - refactor(automation): final logic changes

Compare with previous version

added 1 commit <ul><li>1f6ee9ea - refactor(automation): final logic changes</li></ul> [Compare with previous version](/nofusscomputing/projects/gitlab-ci/-/merge_requests/29/diffs?diff_id=692654593&start_sha=0d3eaa6ac2dc448505b18c6aecd4a72e28ffde83)
jon_nfc commented 2023-05-27 04:57:07 +00:00 (Migrated from gitlab.com)
Copy Link

added 23m of time spent

added 23m of time spent
jon_nfc commented 2023-05-27 05:38:03 +00:00 (Migrated from gitlab.com)
Copy Link

mentioned in merge request nofusscomputing/ops!14

mentioned in merge request nofusscomputing/ops!14
jon_nfc commented 2023-05-27 05:51:49 +00:00 (Migrated from gitlab.com)
Copy Link

mentioned in commit f9af921e6b

mentioned in commit f9af921e6b6ec10f9f77ec6a016c6cbb9559d1bf
jon_nfc commented 2023-05-27 05:51:49 +00:00 (Migrated from gitlab.com)
Copy Link

mentioned in commit c5d27e832e

mentioned in commit c5d27e832e100156cb99c5ca580fd5a8eb600e0f
jon_nfc commented 2023-05-27 05:51:49 +00:00 (Migrated from gitlab.com)
Copy Link

mentioned in commit 158cc94d1a

mentioned in commit 158cc94d1a817f89b6603e9bac7678196b21d1d5
jon_nfc commented 2023-05-27 05:51:50 +00:00 (Migrated from gitlab.com)
Copy Link

added 3 commits

  • 158cc94d - feat(variables): added pipeline trigger and schedule
  • f9af921e - refactor(ansible_playbook): final logic adjustment for job
  • c5d27e83 - feat(auto_jobs): created initial template to auto-create jobs

Compare with previous version

added 3 commits <ul><li>158cc94d - feat(variables): added pipeline trigger and schedule</li><li>f9af921e - refactor(ansible_playbook): final logic adjustment for job</li><li>c5d27e83 - feat(auto_jobs): created initial template to auto-create jobs</li></ul> [Compare with previous version](/nofusscomputing/projects/gitlab-ci/-/merge_requests/29/diffs?diff_id=692662033&start_sha=1f6ee9ea27824df1c82bf85e1e239f57f2145bdf)
jon_nfc commented 2023-05-27 05:54:36 +00:00 (Migrated from gitlab.com)
Copy Link

mentioned in commit 19dde28526

mentioned in commit 19dde28526d5e3f7694da3246505537aa2e19c10
jon_nfc commented 2023-05-27 05:54:37 +00:00 (Migrated from gitlab.com)
Copy Link

added 1 commit

Compare with previous version

added 1 commit <ul><li>19dde285 - chore: fix linting error</li></ul> [Compare with previous version](/nofusscomputing/projects/gitlab-ci/-/merge_requests/29/diffs?diff_id=692662271&start_sha=c5d27e832e100156cb99c5ca580fd5a8eb600e0f)
jon_nfc commented 2023-05-27 05:57:13 +00:00 (Migrated from gitlab.com)
Copy Link

merging so it can be tested.

merging so it can be tested.
jon_nfc commented 2023-05-27 05:57:13 +00:00 (Migrated from gitlab.com)
Copy Link

added 10m of time spent

added 10m of time spent
jon_nfc commented 2023-05-27 05:57:14 +00:00 (Migrated from gitlab.com)
Copy Link

mentioned in commit 573f47ba7c

mentioned in commit 573f47ba7c3104f32d3fca18ffbf60ea72cef23a
jon_nfc (Migrated from gitlab.com) merged commit 573f47ba7c into development 2023-05-27 05:57:15 +00:00
jon_nfc commented 2023-05-27 06:05:08 +00:00 (Migrated from gitlab.com)
Copy Link

mentioned in commit nofusscomputing/ops@7a04bea65a

mentioned in commit nofusscomputing/ops@7a04bea65a01dee356318959b0697f36755e5c3b
jon_nfc commented 2023-05-27 06:25:31 +00:00 (Migrated from gitlab.com)
Copy Link

mentioned in issue nofusscomputing/projects/ansible/ansible_playbooks#1

mentioned in issue nofusscomputing/projects/ansible/ansible_playbooks#1
jon_nfc commented 2023-05-28 03:58:22 +00:00 (Migrated from gitlab.com)
Copy Link

mentioned in issue #27

mentioned in issue #27
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
Bug
Used in discussion about a bug in comments or commits
CVE-2023-5764
Denotes items related to the CVE
CodeReview
Used in comments (issues/MR/commits) to denote code review related items
Documentation
Documentation items
Feature
Used in discussion about a Feature in comments or commits
Lint
Used in comments (issues/MR/commits) to denote lint tasks todo, done, fixed
Privacy
Used in comments (issues/MR/commits) to denote privacy related items
Security
Used in comments (issues/MR/commits) to denote Security related items
breaking-change
label used to denote that the issue/Merge Request does/will introduce a breaking change
bug::reproducable
Given to an issue when the bug has been confirmed as re-producable. Can also be used in comments and commits.
bug::unable to reproduce
Given to an issue when the bug that is not able to be reproduced. Can also be used in comments and commits.
code review::complete
code review::not started
code review::rejected
code review::underway
difficulty::Full Development
Level 3. Difficulty representing that the task to complete must be planned and created.
difficulty::Good First Issue
Level 1. Difficulty representing that the task is very simple and with limited knowledge can be completed.
difficulty::Prior Knowledge
Level 2. Difficulty representing that the task requires some prior knowledge of either the technology or the project for task completion.
documentation::complete
Issues, Merge Requests
documentation::no change required
Issues, Merge Requests and used to denote no documentation changes required
documentation::not started
Issues, Merge Requests
documentation::stalled
Issues, Merge Requests
documentation::underway
Issues, Merge Requests
impact::0
impact::1
impact::2
impact::3
impact::4
impact::5
ops::ansible-roles
OPS project tag
ops::automation
ops::gitlab-ci
OPS project tag
ops::marcas
OPS project tag
ops::python-gitlab-management
OPS project tag
ops::website
priority::0
priority::1
priority::2
priority::3
priority::4
priority::5
stage::Ready for Development
stage::develop
Stage for use in Issues and Merge Requests. Can also be used in discussion in comments and commits
stage::feedback required
stage::planning
Stage for use in Issues and Merge Requests. Can also be used in discussion in comments and commits
stage::test
Stage for use in Issues and Merge Requests. Can also be used in discussion in comments and commits
stale
Label given to issues/merge requests that are considered stale due to no collaboration and is a mark for closure.
triage
Tag given to issues/merge requests requiring triaging by the team.
triage::not_confidential
This tag is given by the triage bot so that URLs can be added to an issue/comment. A triage policy for NFC wide should remove this label.
type::CI / CD
type::automation
This type is used to denote an automation job
type::bug
Type for Issues and Merge Requests. Can also be used in discussion in comments and commits
type::compliance
type::discussion
Type for Issues. Can also be used in discussion in comments.
type::documentation
Type for Issues and Merge Requests. Can also be used in discussion in comments and commits
type::feature
type for Issues and Merge Requests. Can also be used in discussion in comments and commits
type::invalid
label given to tickets that require no action or are deem as invalid.
type::quality assurance
Type for Issues and Merge Requests. Can also be used in discussion in comments and commits
type::question
Type for Issues. Can also be used in discussion in comments.
type::security
Type for Issues and Merge Requests.
type::specification
Design specification
workflow::complete
Issues, Merge Requests
workflow::not ready
workflow::not ready::blocked
workflow::not started
Issues, Merge Requests
workflow::ready to commence
Issues, Merge Requests
workflow::stalled
Label given to issues/merge requests where no work has occured in x days iaw triage policy.
workflow::underway
Issues, Merge Requests
workflow::underway::develop
Area/CI-CD
Documentation changes
Area/Documentation
Documentation changes
Area/Security
This is security issue
Area/Testing
Issue or pull request related to testing
Bug
Failure to Confirm
Bug exists due to not confirming/testing code
Bug
Regression
THe bug is a regression of a feature
Bug
To be Confirmed
This bug is not confirmed
Bug
Unable to Reproduce
A developer can not re-create/re-produce the bug
Compat/Breaking
Breaking change that won't be backward compatible
Impact
Critical
1
The impact is critical in that it is blocking or prevents usage.
Impact
High
2
The impact requires that changes be made for continuted usage.
Impact
Low
4
The impact requires the user approach from a different angle for continued usage.
Impact
Medium
3
The impact requires a workaround for continued usage.
Impact
Very Low
5
The impact has a slight effect on usage.
Priority
High
2
The priority is high
Priority
Low
4
The priority is low
Priority
Medium
3
The priority is medium
Priority
Very High
1
The priority is critical
Priority
Very Low
5
The priority is very low
Reviewed
Confirmed
1
Issue has been confirmed
Reviewed
Duplicate
2
This issue or pull request already exists
Reviewed
Invalid
3
Invalid issue
Reviewed
Won't Fix
3
This issue won't be fixed
Status
Abandoned
3
Somebody has started to work on this but abandoned work
Status
Blocked
1
Something is blocking this issue or pull request
Status
Need More Info
2
Feedback is required to reproduce issue or to continue work
Type
Bug
Something is not working
Type
Epic
Epic User Story
Type
Feature
Feature / Module
Type
Incident
Something occured related to a service
Type
RFE
Request for Enhancement
Type
Task
A work item that must be done
Urgency
Low
4
Prioritize this amoungst your list of things to do.
Urgency
Major
1
Urgency is so high it should have been dealt with last week.
Urgency
Medium
3
Start as soon as possible.
Urgency
Very High
2
Urgency is high enough to warrant near immediate commencement.
Urgency
Very Low
5
Add this to your list of things to do.
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
jason jon
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: infrastructure/gitlab-ci#79
No description provided.
Delete Branch "restructure"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?