1 Replies - 495 Views - Last Post: 30 July 2017 - 11:21 AM

#1 Luca91  Icon User is offline

  • New D.I.C Head

Reputation: 0
  • View blog
  • Posts: 29
  • Joined: 19-August 13

Does it make sense to use jenkins/travis without unit test?

Posted 30 July 2017 - 10:55 AM

Let's suppose that I've a github repo with an opensource project, without any unit test (for example no junit), but with frequent commits/pushes.
Does it make sense to have jenkins/travis integration in this repo? Please tell me the advantages and disadvantages if any.

Thanks
Is This A Good Question/Topic? 0
  • +

Replies To: Does it make sense to use jenkins/travis without unit test?

#2 Skydiver  Icon User is offline

  • Code herder
  • member icon

Reputation: 5898
  • View blog
  • Posts: 20,138
  • Joined: 05-May 12

Re: Does it make sense to use jenkins/travis without unit test?

Posted 30 July 2017 - 11:21 AM

Yes. Even without unit tests continuous integration is still useful because you can still catch merge errors and build errors earlier rather than later.

Jenkins can be used more than just for continuous integration. It can be used for automated deployments, a cron job substitute, a distributed build manager, etc. I used it to do automated mirroring of disjoint repositories, as well as a scheduled backup manager because our corporate based team does not backup dev systems -- only QA and Production.
Was This Post Helpful? 1
  • +
  • -

Page 1 of 1