rndsolutions / hawkcd Goto Github PK

• Implement StageService
• Cover with Unit tests

Steps to reproduce:

Run a simple task w/ one job and one task and try to execute a simple command

Expected Result

A folder with the pipeline name should be created inside the Pipelines folder on the agent

Actual Result

Folder with pipeline name is not created

• Implement MaterialTracker worker
• Implement MaterialTrackerService
• Implement MaterialPreparer worker
• Implement MaterialTrackerService
• Implement MaterialUpdater
• Implement MaterialUpdaterFactory
• Cover with Unit tests

• Portal main page design, it needs to communicate the software value to potential users

• General information architecture (portal structure)
  • Get Started
    • Installation
      • Windows
      • Linux
    • Requirements
    • Concepts
  • Contribute
    • Contribution Agreement
    • Technical Documentation
      • SRS
      • SDD
      • Hawk API
    • Development Process
      • Labels
      • Request Feature
      • Issues
        • Report Bug
        • Create Issue
    • Discussion
      • Forum
      • Chat
  • User Guide
    • Walkthrough
  • Roadmap
  • About Us
  • Download

• User docs, concepts - identify topics
• Developer docs
  • Development process, bug fixing, pull requests, releases. lables explained
  • Debugging the application Nix/Win

• Licensing

• The Hawk Agent should call an endpoint on the Server updating itself in the database.
• The Hawk Agent should call an endpoint on the Server updating the Job it is currently running in the database.

A user should be able to configure:

• Server settings

Port
Host

• Database settings

Current database
Should use embedded database
Redis
MongoDb

• Provider settings
  Github
• Folder settings

Materials
Artifacts

• Worker settings

Pipeline Scheduler
Material Tracker

Steps to reproduce:

Create a pipeline

Go to edit mode and enter a command different than the default
Start the pipeline

Expected Result

The task should reflect the changes entered in the edit screen

Result:

The Job fails with default task values

• Implement NuGetMaterialUpdater
• Cover with Unit tests

• Implement IMaterialDefinitionService
• Implement MaterialDefinitionService
• Implement IMaterialService
• Implement MaterialService
• Cover with Unit tests

Steps to reproduce:

Add two Tasks to a Job
Rearrange them with drag and drop
Refresh the page

Expected Result

The Tasks should be in the new order

Actual Result

The Tasks are still in the initial order

• Implement JobService
• Cover with Unit tests

We need to define what are going to be the notification messages to be shown to the user upon different UI interactions.

• Pipelines
• Stages
• Jobs
• Pipeline Groups
• Pipeline-definitions
• Stage-definitions
• Job-definitions
• Task-definitions
• Materials
• Artifacts
• Agents
• Unit Tests

• Refactor ExecExecutor
• Cover with Unit Tests

1. Implement logic that updates the global ViewModel
   • Implement updating of PipelineGroups
   • Implement updating of Pipelines
   • Implement updating of PipelineDefinitions
   • Implement updating of Agents

Implement a page on the portal site to list all daily builds and scheduled releases so that users can have access to the latest & stable bits of the software.

1. Implement CRUD operations
   • get all
   • get by id
   • add
   • update
   • delete
2. 2. Cover all classes with unit tests

Steps to reproduce:

Create an ExecTask
Command: /bin/bash
Arguments: -c mkdir directoryName

Expected Result

The Task should be executed successfully

Actual Result

/bin/bash: - : invalid option

Abide by team conventions

• 1. Implement logic that searches for Pipelines with updated Materials.
• 2. Implement logic that prepares the found Pipelines for assignment.
• 3. Cover with unit tests.

Should have one method with an overload for each object type.

• 1. Implement validation for Object
• 2. Implement validation for PipelineGroup
• 3. Implement validation for PipelineDefinition
• 4. Implement validation for StageDefinition
• 5. Implement validation for JobDefinition
• 6. Implement validation for TaskDefinition
• 7. Implement validation for MaterialDefinition
• 8. Implement validation for Agent
• 9. Implement validation for ExecTask
• 10. Implement validation for FetchArtifactTask
• 11. Implement validation for FetchMaterialTask
• 12. Implement validation for UploadArtifactTask
• 13. Cover with unit tests

• 1. Implement Core Services
  • Implement PipelineGroupService
  • Implement PipelineDefinitionService
  • Implement PipelineService
  • Implement AgentService
  • Implement EnvironmentService
• 2. Cover all classes with unit tests

• 1. Implement logic that searches for Pipelines to be updated.
• 2. Implement logic that updates the statuses of the found Pipelines and their Stages and Jobs.
• 3. Cover with unit tests.

• Implement Resource Handler
• Add ability to create standalone .jar file
• Automate dist folder placement

Steps to reproduce:

Create a pipeline

Go to edit mode and enter a command different than the default
Start the pipeline
Expected Result

The task should either pass or fail
Result:

The Executor hangs and pipeline is always in status RUNNING.

• Display Stage Runs in Stage Definitions correctly
• Arrange Job Runs correctly
• Display Stage statuses correctly
• Display Job statuses correctly
• Restyle Agents view
• Display Job results correctly
• Seperate History and Current run screens
• Restyle History screen
• Create Current run screen
• Create all Materials in Admin screen
• Implement displaying of last Stage run in Pipelines screen, with statuses

• Refactor FetchMaterialExecutor
• Cover with Unit tests

1. Implement CRUD operations
   • get all
   • get by id
   • add
   • update
   • delete
2. 2. Cover all classes with unit tests

• 1. Create necessary models
• 2. Remove unused properties of created ones
• 3. Abide by conventions
• 4. Encapsulate logic

Steps to reproduce:

Start server & agent
Delete the agent
Wait couple of seconds

Expected Result

The agent should auto-register and be in disabled state

Actual Result

Even the agent is working it's doesn't show on the page.

• Implement IGitService
• Implement GitService
• Implement GitMaterialUpdater
• Cover with Unit tests

• Implement MaterialDefinition Service

• 1. Implement CRUD operations
  • get all
  • get by id
  • add
  • update
  • delete
• 2. Cover all methods with unit tests

• MaterialDefinition
• Material
• GitMaterial
• NuGetMaterial

• Hashing the password

We need to make more intuitive and user friendly the run management screen. Ideally concentrating on the data visualization aspect the workflow. Using some sort of chart to depict the pipeline process will be necessary

Steps to reproduce:

Add a new task of type fetch artifacts
Refer to the Actual result

Expected Result
The task command should be shown in the "command" column

Actual Result

1. Implement CRUD operations for Services
   • PipelineGroup Service
   • PipelineDefinition Service
   • Pipeline Service
   • Agent Service
2. Implement handling of Server response for Services
   • PipelineGroup Service
   • PipelineDefinition Service
   • Pipeline Service
   • Agent Service

• 1. Implement logic that searches for eligible Agents.
• 2. Implement logic that assigns Jobs to the eligible Agents.
• 3. Cover with unit tests.

• Refactor UploadArtifactExecutor
• Cover with Unit tests

• 1. Implement logic to deserialize TaskDefinition class to concrete class type
• 2. Cover with Unit tests

1. Implement CRUD operations
   • get all jobs in pipeline
   • get all jobs in stage
   • get by id
   • add
   • update
   • delete
2. 2. Cover all classes with unit tests

• Implement ability to send information to all connected Sessions through WebSocket

• Integrate the embedded Redis database store to be used as a default database engine

Implement an Agent Controller according to the Hawkengine API documentation:
https://hawkcd.api-docs.io/v1

Overview

For the first beta release we'll need to consider two main "getting started" workflows. The purpose is to provide easy "getting started" experience.

We have 2 main cases that new users will end up with:

When a user sign-in for the first time with the system he should see the /pipelines screen and a big button that invites him to get started setting up his software delivery workflow. If the user came through the Sign-up w/ GitHub scenario he should be offered first to sync his account w/ github-> this will initiate the repos sync and creation of server "materials", once this is done the user should be offered to continue setting up his pipeline.

Sign-up w/ GitHub

For this scenario a user chooses to sign-up w/ GitHub account and agrees to share his source code repos w/ hawkcd.io, The server will automatically import them as materials from type git and make them available for the "Pipeline creation workflow". There should be a way the user to see all git repos and manipulate them sync/delete/add new ones. All the repos that are automatically imported from GH as materials should be labeled w/ github label.

Sign-up w/ email/password

After the sign in the user will be navigated to the pipelines screen, where he can continue with the regular pipeline creation process. Once the pipeline is created a default pipeline group called "default" should be created for the current pipeline.

• Refactor FetchArtifactExecutor
• Cover with Unit Tests

• 1. Implement add method to PipelineService class
• 2. Implement add method to PipelineDefinitionService class
• 3. Cover with unit tests