Setup repo ready for use #1
Closed
opened 2021-08-02 08:01:47 +00:00 by jon_nfc
·
82 comments
No Branch/Tag Specified
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.
Projects
Clear projects
No project
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: infrastructure/gitlab-ci#1
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
No description provided.
Delete Branch "%!s()"
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?
Migrate CI folder contents to this repo.
The intent of this repo is that it will be all of the CI jobs for projects.
Folder structure
All a CI Job per sub folder from the root of the repo.
workflow / CI usage
git clone {this repo} .
from the CI folder. Can be a clone or sub module..gitlab-ci.yaml
include this repos job.gitlab-ci.yml
Changelog per folder
Command to output all commits on a path is
git log --follow -- CI
and can be formated as follows:git log --pretty="format:%H - %s " --follow -- CI
outputs{commit_hash} - {commit subject}
links
using git sub-modules with CI contradiction in sub- module path
git log format cheatsheet
Tasks
set-up this repo open-source and sync with github project
NoFussComputing/gitlab-ci
create a template job folder or document how to setup a job.
if child-repo setup CI as git-submodule can there be fail-over if host fails? If so document.
Feature To Do
ensure linting is done on the yaml files
linting Python files
do shell files need linting?
changelog per ci job folder commits per path could be used to format log, with dates and save as changelog.
merge request template
issue template
assigned to @jon_nfc
changed the description
changed the description
changed the description
changed the description
changed the description
added 20m of time spent
changed the description
added 30m of time spent
changed the description
changed the description
added 2h of time spent
changed the description
added 2h 30m of time spent
changed the description
changed the description
add sub-module
mentioned in commit
bd08adf93f
mentioned in commit 45bfc4a5d7c133108bd2e609891be31699852ab8
mentioned in commit 018017666a6a6ed9c0f2be855e1d66682b3a7d07
mentioned in commit c8b43f43639360ada24cd96eb9e1b23befe3690b
mentioned in commit d93919642979467ba9130ba930debc6ae6ed5582
mentioned in commit 4baf619abedac2b9a3ec8c7a9c5f74a3a608a7ab
mentioned in commit cbaaa3270e545b665441f727c005bdaaea58ca61
mentioned in commit c3d26fe71cf65f2c2e3ddd0c07440defbf0f718a
mentioned in commit 27e0deada409cd8007c28ab4ac5323677523f0fe
mentioned in commit
392a200fd4
mentioned in commit 82b794bae269f74a226d78d20e94ddaa1b46ca8b
mentioned in commit
a2174104d1
mentioned in commit
b593505698
mentioned in commit
9b28ae5952
mentioned in commit
7ffb20418c
mentioned in commit d4605358c2d89297a6b67945aca41e9831d0fa9f
mentioned in commit
247264e36b
mentioned in commit
2413daefb1
mentioned in commit
2a3266fb53
mentioned in commit
1ecd857c0b
mentioned in commit
6678a3dbab
mentioned in commit
72fabea68f
mentioned in commit 5d5c382f90775d7d83cb432cf099961e0a8b3803
mentioned in commit 7c0f51b25edcf185296dea3ea352d2da204b8670
mentioned in commit ca2a208cd473d816515b8858234b7f63d05e95dc
added 7h of time spent
added 30m of time spent
added 1h 53m of time spent
added 1h 54m of time spent
subtracted 1h 54m of time spent
mentioned in commit
1446c28ed2
mentioned in commit
ed5be7fd3c
mentioned in commit
2035ed27af
mentioned in commit
7706085b09
mentioned in commit c40f7209d20f936c8553cc420c2ce3686a8ddde5
mentioned in commit 691d7821d247bf184509de8a212ffb4c420813cb
mentioned in commit
80ca3618ee
mentioned in commit
72e8b6c84d
mentioned in commit 41c6f573eef634e6950d80aa690f956b1736f154
mentioned in commit
eebe8e30dc
mentioned in commit
287b4c954d
mentioned in commit 86846a25bba6574e680ad6f01b44e5501205a8c2
mentioned in commit
cc3fabdaa2
mentioned in commit
3e8c3ce7cd
mentioned in commit
cb78ab8218
marked the checklist item changelog per ci job folder commits per path could be used to format log, with dates and save as changelog. as completed
mentioned in merge request !2
changed the description
marked the checklist item set-up this repo open-source and sync with github project
NoFussComputing/gitlab-ci
as completedmentioned in merge request !3
mentioned in merge request !5
marked the checklist item create a template job folder or document how to setup a job. as completed
marked the checklist item merge request template as completed
marked the checklist item issue template as completed
marked the checklist item is there a gitlab-ci linter? as completed
marked the checklist item linting Python files as completed
marked the checklist item ensure linting is done on the yaml files as completed
added 6h of time spent
mentioned in merge request !7
mentioned in commit
9f7a24c1eb
mentioned in commit
63af1efb4f
mentioned in commit
da8eb5c338
mentioned in commit
ace7a03456
added 15m of time spent
marked this issue as related to #6