Migrate Share builds on Bamboo to Travis

Description

From

We have now decided to consolidate our build infrastructure into Travis. The main reasons being:

  • Travis is already used by a lot of teams and it fits the requirements

  • Bamboo is not a priority area for Atlassian and as such there hasn't been much investment on it

  • Alfresco decided to move away from Rackspace. It will be a huge tasks to even lift and shift Bamboo to AWS so it was decided that best to invest in moving out from it

More details can be found here: https://w3.alfresco.com/confluence/display/APO/Travis+as+our+single+build+infrastructure+system

Share currently uses Bamboo for a number of projects, these build plans require deactivating and where relevant migrating to the new platform

Acceptance Criteria

  • Identified build plans in Bamboo have their configuration set to disabled or plans deleted

  • All development branches are deleted from Bamboo, leaving only 1 branch

  • For supported projects

    • Alternative Travis configurations exist in source control

    • New builds are tested and running successfully

    • All software publishing can take place via Travis

Build plans

Note: Already disabled build plans are not shown

Plan name

Link

Num branches

Share 6.x

SHARE-SHR6

29

Share-PO 6.0

ALF-S6

1

Surf

SRVC-SRF

9

Surf (JDK8)

SRVC-SJ8

3

Aikau

MOD-AIKAU

4

Activity

Show:
Andreea Nechifor
October 31, 2020, 1:10 AM

I create a document with. all the projects and travis build : https://w3.alfresco.com/confluence/display/TECH/Travis+migration+Backporting+Team+APPS1

Assignee

Andreea Nechifor

Reporter

Will Abson

Labels

Release Train

None

Delivery Team

Team Apps1

Story Points

13

Priority

Epic Name

Migrate Share builds on Bamboo to Travis