Ticket #1990 (closed enhancement: fixed)

Opened 2 years ago

Last modified 10 months ago

Source steps falling back to complete re-initialization should not be mandatory

Reported by: ayust Owned by:
Priority: major Milestone: 0.8.+
Version: 0.8.4 Keywords: master-side-source-steps
Cc: in3xes, pawel.worach@…

Description

Currently, if a source step fails to successfully update to a particular revision, it will always fall back to trying to re-initialize the repository. For some workflows, this is very bad, and it would be highly preferable for the build to just fail instead of nuking its repository and re-creating it.

The fallback to a full re-clone (or the equivalent in whatever VCS is being used) should be an option (it's fine if it defaults to on) that can be disabled if necessary.

Change History

comment:1 Changed 2 years ago by dustin

  • Cc in3xes added
  • Milestone changed from undecided to 0.8.5

comment:2 Changed 2 years ago by pworach

  • Cc pawel.worach@… added

comment:3 Changed 17 months ago by tom.prince

  • Milestone changed from 0.8.6 to undecided

It looks like none of the master-side source steps do do a full clone on failed update (excpet git which defaults to off).

Perhaps there should be an option to do a full clone on failure. But this seems like it fixed with the new steps?

comment:4 Changed 16 months ago by dustin

  • Keywords master-side-source-steps added
  • Milestone changed from undecided to 0.8.+

comment:5 Changed 10 months ago by in3xes

Yes, except git no other source checkout step removes the build directory. And git has option not to do it. Should we close it?

comment:6 Changed 10 months ago by dustin

  • Status changed from new to closed
  • Resolution set to fixed

Sounds closed to me, then!

Note: See TracTickets for help on using tickets.