[Automation] Migrate TaaS Jenkins to private Jenkins container in IBM Cloud

[jeffchew]

User Story

As a [user role below]: IBM.com Library Developer

I need to: run all Jenkins jobs within our own private Jenkins instance

so that I can: avoid the costs of the TaaS subscription for a Jenkins instance

Additional information

• The cost for TaaS is $2100/quarter
• According to the ToS for TaaS: https://taas.w3ibm.mybluemix.net/guides/accounts-billing.md#can-i-transfer-a-resource-from-one-team-to-another Before transferring resources, please keep in mind that our Terms of Service does not allow multiple IBM teams to consolidate under a single TaaS account for the sole purpose of reducing costs. Team Accounts should reflect your real-world team structure. Same manager, same developers, same product(s), etc. (See "Creating Teams" above.) Keep in mind that our subscription prices are calculated based on operating costs vs. usage. If teams merge accounts for purely financial reasons, then our prices are more likely to increase for everyone next year. That's obviously not fair to anyone, so please be considerate when deciding when/how to consolidate resources.
• Access to IBM Cloud account: https://ibm.ent.box.com/notes/493566104030
  • Should migrate before the Jenkins instance is deleted:

On February 17th, TaaS will begin enforcing entitlements. If your 
team lacks sufficient entitlements for a certain type of resource, 
all resources of that type will be suspended. (For example, if your 
team has two Jenkins resources but only one Jenkins entitlement, 
both Jenkins will be suspended.) Because of this, it is important 
that you off-board any resources which you no longer wish to keep.

On March 23rd, TaaS may begin permanently deleting suspended resources.

Acceptance criteria

• [ ] Spin up new Jenkins instance in IBM Cloud under the team account
• [ ] Create users for Jenkins (ideally an admin user and stored in 1Password for the core engineering team)
  • [ ] Create users for QA team where they can execute builds manually
  • [ ] Create read-only user and provide in 1Password for all team members
• [ ] Jenkins instance should be behind w3id

[jeffchew]

Closing this issue, been speaking with other squads and we are going to combine and share a subscription with the marketing group.