Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Client state and artifact install scripts - i1

Description

This is partial implementation (first iteration) of .
The purpose of this split is to have a simpler but workable solution sooner (without server-side and no retry support).

Risk & mitigation

None

Market Goal

None
100% Done
Loading...

Checklist

Activity

Show:

Kristian Amlie May 18, 2017 at 11:13 AM

Updated . , I'll leave to you to create an extra task to fix this, if you need it. Or of it's quick just do it without a task.

Marcin Pasinski May 18, 2017 at 7:01 AM

yup, please do. I agree as well. Since you will rewrite this maybe you can also add `Error` action for all the scripts so that and will have a chance to review and comment on this one as well.

Next, I think we need to be explicit about the "API" for the scripts itself, so you can mention that no extra parameters will be passed while calling the scripts and nothing but return code will be read after scripts is executed.

Kristian Amlie May 18, 2017 at 5:26 AM

Agree with both points! , should I just go ahead and change that in the proposal?

Drew Moseley May 16, 2017 at 6:59 PM

Seems reasonable to me. Simplicity is preferable for this initial rollout and I agree there doesn't seem to be much difference between the Artifact Pre/Post/Install states. As for naming, I don't have much to add; as long as it's consistent.

eystein.maloy.stenberg May 16, 2017 at 6:53 PM

maybe you have some comments on the above as well?

Fixed

Details

Assignee

Reporter

Labels

Epic Name

Goals

None

Priority

Backlog

yes

Zendesk Support

Checklist

Created April 26, 2017 at 4:39 PM
Updated June 25, 2024 at 12:02 PM
Resolved September 5, 2017 at 6:06 PM