Unverified Commit c928d6ef authored by boklm's avatar boklm
Browse files

Bug 41281: Remove `fetch: 1` from nightly target

With rbm#40079, when we have `fetch: if_needed` (the default), rbm will
now do a fetch when `git_hash` is pointing to a branch. The reason for
setting `fetch: 1` in the nightly target was that we are using some
git branches, which were not fetched automatically with `fetch:
if_needed`.
parent 8ed4f7ac
Loading
Loading
Loading
Loading
+0 −1
Original line number Diff line number Diff line
@@ -252,7 +252,6 @@ targets:
      alpha: 1
      channel: alpha
  nightly:
    fetch: 1
    var:
      nightly: 1
      channel: nightly
+9 −10
Original line number Diff line number Diff line
@@ -114,15 +114,14 @@ targets:

  nightly:

    ### By default 'fetch' is set to 1 for nightly builds, meaning that new
    ### commits will be fetched automatically during each build. You can
    ### disable this during development if you want to do rebuilds to test
    ### a specific change, but don't want rebuilds caused by unrelated
    ### changes, or if you want to decide at which point new commits are
    ### fetched. When 'fetch' is set to 'if_needed', new commits will only
    ### be fetched if the selected commit (or branch, or tag) is not present,
    ### which means that existing branches won't be updated. In that case
    ### you can fetch new commits by running 'make fetch'.
    #fetch: 'if_needed'
    ### By default 'fetch' is set to 'if_needed', meaning that new
    ### commits will be fetched automatically during each build, if
    ### the selected commit (or branch, or tag) is not present, or if
    ### it is pointing to a branch. With the nightly target, some projects
    ### are pointing to a branch, meaning they will be fetched for each
    ### build. If you want to disable automatic fetchs and decide at
    ### which point new commits are fetched, you can set 'fetch' to '0'
    ### and run `make fetch` when you want to fetch new commits.
    #fetch: 0

# vim: filetype=yaml sw=2