taskcluster icon indicating copy to clipboard operation
taskcluster copied to clipboard

Clean up decision task hacks

Open imbstack opened this issue 4 years ago • 12 comments

Things noted by @tomprince:

  1. TransformSequence in taskcluster/src/transforms/__init__.py is not necessary
  2. We should also change basestring to six.text_type wherever used
  3. Consider using level-1 vs level-3 to keep decision task stuff on its own workers instead of a decision worker.

imbstack avatar May 28 '20 22:05 imbstack

3. Consider using level-1 vs level-3 to keep decision task stuff on its own workers instead of a decision worker.

More specifically to keep pull-request tasks on separate workers for tasks for pushes. This is probably most relevant for any tasks that are involved in the release process (including the decision task).

tomprince avatar May 28 '20 22:05 tomprince

Also, consider moving tascluster/src to taskcluster/taskcluster_taskgraphor the like. The convention releng has adopted is_taskgraph` for local taskgraph code. (Though nothing enforces this or cares)

tomprince avatar May 28 '20 22:05 tomprince

I want to work on this .

090max avatar May 31 '20 19:05 090max

Thank you, @090max! I've assigned you. All work takes place inside the taskcluster directory and .taskcluster.yml file. Let me know if you want any further pointers.

imbstack avatar Jun 01 '20 15:06 imbstack

sure

090max avatar Jun 02 '20 06:06 090max

Just had these two queries:

  1. Can you please elaborate task 3 "Consider using level-1 vs level-3 to keep decision task stuff on its own workers instead of a decision worker."
  2. By removing TransformSequence , all the functions proceeding @transforms.add would no longer be required in the file taskcluster/src/transforms/init.py , right ?

090max avatar Jun 02 '20 07:06 090max

Can you please elaborate task 3 "Consider using level-1 vs level-3 to keep decision task stuff on its own workers instead of a decision worker."

Ah sure. Right now we use a release worker to do certain kinds of tasks and ci to do others. These are defined in taskcluster/ci/config.yml and you can see where they're used elsewhere. We could instead use workers called ci-level-1 and ci-level-2 or something like that.

Now that I think about it, this is a slightly more involved change. Let's do the other changes first and then we can handle this in a followup once you're more familiar with this code.

By removing TransformSequence , all the functions proceeding @transforms.add would no longer be required in the file taskcluster/src/transforms/__init__.py , right ?

I believe that's correct, yeah.

imbstack avatar Jun 02 '20 16:06 imbstack

I am new to contributing to open source orgs Can I work on this?

5aumy4 avatar Jul 06 '20 15:07 5aumy4

Is this issue fixed?. because it is still among the unassigned task on codetribute.

abdelquodr avatar Apr 11 '22 16:04 abdelquodr

@ahal I think you are the most relevant person to ask if this is still needed? Thanks

lotas avatar Apr 11 '22 16:04 lotas

Yeah, a bit of a mish mash of things in here, but looks like it's mostly still relevant. We should be running the decision task with Python 3 at least now, so the basestring stuff should be fixed.

ahal avatar Apr 11 '22 17:04 ahal

hello @ahal and @lotas; can you please assign this to me. I'm interested in working on it. Thanks

abdelquodr avatar Apr 19 '22 14:04 abdelquodr