# Tekton Braindump of Build-server requirements

Support the language build tools (e.g. Maven, Gradle, npm, make)
- [ ] Pipeline for each language build tool
- [ ] Tasks distinguishing build tool (when conditions)
- [ ] Template with env=BuildTool with corresponding pipeline

Developers can Independently of other teams apply modifications to build input parameters for language specific build tools
1. Can be supported in tekton by parameterized pipelines
- [ ] Modify pipeline environment variables, possible in qui; inpact all pipeline user
- [ ] Provide custom PipelineRun resource with this input parameters; don't impact pipeline for others; Gui/CLI
3. The developer can “overwrite” the docker build-image used without changing the tekton pipeline
- [ ] Possible to change base docker image with --from argument passed to the buildah step to overwrite image. Parameter appliayed in pipeline step, impacting other user or creating pipeline run with custom variable to overwrite base image, not impacting others

Aggregating build-logs and making these available from a single source is essential for developer feedback
- [ ] ? Caro logic
- [ ] What provide tekton dashboard https://tekton.dev/docs/dashboard/install/
- [ ] fluentd (https://github.com/tektoncd/pipeline/issues/1155)
- [ ] flux cd v2
- [ ] elastic Stack https://github.com/mgreau/tekton-pipelines-elastic-o11y (2 years solution)
- [ ] cloud storage e.g. gcs task https://hub.tekton.dev/tekton/task/gcs-upload
- [ ] tkn, kubectl

Pipeline status is easily available to quickly identify the step which failed
- [ ] Graphical information provided in PipelineRun Details; Available from Admin and Developer panel
![Uploading file..._m45xu6tk7]()
![Uploading file..._g9qrwf9a9]()

is it enough?

Build pipelines be able to update Merge-request / Pull-request checks in situations like
1. Build of merge/feature branch fails
- [ ] Tekton have a few git tasks. What update Merge-request mean?
- [ ] Tekton provide possibility to add github comment, label, open pull request, create new release
2. Vulnerability scan fails (for failed quality gates in BlackDuck)
- [ ] No BlackDuck task in TektonHub;
- [ ] Create task that recognize the status of BlackDuck scan and update Merge-request
3. Static code check fails (for failed quality gates in SonarQube)
- [ ] Create task that recognize the status of SonarQube scan and update Merge-request

Successful or failed deployments through ArgoCD should be visible from the build tool or possibly git repo management tool.
- [ ] Probably possible

Developers must be able to apply build pipeline specific credentials or other secret information independently
- [ ] Pain in the ...
- [ ] Secrets, pvc, configmaps can be provided only in PipelineRun
- [ ] Limit to pass only one resource from Secrets, pvc, configmaps to one workspace
- [ ] Require some work from developer to add secret, pvc, cfg to pipeline

The build pipelines must obfuscate secret information from log files
- [ ] Not fully understand

Pipelines for automatic integration testing will almost always require customization of the standard pipelines.
- [ ] Not fully understand

Support for building merge or feature branches in isolation and provide developer with isolated feedback
- [ ] Feature Branch by providing custom PipelineRun which will be deployed to dedicated feature branch environment, cluster?
- [ ] Not deploying option for feature branch