Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Current »

Tl;dr

Jira

  •  Add a closing comment with details such as confirmation from customer date/time (optional: attach email from customer, giving the confirmation),
  •  Complete Stash steps and Move the ticket over to the "DONE" column

Stash

  •  For new projects:
    1.  Create a new repository in FNF project
    2.  Clone repository to local (using Sourcetree)
    3.  Add the nitro file from Leap TEST environment
    4.  Commit and push to master branch,
      •  When committing, include the Jira ticket, by using a string "JIRA <TICKET>" (example: "JIRA FEB-530")
    5.  Create a tag and notify Jason Card mention: the tag name, and request for it to be released into PROD
  •  For existing projects:
    •  Do the Steps 2 - 5, above

Confluence

Update the project requirements page, under the FEB space:

  •  For new projects:
    •  Update the Document Properties box:
      •  "Document Status" at the top and other sections (such as Pre Go-Live, etc,) as necessary
  •  For existing projects:
    •  Update the "Post Production Enhancement List" section
      •  "Description" to capture enhancement(s) at high-level; provide a link: if you have a detailed documentation page (where this set of enhancements are captured in detail)
      •  After receiving confirmation/notification for Stash step #14 (that the tag has been deployed in PROD)
        •  Update Version (in PROD) property (Document Properties box) with the latest version


Jira

Update the ticket

  1.  Provide the following details in comments: Who approved the go-live and when.
    1.  If possible/you'd like to, attach the email confirmation to the comments
  2.   AFTER completing the Stash steps: Move the ticket from "UNDER REVIEW" to "DONE" column; ensure that the ticket's workflow status is "DONE" and not "CANCELLED"
  3. Notify Jason Card that the "Tag" has been created (Stash step #14)


Stash

Brand New Project

Step #Description
1
  1.  Login to stash: https://stash.uconn.edu/

  2.  Navigate to FEB Nitro Files (FNF) project

  3.  Provided you have the necessary privileges, click on the "Create repository" button, top-right



  4.  Provide an appropriate name and then click on the "Create repository" button



  5.  Clone repository to local — this is your local repository

    Tip

    Establish clean directory structure for all your Leap apps; directory within this structure is where you will create a local repository 

    1.  Create a project directory for this Leap application

    2.  Use git/bash command:

      Make sure you are inside the project folder of where you want to clone and then execute the following command:


      Clone Remote Repository
      git clone REPOSITORY_URL



  6.  Open up Sourcetree software

  7.  Add a new repository, by clicking on the "+" at the top:



    1.  Click on Add at the top:



    2.  Click on "Browse"



    3.  Navigate to where you cloned locally (Step 5.a., above)

    4.  And click on "Select Folder" ---- ensure that the folder you select has a .git folder (this is a hidden folder — so you might not see it, based on your settings), as shown below



    5.  Finally, click "Add"





  8. Go to Leap TEST environment and export the project (if you have not done it already) and save it locally

    Heads-up!

    Unless you have been told otherwise: Make sure that the "Include submission data?" checkbox is  not checked!

  9.  Locate the *.nitro_s file that you downloaded from Leap TEST environment and move it to the directory of your project's local repository (same folder as 5.a., above)

  10.  Sourcetree automatically detects a change in your local repository; it's time to stage your project's nitro file — Reference the screenshot below for steps 10.a & 10.b:



    1.  Your project's nitro file will be listed under "Unstaged files" section

    2.  Click on

      Note:

      You should only see your project's nitro file... if you see more than one file, reach out to our Leap group and troubleshoot as to why that is the case

  11.  Select "File Status" tab (if it is not selected)

  12.  Committing to remote repository — Reference the screenshot below for steps 12.a — 12.c:
     


    1.  Under comments, use the following format — the first comment line & its format is mandatory! 

      JIRA XXX-###
YOUR COMMENTS

      (where XXX-### is the Jira ticket; you can provide your comments after that)

      Tip

      If you have a prior commit, you may click on the  icon and select an applicable comment. If you select a comment from history, be sure to change the ticket number (and the comment, if applicable)!

    2.  Click on

    3.  Click on the  button


 Notify Jason Card that the tag "TAG_NAME" (from #13.c.i) has been created and it's ready to go live.

Here's my notification template... feel free to use it, if it helps!

Note:

Change the  [PLACEHOLDERS] and in order to ensure the accuracy: the verbiage, as necessary!


TemplateExample

[SALUTATION]


At your earliest convenience / release-to-prod window, please release the following tag to PROD and let me know when it's done.

[MyTagName_v#.#]

Details:

The new set of changes requested by  [DEPARTMENT_NAME] for their  [LEAP_APPLICATION_NAME] form have been addressed.

It has gone through UAT and the customer has confirmed & approved the changes and has requested for it to go live!

All Confluence, Jira, & Stash steps have been completed.


[CLOSING/SIGNATURE]

Hello Jason,


At your earliest convenience / release-to-prod window, please release the following tag to PROD and let me know when it's done.


TaxAndCompliance-ForeignNationalInformation_v1.1


Details:

The new set of changes requested by the Tax and Compliance Department for their Foreign National Information form have been addressed.


It has gone through UAT and the customer has confirmed & approved the changes and has requested for it to go live!


All Confluence, Jira, & Stash steps have been completed.


Best,

Rush
13 Goes HERE
Create a tag

 a. Click on "master" under "BRANCHES" on the left; notice that middle pane



 b. Right-click on the commit that you did in (Step 12, above) and select "Tag..."



c. In the resulting dialog box, under "Add Tag" tab

i. Provide a name for the tag (this convention should work: "NAME_OF_REPO_v#.#", where #.# is your version number e.g. 1.0, 1.1, etc.)

ii. Select/check the  checkbox

iii. Click the  button

1414 GOES HERE

Existing Project

Step #Description
1

On local machine, navigate to the project's directory where you have established your local repository

Note:

You should only see the .git folder and the previously exported nitro file:

2Delete the nitro_s file from this directory
3Continue from Step 8 of "Brand New Project"


Confluence

Pre Go-Live

If the project requirements page does not have a pre go-live log, add it and follow the Developer checklist. Sample Pre Go-Live log, below.

Go-Live DateDate of Last Deploy in TESTCustomer/Designee Sign-off & Date/TimeVersionDeveloperJIRA TicketRelease to PROD Date/TimeReleased By





@DEVELOPER NAME

  • JavaScript files: using minified versions?
  • Confirm Security/Access Control (as reflected on THIS page)
  • Update Jira Ticket
  • Stash component
  • Queued for Go-Live! / Notify Jason Card
  • Update project's requirements page on Confluence
  • Notify customer/team post deployment with relevant link(s)











  • No labels