Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Only approved model editors can update the working branch in Gerrit. 
  • To be a model editor you must undergo Papyrus training and attend the weekly Papyrus modeling sessions.
  • Once you have finished making your model changes, make sure you "save" them in Papyrus, by selecting "File→ Save", or select the file icon.
  • Next, you will need to go to the "Git" perspective to select the files you have changed and prepare them for uploading to Gerrit
    • Go to the Git perspective by selecting  "Window->Perspective→Open Perspective→ Other → Git" like this:  
    • Once in the Git Perspective, select the repository where you have changed the files.


    • Select the "Git Staging" tab in the lower right hand portion of your screen (it might also be on the right-hand side of your screen based on your layout) it looks like this: with a little green down-arrow
    • You will see the files that you have changed in the "Unstaged changes". Note: If there is a file there that you did not intend to change, right-click on that file and select "Replace with HEAD revision". That will revert any unwanted changes you may have made.
    • STAGE CHANGES: Select the files that you did change, right-click and select "Add to index", Or, as a shortcut, you can select the little green "plus" sign that will add the files for you:

                     

    • The Git Staging window looks like this: Image Added
    • after you hit the green "++" it looks like this: Image Added
    • Once they have been added, they will show up in the "Staged Changes
    • COMMIT MESSAGE: Next you will need to prepare to "Commit and Push" your changes. Position your cursor in the "Commit Message" window
    • Add a commit message indicating the change you have done, i.e. "Added new diagram to service model" then carriage return twice so that you will have a blank line after your message.
    • You can then optionally add a more detailed message about the change.
    • JIRA TICKET: Next, you will have to associate the change to a JIRA ticket. Add on the line after the blank line:  Issue-ID: MODELING-104
    • Note that there is a blank between ":" and "M".  The JIRA ticket MODELING-104 is a general ticket for changes to the working branch.
    • Note that Git will generate a "Change id" for you, so you don't need to manually add one.
    • Then you will need to "Sign-off" on the change by selecting the "Sign-off" button. This is the "Pen" icon next to the "Commit Message". Select that icon

...