Uploaded image for project: 'IGB'
  1. IGB
  2. IGBF-1764

On-boarding: Step 2 - fork IGB team repository and set up bitbucket pipelines to build installers

        Details

        • Type: Task
        • Status: Closed (View Workflow)
        • Priority: Blocker
        • Resolution: Done
        • Affects Version/s: None
        • Fix Version/s: None
        • Labels:
        • Story Points:
          2
        • Epic Link:
        • Sprint:
          Fall 5 : 14 Oct to 25 Oct, Fall 6 : 28 Oct to 8 Nov, Spring 9 : 25 May to 8 Jun, Summer 3: 6 Jul - 17 Jul, Summer 4: 14 Jul - 28 Jul, Summer 6: 17 Aug - 28 Aug, Summer 7: 31 Aug - 11 Sep, Winter 4 Feb 8 - Feb 19, Winter 5 Feb 22 - Mar 5, Spring 4 2021 May 3 - May 14, Summer 1 2023 May 15, Summer 2 2023 May 29, Fall 3 2023 Oct 2, Spring 5, Fall 4, Fall 5, Fall 6, Fall 7

          Description

          Read modules 2 and 3 the on-line course "Open source programming with IGB."

          Following the instructions, fork the IGB repository and configure your fork to build IGB platform-specific installers.

          To build IGB installers:

          • Log in to bitbucket using your bitbucket user account.
          • Check your account has been added to the Developers group by confirming that you can open and see private (as denoted by a "padlock" icon) IGB project repositories and their files under
            https://bitbucket.org/account/user/lorainelab/projects/IGB
          • Look for the installers private content repository. Follow the instructions there to create repository variables required to build installers.
          • Next, trigger the main branch pipeline. (See Canvas course module Building IGB for how to do this.)
          • Check that files IGB-macos-universal-main.dmg, IGB-windows-amd64-main.exe, IGB-linux-amd64-main.sh, and main.jar got copied to the Downloads section of your fork.

          If you do not see the installers, click the Pipelines button to review any error messages. The main problems people have when using pipelines are:

          • You need to run the pipeline “custom: build-installers-for-dev ” on Bitbucket to create installers, rather than the “custom: manual-build” pipeline which creates the IGB jar file.
          • Something has gone wrong with the Loraine Lab maven repository which hosts dependencies (jar files) needed for building IGB. Check that https://nexus.bioviz.org is available.
          • Your user account does not have access to the installer private content repository. Make sure that you can see the files in the private repository when logged in to bitbucket.
          • Your repository environment variables are not configured properly. Review the installer private contents repository again to make sure all repository environment variables are properly defined.
          • Your account has run out of Bitbucket pipeline minutes. Create a new bitbucket account using an "edu" domain to get more minutes.
          • Double-check that your Bitbucket username is correct by selecting Settings > Personal Bitbucket settings > Account settings > Username.

          Finally, add a new comment with a link to your fork and move this ticket to Needs First Level Review.

          Reviewers should check that:

          • This ticket has a comment with a link to the developer's fork
          • The main branch installers are present in the fork's Downloads section
          • When you view the commit history on the developer's fork, Jira IGBF issue hyperlinks are present.

            Attachments

              Issue Links

              blocks

              Task - A task that needs to be done. IGBF-1464 On-boarding: Step 4 - add your name to Credits

              • Major - Major loss of function.
              • Closed

              Task - A task that needs to be done. IGBF-1573 On-boarding: Step 3 - get familiar with IGB workflow and git

              • Major - Major loss of function.
              • Closed

              Task - A task that needs to be done. IGBF-2412 CLONE - On-boarding: Step 4 - add your name to Credits

              • Major - Major loss of function.
              • Closed
              is blocked by

              Task - A task that needs to be done. IGBF-1763 On-boarding: Step 1 - set up your account in bitbucket and jira

              • Blocker - Blocks development and/or testing work, production could not run.
              • Closed
              is cloned by

              Task - A task that needs to be done. IGBF-3992 CLONE - On-boarding: Step 2 - fork IGB team repository and set up bitbucket pipelines to build installers

              • Blocker - Blocks development and/or testing work, production could not run.
              • Closed
              relates to

              Task - A task that needs to be done. IGBF-3468 Migrate to the latest Notarization tool, notarytool as altool is deprecated

              • Major - Major loss of function.
              • To-Do

              Improvement - An improvement or enhancement to an existing feature or task. IGBF-2404 Suggest improvements to pipelines on-boarding tickets using insights from RW and JW

              • Major - Major loss of function.
              • Closed

                Activity

                Ascending order - Click to sort in descending order
                41 older comments
                Hide
                Permalink
                sjagarap saideepthi jagarapu added a comment -

                was not able open the dmg file from download section saying cannot open the software as it is malicious, followed this canvas course module and resolved https://canvas.instructure.com/courses/1164217/pages/how-to-notarize-installers-for-macos?module_item_id=42905992

                Show
                sjagarap saideepthi jagarapu added a comment - was not able open the dmg file from download section saying cannot open the software as it is malicious, followed this canvas course module and resolved https://canvas.instructure.com/courses/1164217/pages/how-to-notarize-installers-for-macos?module_item_id=42905992
                Hide
                Permalink
                ann.loraine Ann Loraine added a comment -

                Thank you saideepthi jagarapu for the above comment. As you noted, this is an expected behavior on an Apple computer with "factory default" security settings.

                Show
                ann.loraine Ann Loraine added a comment - Thank you saideepthi jagarapu for the above comment. As you noted, this is an expected behavior on an Apple computer with "factory default" security settings.
                Hide
                Permalink
                ann.loraine Ann Loraine added a comment -

                saideepthi jagarapu: Currently this issue is assigned to you. I'm not sure what you want to do with this issue, but I'm guessing you want somebody else to review it. This is confusing because our convention is that if an issue is assigned to a person, then we assume that particular person is either working on it or is planning to work on it later, and does not need anybody else to do anything for it. So, if you forget to un-assign yourself from an issue, it will sit in "needs first level review" for a long time, blocking progress.

                Show
                ann.loraine Ann Loraine added a comment - saideepthi jagarapu : Currently this issue is assigned to you. I'm not sure what you want to do with this issue, but I'm guessing you want somebody else to review it. This is confusing because our convention is that if an issue is assigned to a person, then we assume that particular person is either working on it or is planning to work on it later, and does not need anybody else to do anything for it. So, if you forget to un-assign yourself from an issue, it will sit in "needs first level review" for a long time, blocking progress.
                Hide
                Permalink
                sjagarap saideepthi jagarapu added a comment -

                Sorry Ann Loraine for the confusion caused. It was my mistake to leave the issue assigned to myself, and I’ll be more mindful to un-assign myself in the future to avoid blocking progress.

                Show
                sjagarap saideepthi jagarapu added a comment - Sorry Ann Loraine for the confusion caused. It was my mistake to leave the issue assigned to myself, and I’ll be more mindful to un-assign myself in the future to avoid blocking progress.
                Hide
                Permalink
                uchinta Udaya Chinta added a comment -

                Review:

                1. The ticket has comment with a link to the developer's fork.
                2. The main branch installers are present in the download section.
                3. IGBF issue hyperlinks are present in commit history.

                Moving the ticket to done.

                Show
                uchinta Udaya Chinta added a comment - Review: The ticket has comment with a link to the developer's fork. The main branch installers are present in the download section. IGBF issue hyperlinks are present in commit history. Moving the ticket to done.

                  People

                  • Assignee:
                    sjagarap saideepthi jagarapu
                    Reporter:
                    ann.loraine Ann Loraine
                  • Votes:
                    0 Vote for this issue
                    Watchers:
                    14 Start watching this issue

                    Dates

                    • Created:
                      Updated:
                      Resolved: