Uploaded image for project: 'Moodle app'
  1. Moodle app
  2. MOBILE-3501

Create task to push a branch and automatically update tracker issue

    XMLWordPrintable

    Details

    • Testing Instructions:
      Hide

      This issue needs to be tested in a dev environment, not in a real device.

      Test previous tasks

      1. Edit src/config.json and change the value of any field (e.g. appname).
      2. Edit src/lang/en.json and add a new string: e.g. "aaa": "Test".
      3. Run "gulp". Check that no error is raised.
      4. Open src/assets/lang/en.json. Check that the new string is there.
      5. Open src/configconstants.ts. Check that the field you edited in step 1 has the new value.
      6. Remove the folder www/templates.
      7. Run "gulp copy-component-templates". Check that the folder www/templates has been re-created.
      8. Run "gulp combine-scss". Check that a file named "combined.scss" is created at the root of the project with all the scss.

      Test push

      1. In Jira, create an issue or choose one that hasn't been done yet.
      2. In your dev environment, make some changes and commit them. Please make sure that the commit message has a wrong issue number in the commit name (or no issue number at all).
      3. Run "gulp push".  Check that it displays an error saying that the issue number is wrong.
      4. Type 'n' or just Enter to cancel the task.
      5. Change the commit name to have the right issue number.
      6. Run "gulp push" again. It might ask you for your tracker URL, username and password.
      7. Check that the branch is pushed to your "origin" remote. Check that the Jira issue is updated with the repository, branch name and diff URL.
      8. Now run "gulp push --patch". Check that a ".patch" file is uploaded in the tracker issue.
      Show
      This issue needs to be tested in a dev environment, not in a real device. Test previous tasks Edit src/config.json and change the value of any field (e.g. appname). Edit src/lang/en.json and add a new string: e.g. "aaa": "Test". Run " gulp ". Check that no error is raised. Open src/assets/lang/en.json. Check that the new string is there. Open src/configconstants.ts. Check that the field you edited in step 1 has the new value. Remove the folder www/templates. Run " gulp copy-component-templates ". Check that the folder www/templates has been re-created. Run " gulp combine-scss ". Check that a file named "combined.scss" is created at the root of the project with all the scss. Test push In Jira, create an issue or choose one that hasn't been done yet. In your dev environment, make some changes and commit them. Please make sure that the commit message has a wrong issue number in the commit name (or no issue number at all). Run " gulp push ".  Check that it displays an error saying that the issue number is wrong. Type 'n' or just Enter to cancel the task. Change the commit name to have the right issue number. Run " gulp push " again. It might ask you for your tracker URL, username and password. Check that the branch is pushed to your "origin" remote. Check that the Jira issue is updated with the repository, branch name and diff URL. Now run " gulp push --patch ". Check that a ".patch" file is uploaded in the tracker issue.
    • Affected Branches:
      MOODLE_39_STABLE
    • Fixed Branches:
      MOODLE_39_STABLE
    • Pull Master Branch:
    • Sprint:
      Moodle App 3.9.3

      Description

      Create task to push a branch and automatically update tracker issue, similar to "mdk push -t".

        Attachments

          Activity

            People

            Assignee:
            dpalou Dani Palou
            Reporter:
            dpalou Dani Palou
            Peer reviewer:
            Pau Ferrer
            Integrator:
            Juan Leyva
            Tester:
            Pau Ferrer
            Participants:
            Component watchers:
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:
              Fix Release Date:
              30/Nov/20