Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

transportation-data-utils: Travis/CircleCI pipeline #234

Closed
6 tasks done
sergiogcx opened this issue Jun 18, 2019 · 2 comments
Closed
6 tasks done

transportation-data-utils: Travis/CircleCI pipeline #234

sergiogcx opened this issue Jun 18, 2019 · 2 comments
Assignees
@sergiogcx
Labels
Need: 2-Should Have May be painful to leave out, but the solution is still viable Service: Dev Infrastructure and engineering Type: Enhancement Request for an improvement to existing functionality in an application Workgroup: DTS Data and Technology Services
Milestone
Sprint 1

Comments

@sergiogcx
Copy link

sergiogcx commented Jun 18, 2019 •
edited
Loading

As part of Epic #191 This issue is made to track the development of a pipeline in Travis

  • Retains monorepo architecture
  • Identifies changes to specific libraries
  • Builds libraries automatically
  • Shuts down build if package version already exists.
  • Can detect current environment: master (production), any other branch: dev
  • Test deployment to pypi under dev
@sergiogcx sergiogcx added Need: 2-Should Have May be painful to leave out, but the solution is still viable Service: Dev Infrastructure and engineering Type: Enhancement Request for an improvement to existing functionality in an application labels Jun 18, 2019
@sergiogcx sergiogcx self-assigned this Jun 18, 2019
@sergiogcx sergiogcx added this to the Sprint 1 milestone Jun 18, 2019
@sergiogcx sergiogcx changed the title transportation-data-utils: Travis pipeline transportation-data-utils: Travis/CircleCI pipeline Jun 19, 2019
@sergiogcx
Copy link
Author

  • I've set up a repo and I have connected it to CircleCI, it looks like it runs and it is properly configured to listen to any events to the two branches: master and dev.

  • The script can build packages, but nothing will be deployed until we have a well-tested environment detection script (currently working on this).

Also: Using CircleCI instead of Travis because lately travis has been very unreliable, often does not trigger builds at all and there have been outages. Using CircleCI (also free for open source) in the mean time.

@sergiogcx sergiogcx added the Workgroup: DTS Data and Technology Services label Jun 20, 2019
@sergiogcx
Copy link
Author

Also done, moving to Review/QA.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sergiogcx sergiogcx

Labels
Need: 2-Should Have May be painful to leave out, but the solution is still viable Service: Dev Infrastructure and engineering Type: Enhancement Request for an improvement to existing functionality in an application Workgroup: DTS Data and Technology Services
Projects
None yet
Milestone
Sprint 1
Development

No branches or pull requests
1 participant
@sergiogcx