How about change taskid to task-name and runid to auto-increase number

General Discussions
#1

current id:

  • runid: 0000001f0p639-0000000000015
  • taskid: 36e7f0e9-ead5-4907-82c2-94ab2e0e7996
http://xx/user/sam/projects/gin-admin-dvp.proj/runs/0000001f0p639-0000000000015/tasks/36e7f0e9-ead5-4907-82c2-94ab2e0e7996

we can see the seq generated in action.go: newRun recreateRun:

	// generate a new run sequence that will be the same for the run and runconfig
	seq, err := sequence.IncSequence(ctx, h.e, common.EtcdRunSequenceKey)
	if err != nil {
		return nil, err
	}
	id := seq.String()
#2

I’ve changed in my case: /user/sam/projects/fk-onemall.proj/runs/0000j/tasks/tsk.603fec4

agola_url_runs_tasks
agola_url_runs_tasks1291×631 28.8 KB

  • the seq for runid, just got the last 5 chars.
  • the uuid for taskid, just with sha1 and get first 7 chars just like git commit sha1.
#3

@huapox The unique identifier of a run and a task are their ID. What you’re asking is using something different in the agola-web uri (not related to agola gateway API) but I don’t see a great gain changing them to something different. Using the run number could be possible but will require an additional api and using the task name will make ugly urls since task names can be long with all the non “standard” chars URI escaped.

This won’t work: the last 5 chars of a run id are not enough to unique distinguish it (you need the full runid) and the sha1 (both full or truncated) of the task name isn’t reversible so we cannot retrieve the task id from it.