Uploaded image for project: 'Forge'
  1. Forge
  2. FORGE-1550

Set up a CI build server that is publicly visible and works.

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Critical Critical
    • None
    • None
    • None
    • None

          [FORGE-1550] Set up a CI build server that is publicly visible and works.

          Daniel Cunha (soro) (Inactive) added a comment -

          I understand, the problem is builder on Windows.
          I don't know a free CI with windows.

          Doesn't viable execute builder on Windows in another server?

          Daniel Cunha (soro) (Inactive) added a comment - I understand, the problem is builder on Windows. I don't know a free CI with windows. Doesn't viable execute builder on Windows in another server?

          George Gastaldi added a comment -

          Hi Daniel,

          We are actually using TeamCity for our builds. Since the build is quite large and should also run in Windows boxes, I think we can stick with it. The only problem is that it is not publicly available. We also have a Forge CI server on Cloudbees (https://forge.ci.cloudbees.com) but we are not really using it atm, given the Windows requirement.

          George Gastaldi added a comment - Hi Daniel, We are actually using TeamCity for our builds. Since the build is quite large and should also run in Windows boxes, I think we can stick with it. The only problem is that it is not publicly available. We also have a Forge CI server on Cloudbees ( https://forge.ci.cloudbees.com ) but we are not really using it atm, given the Windows requirement.

          George Gastaldi added a comment -

          Inspite of having a Cloudbees instance available (http://forge.ci.cloudbees.com/), we are using TeamCity

          George Gastaldi added a comment - Inspite of having a Cloudbees instance available ( http://forge.ci.cloudbees.com/ ), we are using TeamCity

          George Gastaldi added a comment -

          Hi Daniel,

          We are actually using TeamCity for our builds. Since the build is quite large and should also run in Windows boxes, I think we can stick with it. The only problem is that it is not publicly available. We also have a Forge CI server on Cloudbees (https://forge.ci.cloudbees.com) but we are not really using it atm, given the Windows requirement.

          George Gastaldi added a comment - Hi Daniel, We are actually using TeamCity for our builds. Since the build is quite large and should also run in Windows boxes, I think we can stick with it. The only problem is that it is not publicly available. We also have a Forge CI server on Cloudbees ( https://forge.ci.cloudbees.com ) but we are not really using it atm, given the Windows requirement.

          Daniel Cunha (soro) (Inactive) added a comment -

          The project use travis: https://github.com/forge/core/blob/master/.travis.yml
          Do you want migrate to other service?

          Daniel Cunha (soro) (Inactive) added a comment - The project use travis: https://github.com/forge/core/blob/master/.travis.yml Do you want migrate to other service?

          Daniel Cunha (soro) (Inactive) added a comment - - edited

          http://www.travis-ci.org
          Eg. https://travis-ci.org/aeshell/aesh
          WDYT?

          Daniel Cunha (soro) (Inactive) added a comment - - edited http://www.travis-ci.org Eg. https://travis-ci.org/aeshell/aesh WDYT?

          George Gastaldi added a comment -

          Some options include:

          George Gastaldi added a comment - Some options include: Cloudbees: http://www.cloudbees.com/ Dedicated Jenkins instance (Eg: http://ci.hibernate.org/ )

            Unassigned Unassigned
            lincolnthree Lincoln Baxter III (Inactive)
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: