Uploaded image for project: 'Modules'
  1. Modules
  2. MODULES-4448

Implement i18n Step for Linux Adhoc Pipelines

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
    • Template:
    • Acceptance Criteria:
      Hide

      the i18n script should be able to pull or push to any GITHUB_REF passed through the adhoc init job.

      Show
      the i18n script should be able to pull or push to any GITHUB_REF passed through the adhoc init job.
    • Team:
      Modules
    • Story Points:
      3
    • Sprint:
      Modules - Engineering Backlog
    • QA Risk Assessment:
      Needs Assessment

      Description

      Because our adhoc Jenkins pipelines can use any branch of any user's public repo, our i18n script as it is now will break. A few things need to happen before i18n can be a part of our adhoc pipelines:

      1. GITHUB_REF from the adhoc init job needs to be written to ci.props so it can be passed to the i18n job. Since this variable is also used by the Jenkins Git plugin, it doesn't persist between jobs on its own unless its set by the plugin, which its not in this case.

      2. A conditional block needs to be added to our i18n script. Perhaps something along these lines:

      if [[ $GITHUB_REF ]]; then
          REF_TO_CHECKOUT=$GITHUB_REF
      else
          REF_TO_CHECKOUT={scm_branch}
      fi
      

      This new var also needs to replace {scm_branch} throughout the script

      ::UPDATE::
      Since the creation of this ticket, the git logic has been removed from the modules i18n script which negates the need for any changes to be made. All we need to do now is add the i18n job to the adhoc pipelines in last position.

        Attachments

          Activity

            People

            Assignee:
            Unassigned
            Reporter:
            eric.putnam Eric Putnam
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Zendesk Support