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

Update tasks to azure-pipelines-task-lib 2.8.0 #10762

Merged
merged 22 commits into from
Jul 3, 2019

Conversation

joshmgross
Copy link
Member

@joshmgross joshmgross commented Jun 26, 2019

Updating a bunch of related tasks to azure-pipelines-task-lib 2.8.0

Change list:

  • ANTV1

    • Updated to azure-pipelines-task-lib 2.8.0
  • GradleV2

    • Updated to azure-pipelines-task-lib 2.8.0
    • Removed dependency on Common/Utility-Common (getSystemAccessToken
  • MavenV2

    • Updated to azure-pipelines-task-lib 2.8.0
    • Switched from pacakaging-common-old to packaging-common
  • MavenV3

    • Updated to azure-pipelines-task-lib 2.8.0
    • Switched from pacakaging-common-old to packaging-common
    • Ported over legacy tests
  • XamarinAndroidV1

    • Updated to azure-pipelines-task-lib 2.8.0
    • Removed dependency on Common/MSBuildHelpers (getMSBuildPath)
    • Ported over legacy tests
  • PublishCodeCoverageResultsV1

    • Bumped version for changes in Common\codecoverage-tools
    • A resource string was automatically updated as well
  • Common tasks updated to azure-pipelines-task-lib 2.8.0:

    • codecoverage-tools
    • codeanalysis-common
    • java-common
  • packaging-common-old

    • Removed as it was only used by MavenV2 and MavenV3 while they were on the old task lib version

Tested via build canaries for ANTV1, GradleV2, MavenV2, MavenV3, XamarinAndroidV1, and PublishCodeCoverageResultsV1

Copy link
Member

@keljos keljos left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The changes to the ANT, Gradle, and Maven tasks look good to me. Once the tests have been updated and pass, I will approve the changes.

@joshmgross
Copy link
Member Author

I ported over the legacy tests for MavenV3 and XamarinAndroid. Most of them are intact, a few I deemed were duplicate and not ported over. For Maven, I left out a few that weren't really testing anything MavenV3 task-related (such as common package tests) as those are now mocked out.

@@ -0,0 +1,271 @@
/// <reference path="../../definitions/mocha.d.ts"/>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

how come we're adding a legacy test?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These tests were in the Maven legacy tests and don't need to be ported over.

@joshmgross joshmgross merged commit a243210 into master Jul 3, 2019
@joshmgross joshmgross deleted the users/jogros/update-task-libs branch July 3, 2019 18:25
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