robertnorthard/adop-pipeline-builder

ADOP Interactive Pipeline Builder

adop-pipeline-builder's Issues

Add run instructions to project readme

As a developer/user
I want to be able to run the application locally
So I can test it

Issues setting downstream

1. The cartridge collection loader expects it to be called downstream_folder. See:
   https://github.com/kramos/adop-platform-management/blob/master/projects/jobs/jobs.groovy#L342

2. (Minor) the downstream for production is being set to "Production_Pipeline", it should be unset
   https://gist.githubusercontent.com/anonymous/a05ca0e651052deb016823347d5b0498/raw

3. The downstream for an integration pipeline is not being set, it should be the downstream integration pipeline name or PROD
   https://gist.githubusercontent.com/anonymous/a05ca0e651052deb016823347d5b0498/raw

4. The "Production_Pipeline" is being called "PROD" whereas "Production_Pipeline" is a both better name and what CI pipelines off the Prod node are expecting (see ADOP_Flyway_Cartridge)
   https://gist.githubusercontent.com/anonymous/a05ca0e651052deb016823347d5b0498/raw

5. The downstream for CI pipelines off an integration pipeline is being set to "Application_Pipeline", it needs to be set to the name of the downstream Integration pipeline e.g. Integration1 in
   https://gist.githubusercontent.com/anonymous/a05ca0e651052deb016823347d5b0498/raw
   OR to "Production_Pipeline".

Happy to demo.

Support generating a jenkins pipeline file for integrated builds

Enhancement

It would be nice to be able to name Integration pipelines and Prod as well.

Remove node_modules and vendor directory

Remove noe_modules and vendor directory as they are generated by npm and bower respectively.

Use alpine base docker image

To reduce the application's footprint let's use the alpine docker base image.

Refactor hackathon code to promote OOP best practices

This was done during a hackathon and the code is rather hacky in place. It should be refactored to promote OOP best practices (low coupling, cohesive, law of demeter etc).

• Use bower for all dependencies, if they exist.

Depict CI and integrated build pipelines differently

To better distinguish between CI and integrated pipelines they should be depicted differently (e.g. this could be shape and colour).

Add ability to load tree from an existing cartridge collection JSON file

As a user
I want to be able to depict view the existing tree structure for an integration pipeline
So that I have an overview of my project.