Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

This page will detailed detail the configurations that are most commonly used.  Of course, if appropriate, other configurations not covered in this page will may need to be set.

  1. Create a new Freestyle Project.
  2. Determine whether or not to Discard Old Builds.  In the example below, only 30 builds are kept.



  3. Determine whether or not Enable project-based security.  In the example below, a metagroup is used to secure the project and assign permissions.

  4. Determine whether or not to Restrict where the project can be run.  In the example below, the project can only be run on the master machine labelled "redsky" and none of the six slaves that belong to "redsky" are specified.

    fdsg

  5. Under Source Code Management, provide the url to the repo, and also add any credential (sshkey) that is valid.  In the example below, the repo url is git@github.com:ACME-Climate/ACME.git, and the credential that was added is Jim Foucar's GitHub sshkey.

    Image Added

  6. Specify a branch of the repo to track.  In the example below, the specified branch is */master.

    Image Added
  7. Under Additional Behaviours, you could Add two: Check out to a sub-directory and Advanced sub-modules behaviours.  Click the Add drop-down menu to add additional behaviours.

    Image Added

    In the example below, ACME has been designated as the local subdirectory where the Git repo will be checked out.  Additionally, submodules processing has been disabled.

    Image Added

  8. Under Build Triggers, check the box named Build periodically.  In the example below, the Schedule is set for a run at 10:00 PM every night.

    Image Added
  9. gdfsgh
  10. sdh