-
Bug
-
Resolution: Not A Defect
-
Minor
-
ivy plugin 1.19 on jenkins 1.439
All of my jobs are free-style projects using the ivy plugin to knit
them together.
I'm building an ivy module with different ivy branches. Builds on
any ivy branch trigger all the downstream projects, even the ones that
don't reference that particular branch. Is that expected behavior? I
browsed the source, and it looks like the ivy branch is taken into
account when determining dependencies.
Here's a generalized example,
ivy module Foo with branches A and B
ivy module Bar depends on Foo branch A
When Jenkins builds Foo branch B, it launches a downstream build of
Bar. Bar's dependency has not actually changed because it depends on
Foo branch A. It doesn't seem like the branch is being taken into
account when building the dependency graph.
[JENKINS-11724] Ivy branch not considered when determining dependencies
John McCarthy
created issue -
Gregory Boissinot
made changes -
| Assignee | Original: Timothy Bingaman [ tbingaman ] | New: Gregory Boissinot [ gbois ] |
John McCarthy
made changes -
| Description |
Original:
All of my jobs are free-style projects using the ivy plugin to knit them together. I'm building an ivy module with different ivy branches. Builds on any ivy branch trigger all the downstream projects, even the ones that don't reference that particular branch. Is that expected behavior? I browsed the source, and it looks like the ivy branch is taken into account when determining dependencies. Here's a generalized example, ivy module Foo with branches A and B ivy module Bar depends on Foo branch A When Jenkins builds Foo branch B, it launches a downstream build of Bar. Bar's dependency has not actually changed because it depends on Foo branch A. It doesn't seem like the branch is being taken into account when building the dependency graph. |
New:
All of my jobs are free-style projects using the ivy plugin to knit them together. I'm building an ivy module with different ivy branches. Builds on any ivy branch trigger all the downstream projects, even the ones that don't reference that particular branch. Is that expected behavior? I browsed the source, and it looks like the ivy branch is taken into account when determining dependencies. Here's a generalized example, ivy module Foo with branches A and B ivy module Bar depends on Foo branch A When Jenkins builds Foo branch B, it launches a downstream build of Bar. Bar's dependency has not actually changed because it depends on Foo branch A. It doesn't seem like the branch is being taken into account when building the dependency graph. |
John McCarthy
made changes -
| Fix Version/s | New: current [ 10162 ] | |
| Resolution | New: Not A Defect [ 7 ] | |
| Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
John McCarthy
made changes -
| Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
| Workflow | Original: JNJira [ 141967 ] | New: JNJira + In-Review [ 205476 ] |
