#1609 importArchive should error if the build lacks the given type
Closed: Fixed 4 years ago by tkopecek. Opened 4 years ago by mikem.

Disclaimer: workflows based on importArchive are a bad idea and should be avoided

It is currently possible (though not usually advisable) to add an archive to an existing build using the importArchive call. As it stands, the call can add any type of archive to any type of build. However, this creates a consistency problem because it can result in a build that has archives of a type that it itself does not have.

It is possible to add new types to a build via the create[Image|Maven|Win]Build calls. Users that must use a workflow like this should also be updating the build type.

The importArchive() call should refuse to proceed if the build does not have the given type (which is one of the arguments to the call).


Metadata Update from @tkopecek:
- Custom field Size adjusted to None

4 years ago

Side note: this is sort of a follow-up to #1507

Metadata Update from @tkopecek:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

4 years ago

Metadata Update from @jcupova:
- Issue tagged with: testing-done

4 years ago

Metadata Update from @dgregor:
- Issue assigned to tkopecek

4 years ago

Login to comment on this ticket.

Metadata
Related Pull Requests
  • #1614 Closed 4 years ago