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

fix: ansible playbook #134

Merged
jon_nfc merged 1 commits from fix-ansible-playbook into development 2024-06-30 17:42:51 +00:00
Conversation 14 Commits 1 Files Changed 1 +2 -2
jon_nfc commented 2024-06-30 16:28:36 +00:00 (Migrated from gitlab.com)
Copy Link

📚 Summary

get ansible playbooks running so that ansible ci tasks run. reason for failure was the update of the playbooks hosts key

🔗 Related Issue(s) 🔗 Related Merge Request(s)
nofusscomputing/projects/ansible/ansible_playbooks!104
nofusscomputing/projects/ansible/execution_environment!258

👷 Tasks

  • merging to correct branch?

  • issue linked to this MR?

  • related issues:

    • closed in a commit message

    • Manually closed

    • All related issues tasks complete?

## :books: Summary <!-- your summary here emojis ref: https://github.com/yodamad/gitlab-emoji--> get ansible playbooks running so that ansible ci tasks run. reason for failure was the update of the playbooks `hosts` key ----- | :link: **Related Issue(s)** | :link: **Related Merge Request(s)** | |:----:|:----:| | <!-- example #1 <br> #2 <br> #3 etc. if none enter *none* --> | nofusscomputing/projects/ansible/ansible_playbooks!104 <br> nofusscomputing/projects/ansible/execution_environment!258 | ### :construction_worker: Tasks <!-- dont remove tasks strike through including the checkbox by enclosing in double tidle '~~' --> - [ ] merging to correct branch? - [ ] issue linked to this MR? - related issues: - [ ] closed in a commit message - [ ] Manually closed - [ ] All related issues tasks complete? <!-- don't adjust the below slash commands -->
jon_nfc commented 2024-06-30 16:28:36 +00:00 (Migrated from gitlab.com)
Copy Link

added 10m of time spent

added 10m of time spent
jon_nfc commented 2024-06-30 16:28:36 +00:00 (Migrated from gitlab.com)
Copy Link

assigned to @jon_nfc

assigned to @jon_nfc
jon_nfc commented 2024-06-30 16:32:55 +00:00 (Migrated from gitlab.com)
Copy Link

mentioned in merge request nofusscomputing/projects/ansible/execution_environment!258

mentioned in merge request nofusscomputing/projects/ansible/execution_environment!258
jon_nfc commented 2024-06-30 16:35:13 +00:00 (Migrated from gitlab.com)
Copy Link

mentioned in merge request nofusscomputing/projects/ansible/ansible_playbooks!104

mentioned in merge request nofusscomputing/projects/ansible/ansible_playbooks!104
jon_nfc commented 2024-06-30 16:35:36 +00:00 (Migrated from gitlab.com)
Copy Link

mentioned in commit b9f65bf908

mentioned in commit b9f65bf908b6d5c5574e4522b3670780bcfb5bb8
jon_nfc commented 2024-06-30 16:35:37 +00:00 (Migrated from gitlab.com)
Copy Link

added 1 commit

  • b9f65bf9 - fix(ansible): add localhost to PB hosts var

Compare with previous version

added 1 commit <ul><li>b9f65bf9 - fix(ansible): add localhost to PB hosts var</li></ul> [Compare with previous version](/nofusscomputing/projects/gitlab-ci/-/merge_requests/84/diffs?diff_id=1051314415&start_sha=02422c55b8450d210b53e4cf3ebf0b1c30a4e981)
jon_nfc commented 2024-06-30 16:38:02 +00:00 (Migrated from gitlab.com)
Copy Link

mentioned in commit nofusscomputing/projects/ansible/ansible_playbooks@db9904c777001bc3cb458188822e43388eb98bcd

mentioned in commit nofusscomputing/projects/ansible/ansible_playbooks@db9904c777001bc3cb458188822e43388eb98bcd
jon_nfc commented 2024-06-30 16:39:25 +00:00 (Migrated from gitlab.com)
Copy Link

changed the description

changed the description
jon_nfc commented 2024-06-30 16:42:54 +00:00 (Migrated from gitlab.com)
Copy Link

mentioned in commit nofusscomputing/projects/ansible/execution_environment@6ba8f735367d1f550984b62be18352d130db1212

mentioned in commit nofusscomputing/projects/ansible/execution_environment@6ba8f735367d1f550984b62be18352d130db1212
jon_nfc commented 2024-06-30 16:47:51 +00:00 (Migrated from gitlab.com)
Copy Link

changed the description

changed the description
jon_nfc commented 2024-06-30 17:15:28 +00:00 (Migrated from gitlab.com)
Copy Link

mentioned in commit nofusscomputing/projects/ansible/ansible_playbooks@e66b2034a8d97ecfc8548c73b5603b064f3a426d

mentioned in commit nofusscomputing/projects/ansible/ansible_playbooks@e66b2034a8d97ecfc8548c73b5603b064f3a426d
jon_nfc commented 2024-06-30 17:16:04 +00:00 (Migrated from gitlab.com)
Copy Link

mentioned in merge request nofusscomputing/projects/ansible/ansible_playbooks!105

mentioned in merge request nofusscomputing/projects/ansible/ansible_playbooks!105
jon_nfc commented 2024-06-30 17:19:20 +00:00 (Migrated from gitlab.com)
Copy Link

mentioned in commit nofusscomputing/projects/ansible/execution_environment@645998ca891f688e06d0da47840caf2f534e67e4

mentioned in commit nofusscomputing/projects/ansible/execution_environment@645998ca891f688e06d0da47840caf2f534e67e4
jon_nfc commented 2024-06-30 17:42:51 +00:00 (Migrated from gitlab.com)
Copy Link

mentioned in commit 673441f83a

mentioned in commit 673441f83a7d943434252ee23899e3572cdfb141
jon_nfc (Migrated from gitlab.com) merged commit 673441f83a into development 2024-06-30 17:42:51 +00:00
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
type::bug
workflow::not started
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#134
No description provided.
Delete Branch "fix-ansible-playbook"

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?