Uploaded image for project: 'Infrastructure'
  1. Infrastructure
  2. INFRA-2522

Add s390x jenkins agent to ci.jenkins.io

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      This new node requires the label 's390x' and being reachable from an ssh bastion

        Attachments

          Activity

          Hide
          markewaite Mark Waite added a comment - - edited

          The s390 agent needs to be run through ssh. I have the agent running by creating:

          • Jenkins master agent defined for the destination host
          • configure destination host with my agent user `jagent` (please choose a different agent user name for ci.jenkins.io)
          • configure the destination host to install:
            • Agent jar file (3.36.1 in the case I'm using)
            • AdoptOpenJDK Java 8 OpenJ9 (OS package for openjdk 8 has no JIT, too slow)
            • AdoptOpenJDK Java 11 OpenJ9
            • Maven 3.6.3
            • Git
            • Git LFS (installed by download from GitHub release, not by installation from OS)
          Show
          markewaite Mark Waite added a comment - - edited The s390 agent needs to be run through ssh. I have the agent running by creating: Jenkins master agent defined for the destination host configure destination host with my agent user `jagent` (please choose a different agent user name for ci.jenkins.io) configure the destination host to install: Agent jar file (3.36.1 in the case I'm using) AdoptOpenJDK Java 8 OpenJ9 (OS package for openjdk 8 has no JIT, too slow) AdoptOpenJDK Java 11 OpenJ9 Maven 3.6.3 Git Git LFS (installed by download from GitHub release, not by installation from OS)
          Hide
          slide_o_mix Alex Earl added a comment -

          Mark Waite I believe this is completed, correct?

          Show
          slide_o_mix Alex Earl added a comment - Mark Waite I believe this is completed, correct?
          Hide
          markewaite Mark Waite added a comment -

          I think it is complete. Olivier Vernin and I discussed some form of automation that could record the configuration of the agent in a git repository. However, I'm not aware of that type of configuration storage elsewhere on ci.jenkins.io. We have the config history plugin files that are stored on ci.jenkins.io, so that provides some record of the configuration.

          Show
          markewaite Mark Waite added a comment - I think it is complete. Olivier Vernin and I discussed some form of automation that could record the configuration of the agent in a git repository. However, I'm not aware of that type of configuration storage elsewhere on ci.jenkins.io. We have the config history plugin files that are stored on ci.jenkins.io, so that provides some record of the configuration.

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            olblak Olivier Vernin
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: