Ticket #1602 (closed defect: fixed)
Opened 2012-12-11T14:01:04-06:00
Last modified 2013-01-09T09:53:13-06:00
incremental-deploy.sh does not deploy POMs
| Reported by: | curtis | Owned by: | dscho |
|---|---|---|---|
| Priority: | major | Milestone: |
|
| Component: | Build System | Version: | |
| Severity: | serious | Keywords: | |
| Cc: | Blocked By: | ||
| Blocking: | #1608 |
Description
Jenkins deployed the 2.0.0-beta5 release for us, but that job uses incremental-deploy.sh, which skips POM deployment. However, we must deploy the POMs for our releases to be valid and usable.
For 2.0.0-beta5 I deployed the POMs manually (mvn deploy in strategic places) but it would be best to fix incremental-deploy.sh to do the right thing.
Change History
comment:1 Changed 2012-12-11T14:14:51-06:00 by curtis
Last edited 2012-12-11T14:15:24-06:00
by curtis
comment:3 Changed 2012-12-27T11:14:14-06:00 by curtis
- Milestone changed from imagej2-b6-legacy to imagej2-b7-ndim-data
comment:4 Changed 2013-01-09T09:53:13-06:00 by dscho
- Status changed from new to closed
- Resolution set to fixed
This should be fixed in https://github.com/fiji/fiji/commit/12d47a22313b787697ed132def5da1bd91a83286.
Last edited 2013-01-09T09:53:34-06:00
by dscho
This problem shed some light on the fact that the ImageJ job was doing too much by doubling as our release job. It runs unit tests, does performance analysis, and triggers downstream builds ImageJ-style and [ ImageJ-tutorials), none of which make sense when building the release.
So I created a new parameterized ImageJ-release job just for that, which is stripped down. It also builds all the UIs (-P all), which the regular ImageJ job does not do, which kept artifacts like ij-ui-awt from ever being released.
I removed the branch parameter from the ImageJ job, since it is no longer necessary.
And I updated the `release-steps.txt` accordingly too.