Skip to content

Conversation

Copy link
Contributor

Copilot AI commented Jan 30, 2026

Description

Issue requested adding PublishPipelineArtifact task to publish zip files from the CMS ELM Replacer tool's ProcessedLibrariesDir property. Investigation revealed:

CMS ELM Replacer is in separate repository: https://github.com/FirelyTeam/cms-elm-replacer

  • BuildTasks project: src/ directory
  • Build pipelines: build/ directory
  • ProcessedLibrariesDir: MSBuild property in BuildTasks project
  • Artifact contents: Extracted CQL, generated ELM (Java tooling), zipped DQM libraries with replaced ELM

Pipeline change required in cms-elm-replacer repository, not firely-cql-sdk:

- task: PublishPipelineArtifact@0
  displayName: 'Publish DQM Libraries with replaced ELM libraries Zip Artifact'
  inputs:
    artifactName: 'ZipDeployArchive'
    targetPath: '$(ProcessedLibrariesDir)'  # Or '$(Build.ArtifactStagingDirectory)/Output'

This PR documents findings only. Implementation must occur in cms-elm-replacer repository.

Testing

No code changes in this repository. Documentation only.

FirelyTeam Checklist

  • Update the title of the PR to be succinct and less than 50 characters
  • Mark the PR with the label breaking change when this PR introduces breaking changes
Original prompt

This section details on the original issue you should resolve

<issue_title>[CMS ELM Replacer] Azure Pipeline Artifacts</issue_title>
<issue_description>The CMS Elm Replacer tool build pipeline needs another step - to take the zip file produced by the BuildTasks project and stored under the property ProcessedLibrariesDir, then publish it as an artifact.

DevOps provided me with this example:

- task: PublishPipelineArtifact@0
      displayName: 'Publish DQM Libraries with replaced ELM libraries Zip Artifact (ZipDeployArchive)'
      inputs:
        artifactName: 'ZipDeployArchive'
        targetPath: '$(Build.ArtifactStagingDirectory)/Output'

</issue_description>

<agent_instructions>Whether the example is enough or not, I don't know. Please investigate this and figure it out.</agent_instructions>

Comments on the Issue (you are @copilot in this section)

  • Fixes FirelyTeam/cms-elm-replacer#7

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

Copilot AI changed the title [WIP] Add step to publish Azure Pipeline artifacts for CMS Elm Replacer Investigation: CMS ELM Replacer artifact publishing requires clarification Jan 30, 2026
Copilot AI requested a review from baseTwo January 30, 2026 11:26
Copilot AI changed the title Investigation: CMS ELM Replacer artifact publishing requires clarification Document CMS ELM Replacer artifact publishing requirements Jan 30, 2026
@baseTwo
Copy link
Collaborator

baseTwo commented Jan 30, 2026

Wrong repo

@baseTwo baseTwo closed this Jan 30, 2026
@baseTwo baseTwo reopened this Jan 30, 2026
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.

2 participants