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

[Epic] Post actions improvements #2490

Closed
12 of 14 tasks
AR-May opened this issue Sep 2, 2020 · 2 comments
Closed
12 of 14 tasks

[Epic] Post actions improvements #2490

AR-May opened this issue Sep 2, 2020 · 2 comments
Labels
Cost:M Work that requires one engineer up to 2 weeks parent:1240298 Priority:2 Work that is important, but not critical for the release triaged The issue was evaluated by the triage team, placed on correct area, next action defined. User Story A single user-facing feature. Can be grouped under an epic.
Milestone

Comments

@AR-May
Copy link
Member

AR-May commented Sep 2, 2020

As a customer, I want post actions fixed, so that I can build richer templates.

There are plenty of issues concerning post actions. Here is a user story where we will track them all:

  • Bug: In post action "Add projects to a solution file" primaryOutputs does not always updated with sourceName. It also does not work with -o and -n option.
  • Bug: In post action "Restore NuGet packages" primaryOutputs are not updated with sourceName.
  • Bug: primaryOutputs are not updated with sourceName when a target directory is specified.
  • Bug: Template engine not renaming primaryOutputs paths
  • Bug: Post action "Run script" does not work with "preferNameDirectory" : "true", and, probably, with -o option as well.
  • Bug: Post-actions chmod - No such file.
  • Bug: Post-action chmod fails on Mac.
  • Bug: "Change file permissions" step reported as failed on OSX Mojave.
  • Bug: Localization bug.
  • Doc: Update the post action registry wiki page.
    Registry Document.
  • Feature: For post action "Add projects to a solution file" add an option for specifying the solution directory.
  • Feature: Loss of functionality in post action "Restore NuGet packages".

Low prio:

  • Feature: Update PostAction with symbol parameters to cmd file arguments.

Gathering feedback:

  • Feature: Post Action Certificate Creation.
@AR-May AR-May added triaged The issue was evaluated by the triage team, placed on correct area, next action defined. Epic Groups multiple user stories. Can be grouped under a theme. labels Sep 2, 2020
@AR-May AR-May self-assigned this Sep 10, 2020
@AR-May AR-May removed their assignment Oct 19, 2020
@vlada-shubina vlada-shubina self-assigned this Oct 29, 2020
@donJoseLuis donJoseLuis added User Story A single user-facing feature. Can be grouped under an epic. Cost:M Work that requires one engineer up to 2 weeks Priority:2 Work that is important, but not critical for the release parent:1240298 and removed Epic Groups multiple user stories. Can be grouped under a theme. labels Dec 19, 2020
@donJoseLuis donJoseLuis changed the title [EPIC] Fix post actions As a customer, I want post actions fixed, so that I can build richer templates Dec 19, 2020
@vlada-shubina vlada-shubina removed their assignment Jan 21, 2021
@vlada-shubina vlada-shubina added the Epic Groups multiple user stories. Can be grouped under a theme. label Jan 28, 2021
@vlada-shubina vlada-shubina added this to the Backlog milestone Mar 3, 2021
@StingyJack
Copy link

I would like to add "Some documentation artifact that clearly explains what a post action is and what it does" I can read through a bunch of code and issues here and glean some understanding but there isnt anything I can find that says what they are.

@vlada-shubina vlada-shubina changed the title As a customer, I want post actions fixed, so that I can build richer templates Post actions improvements Jun 1, 2021
@vlada-shubina vlada-shubina removed the Epic Groups multiple user stories. Can be grouped under a theme. label Jul 27, 2021
@vlada-shubina vlada-shubina changed the title Post actions improvements [Epic] Post actions improvements Jul 27, 2021
@vlada-shubina
Copy link
Member

I'm closing this epic, 2 remaining issues will be kept individually in the backlog.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Cost:M Work that requires one engineer up to 2 weeks parent:1240298 Priority:2 Work that is important, but not critical for the release triaged The issue was evaluated by the triage team, placed on correct area, next action defined. User Story A single user-facing feature. Can be grouped under an epic.
Projects
None yet
Development

No branches or pull requests

4 participants