Add new command: hal build

[cmoulliard]

New feature

I'm thinking that we need a command hal new-build able to start/trigger a new taskrun build.

hal new-build -c fruit-client-sb

The easiest approach is to delete the taskrun resource which has been created by the operator for the specified component and then a new one will be re-created automatically.
Of course, this approach means that we will not use any update of the buildConfig and that we will deploy a new Task/TaskRun

oc get taskruns
NAME               SUCCEEDED   REASON      STARTTIME   COMPLETIONTIME
fruit-backend-sb   True        Succeeded   31m         28m
fruit-client-sb    True        Succeeded   31m         28m

oc delete taskruns/fruit-backend-sb
taskrun.tekton.dev "fruit-backend-sb" deleted

oc get taskruns
NAME               SUCCEEDED   REASON      STARTTIME   COMPLETIONTIME
fruit-backend-sb   Unknown     Pending     4s
fruit-client-sb    True        Succeeded   31m         28m

[metacosm]

If such a command is introduced, it will be as hal component build. Why is such a command needed? What's the point of re-doing a build if the build config isn't changed?

[cmoulliard]

What's the point of re-doing a build if the build config isn't changed?

Simply if you commit a new change within your git hub repo and would like to update the image with this change

[metacosm]

@cmoulliard shouldn't Tekton take care of that scenario?

[cmoulliard]

shouldn't Tekton take care of that scenario?

Tekton has developed a client but it don't support to trigger a new build, will also imply that you install another tool after kubectl, hal ,... https://github.com/tektoncd/cli

[metacosm]

shouldn't Tekton take care of that scenario?

Tekton has developed a client but it don't support to trigger a new build, will also imply that you install another tool after kubectl, hal ,... https://github.com/tektoncd/cli

I meant, shouldn't Tekton rebuild images automatically when the associated repo has changed? Isn't that the whole point?

[cmoulliard]

Tekton rebuild images automatically when the associated repo

This is not supported by the existing Tekton operator which just creates
a pod from task + taskrun where initcontainers = steps of the build