Add support for the Azure DevOps Marketplace tasks

[jessehouwing]

What would you like Renovate to be able to do?

Currently Renovate only updates the built-in tasks supplied by Microsoft and ignores any task that's installed through the Azure DevOps Marketplace.

Renovate should also suggest updates for any public marketplace installed tasks.

If you have any ideas on how this should be implemented, please tell us here.

• feat(datasource/azure-pipelines-tasks): Adds support for the Azure DevOps Marketplace #19692

Is this a feature you are interested in implementing yourself?

Yes

@JamieMagee To transfer the repo to generate the static file I can initiate a repository transfer:

• Transfer https://github.com/jessehouwing/renovate-azure-devops-marketplace/ to github.com/renovatebot/azure-devops-marketplace/
• fix(data/azure-pipelines-marketplace-tasks): Updates the download location of azure-pipelines-markeplace-tasks. #19764
• Set a PAT in the Actions Secret
• Change the commit details in the repository scripts
• Add me as contributor

[jessehouwing]

@geekzter FYI

[JamieMagee]

We can use this issue to track migrating the repo. This is fine.

[JamieMagee]

@jessehouwing it looks like the order might not be consistent. See #19720

[jessehouwing]

@JamieMagee I had already updated the script to keep order. But the json file in the initial pull-request is from before that update, so we'll have to do at least one big diff commit to fix that in the renovate repo.

I'm seeing one more interesting thing happen in the update from today, and that's from 2 extension that have the same display name (current sort order) (and one should never have been a public extension to begin with it seems) which seem to flip-flop in the data file sigh.

I can see if I can simply order the file alphabetically upon save.

[jessehouwing]

Updated the scripts to sort the json properties alphabetically before save. So it should now be in consistent order.

renovatebot/azure-devops-marketplace@f32bf41

[jessehouwing]

Some things I'd love to (see) add(ed), but would be more work:

• Add support for the preview flag (task.json)
• Add support for the deprecated flag (task.json)
• Add support for the repository attribute (extension.json)
• Add support for marking a whole extension deprecated (no longer returned by the marketplace API)
• Suggest renames (same task.id, higher task.version, different task.name).

These require a change in the datasource structure and I'd need to better understand how renovatebot does that.

[jessehouwing]

• Related: Add support for Azure DevOps API-based datasource #19725

[jessehouwing]

• Related: docs: Update the docs to reflect new Azure DevOps Marketplace functionality #19738

[jessehouwing]

• Related: Support for Azure Pipelines Tasks #15818

[JamieMagee]

@JamieMagee To transfer the repo to generate the static file I can initiate a repository transfer:

I received your invitation, but I don't have the necessary permissions in the renovatebot org. You'll need to invite @rarkins to do the repo transfer.

[rarkins]

Because it's a personal repo, I think you'll actually need to transfer it to me (@rarkins) before I can then transfer it into the renovatebot org

[HonkingGoose]

That's correct, see this quote from the GitHub Docs: ¹

Repository transfers and organizations

To transfer repositories to an organization, you must have repository creation permissions in the receiving organization. If organization owners have disabled repository creation by organization members, only organization owners can transfer repositories out of or into the organization.

Once a repository is transferred to an organization, the organization's default repository permission settings and default membership privileges will apply to the transferred repository.

Footnotes

1. https://docs.github.com/en/repositories/creating-and-managing-repositories/transferring-a-repository#repository-transfers-and-organizations ↩

[jessehouwing]

@JamieMagee @rarkins can you overwrite the AZURE DEVOPS PAT secret with a fresh PAT (expires yearly) with 'Marketplace (read)' permissions on the 'all accessible organisations' scope?

[JamieMagee]

@rarkins I don't have permissions. You'll need to do it.

[rarkins]

I've updated it with my own PAT now. What's the best way to make sure it's working?

[jessehouwing]

Running the workflow manually. I just triggered a run.

[jessehouwing]

PAT is working. I increased the logging a little bit to be sure :).

A new run is both fetching new extensions and downloading the vsix files.

@rarkins To what should I change the committer? Right now it's still making all commits (including bot) under my name. Should it be Renovate(bot)? Or is it ok to leave it under my creds for now?

[rarkins]

I'm not sure it makes any difference? If not then fine to leave as is until it's necessary to change