Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for project scoped package feeds. #42

Merged
merged 2 commits into from
Jan 20, 2020
Merged

Support for project scoped package feeds. #42

merged 2 commits into from
Jan 20, 2020

Conversation

amrock-my
Copy link
Contributor

As there was no contribution.md file, I wasn't sure if our contributions should include updating the version numbers for the task/extension.

Also, I had the task extract the name portion of the package instead of the guid for readability in YAML pipeline files. The classic build/release editors are not affected. Feel free to alter this if necessary.

Finally, I added a schema mark for the task.json file. I could get the local tests to run properly because my work machine has group policies around powershell scripts and our security team blocks certain network traffic. But I did verify this works by creating a private package and using that in our pipeline.

Azure Artifacts now supports both organization and project scoped package feeds. The fully qualified name for the package feeds is {ProjectName}/{PackageFeed} (project scoped) or {PackageFeed} (organization scoped).
Updated the powershell script to extract out the projectId if the package feed was project scoped. Either the project feed remains an empty string or the projectId is populated and the feedName is shortened using the String.Split() function.
@amrock-my
Copy link
Contributor Author

One thing to note, this does not resolve the issue around the Release views dropdown properly populating because the "tfs:feed" url is not the correct url for project scoped feeds.

@jzserai
Copy link

jzserai commented Jan 13, 2020

One thing to note, this does not resolve the issue around the Release views dropdown properly populating because the "tfs:feed" url is not the correct url for project scoped feeds.

Won't this still prevent it from working in the Classic editor and in Release pipelines?

@juritdev
Copy link

When will this pull request be completed? We are waiting for this fix so we can use this task again. thanks

@renevanosnabrugge
Copy link
Owner

I will merge this. Can you send me your Azure DevOps organizations, so I can share the extension with you privately and you can test it as well? Thanks!

@jzserai
Copy link

jzserai commented Jan 15, 2020 via email

@renevanosnabrugge
Copy link
Owner

renevanosnabrugge commented Jan 15, 2020 via email

@juritdev
Copy link

juritdev commented Jan 15, 2020 via email

@renevanosnabrugge
Copy link
Owner

pushed a new version to your accounts

@jzserai
Copy link

jzserai commented Jan 16, 2020 via email

@juritdev
Copy link

juritdev commented Jan 17, 2020 via email

@renevanosnabrugge
Copy link
Owner

Hi. The extension I shared with you is a private extension with version 1.5.2 .You can unfortunately not run side by side. So uninstall the extension (or use another account) and reinstall the private extension from the extension page..

@juritdev
Copy link

Thanks Rene, it is working now!

@juritdev
Copy link

although using a agent from our local pool we still get the error: "##[error]Cannot bind argument to parameter 'Path' because it is null."

With the default azure pipelines agens it's working fine.

@jzserai
Copy link

jzserai commented Jan 17, 2020 via email

@renevanosnabrugge
Copy link
Owner

renevanosnabrugge commented Jan 17, 2020 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants