Skip to content

Project not maintained and contributors not being able to run tests #16709

Open
@svrooij

Description

@svrooij

Is this projected maintained at all? With 140 open pull requests it seems like Microsoft is ditching Azure Pipelines very soon.

I've been waiting to get feedback on #16283 for ages (3 months) and I'm for sure not the only one, someone playing knock-knock

Then I decided I'm no longer going to wait, and build/publish/deploy as custom version myself.
Since the tasks I changed already seem to have some tests, I tried if I could run those tests. And it's hard.... See #16708

Issues I'm having trying to deploy my own version:

  • All tasks seem to be tested by some hidden Azure Pipeline
  • On my PR the automated test run is not executed (probably because of some access issue)
  • If it where to be executed, I would not be able to see the results anyway
  • Trying to run the tests locally returns a ENOENT no such file ... /.taskkey until you create the C:\temp\agent\home\temp\ folder
  • Tasks don't seem to be published as an extension but seem to be published as nugets

Is it worth investing time to deploy custom versions of existing tasks?
Will my PR get any feedback in the next week?
Is there an escalation plan when codeowners are awol?

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions