It seems that both GeoTools and GeoServer’s release-jira jobs fail (and have been failing for 9 and 6 months) - I assume this is related to the change of jira hosting, is there a new script or manual step that I need to run before hitting publish for the new releases?
Cheers
Ian
Ian Turton
Ian,
yes, the Jira API changed when we moved from Codehaus and the Python script is broken. Not as smooth as your last releases in 2014.
The undocumented manual procedure is to for each project:
- Manually perform the release in Administration / Versions and release the version using the "..." on the right-hand side
- Create the next unreleased version for the series (13.6 and 2.7.6 in your case.
- Search for problematic fixVersions, that is, Unresolved issues (Open, In Progress, or Reopened) for the released version and read the comments. Was the issue really resolved for this version? If so, leave the fixVersion, otherwise remove it. fixVersion means was fixed; this is not an aspirational field. If you are really puritanical you can check all issues to make sure no Resolved issues were Won't-Fix: these should have no fixVersions. This is more than the script ever did but is worth the effort for a good quality changelog. And on maintenance the effort is tiny.
GeoTools 13.5:
https://osgeo-org.atlassian.net/projects/GEOT/versions/12000
For this issue with fixVersion 13.5 Torben wrote: "I was not able to backport to 13.x due to API incompatibility." so remove 13.5 from fixVersions (you can also search the git log of 13.x for the issue):
https://osgeo-org.atlassian.net/browse/GEOT-5318
GeoServer 2.7.5:
https://osgeo-org.atlassian.net/projects/GEOS/versions/11902
Looks like there is already a GS 2.7.6 version (naughty, naughty, Jira makes is far too easy for an administrator to inadvertently add a version); someone has an issue for it:
https://osgeo-org.atlassian.net/browse/GEOS-7353
Comment here suggests Andrea backported to 2.7.x, so check GitHub commits to confirm and change the fixVersion from 2.7.6 to 2.7.5:
https://github.com/geoserver/geoserver/pull/1375
All the issues for 2.7.5 are resolved so just release the version and you have your changelog.
Kind regards,
Ben.
On 21/12/15 21:19, Ian Turton wrote:
It seems that both GeoTools and GeoServer's release-jira jobs fail (and
have been failing for 9 and 6 months) - I assume this is related to the
change of jira hosting, is there a new script or manual step that I need to
run before hitting publish for the new releases?Cheers
Ian
------------------------------------------------------------------------------
_______________________________________________
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel
--
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/>
New Zealand
On Mon, Dec 21, 2015 at 12:16 PM, Ben Caradoc-Davies <ben@anonymised.com>
wrote:
Looks like there is already a GS 2.7.6 version (naughty, naughty, Jira
makes is far too easy for an administrator to inadvertently add a
version); someone has an issue for it:
https://osgeo-org.atlassian.net/browse/GEOS-7353
Comment here suggests Andrea backported to 2.7.x, so check GitHub
commits to confirm and change the fixVersion from 2.7.6 to 2.7.5:
https://github.com/geoserver/geoserver/pull/1375
Since GeoServer 2.7.5 was already out I had to mark the new ticket
for 2.7.6, even if 2.7.5 was not released in Jira.
Can you explain what's wrong with that?
Cheers
Andrea
*Geosolutions' Winter Holidays from 24/12 to 6/1*
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549
http://www.geo-solutions.it
http://twitter.com/geosolutions_it
*AVVERTENZE AI SENSI DEL D.Lgs. 196/2003*
Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
loro utilizzo è consentito esclusivamente al destinatario del messaggio,
per le finalità indicate nel messaggio stesso. Qualora riceviate questo
messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
darcene notizia via e-mail e di procedere alla distruzione del messaggio
stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
utilizzarlo per finalità diverse, costituisce comportamento contrario ai
principi dettati dal D.Lgs. 196/2003.
The information in this message and/or attachments, is intended solely for
the attention and use of the named addressee(s) and may be confidential or
proprietary in nature or covered by the provisions of privacy act
(Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
Code).Any use not in accord with its purpose, any disclosure, reproduction,
copying, distribution, or either dissemination, either whole or partial, is
strictly forbidden except previous formal approval of the named
addressee(s). If you are not the intended recipient, please contact
immediately the sender by telephone, fax or e-mail and delete the
information in this message that has been received in error. The sender
does not give any warranty or accept liability as the content, accuracy or
completeness of sent messages and accepts no responsibility for changes
made after they were sent or for other risks which arise as a result of
e-mail transmission, viruses, etc.
-------------------------------------------------------
On 22/12/15 00:21, Andrea Aime wrote:
On Mon, Dec 21, 2015 at 12:16 PM, Ben Caradoc-Davies <ben@anonymised.com>
wrote:Looks like there is already a GS 2.7.6 version (naughty, naughty, Jira
makes is far too easy for an administrator to inadvertently add a
version); someone has an issue for it:
https://osgeo-org.atlassian.net/browse/GEOS-7353
Comment here suggests Andrea backported to 2.7.x, so check GitHub
commits to confirm and change the fixVersion from 2.7.6 to 2.7.5:
https://github.com/geoserver/geoserver/pull/1375Since GeoServer 2.7.5 was already out I had to mark the new ticket
for 2.7.6, even if 2.7.5 was not released in Jira.
Can you explain what's wrong with that?
I see no tag for 2.7.5 in GitHub nor a call for artifact testing. Are you sure this issue was omitted? In the release procedure, release in Jira is the first step. If the steps were performed out of order and you are sure 2.7.5 has been tagged successfully, then 2.7.6 is fine if you are sure your issue is not fixed in 2.7.5.
I see this release job for 2.7.5:
http://ares.boundlessgeo.com/jenkins/view/release/job/geoserver-release/91/consoleText
But a release job can be re-run and a new tag can be made, for example, if there is a problem with the build. Only the publish step pushes the tag to GitHub.
Kind regards,
--
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/>
New Zealand
And this is what I recommend when encountering issues with an unexpected fixVersion:
On 22/12/15 00:16, Ben Caradoc-Davies wrote:
so check GitHub commits to confirm
--
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/>
New Zealand
On Mon, Dec 21, 2015 at 12:33 PM, Ben Caradoc-Davies <ben@anonymised.com>
wrote:
I see no tag for 2.7.5 in GitHub nor a call for artifact testing. Are you
sure this issue was omitted? In the release procedure, release in Jira is
the first step. If the steps were performed out of order and you are sure
2.7.5 has been tagged successfully, then 2.7.6 is fine if you are sure your
issue is not fixed in 2.7.5.
The "first step" has been skipped for months, the others are carried out in
sequence, starting from a fixed revision,
provided as a parameter to the build server
That is the revision that gets tagged when performing "release publish",
which is the very last step in the release process.
Ian has already made the testing artifacts based on that revision.
If you have doubts other have made mistakes here is a procedure for you to
double check that,
without publicly pointing fingers, wasting other people time, and keep on
advancing doubts even
when the others tell you it's fine:
* Get the testing artifacts (the bin one)
* Unpack them locally
* Grab one GeoServer jar, reach for META-INF/MANIFEST.MF and get the
revision out of it:
Manifest-Version: 1.0
Build-Timestamp: 19-Dec-2015 11:32
Implementation-Title: REST Configuration Service Module
Implementation-Version: 2.7.5
*Git-Revision: 26f0e9f908fcc279652e0c2622db1028469be16e*
Built-By: jenkins
Specification-Vendor: The Open Planning Project
Application-Name:
GeoServerModule: core
Created-By: Apache Maven 3.0.4
Implementation-Vendor: The Open Planning Project
Iteration-Name:
Implementation-Vendor-Id: org.geoserver
Build-Jdk: 1.7.0_51
Project-Version: 2.7.5
Specification-Title: REST Configuration Service Module
Specification-Version: 2.7.5
Archiver-Version: Plexus Archiver
As an alternative, reach to the build job used to build the artifacts
and check its parameters:
http://ares.boundlessgeo.com/jenkins/view/release/job/geoserver-release/91/parameters/
Now that you have the revision, compare with the commit logs on 2.7.x:
https://github.com/geoserver/geoserver/commits/2.7.x
So yes, the commit is not in 2.7.5 and the ticket it's thus correctly
tagged for 2.7.6 (unless Ian needs to rebuild from a newer revision, but
it does not seem that's the case).
Cheers
Andrea
*Geosolutions' Winter Holidays from 24/12 to 6/1*
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549
http://www.geo-solutions.it
http://twitter.com/geosolutions_it
*AVVERTENZE AI SENSI DEL D.Lgs. 196/2003*
Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
loro utilizzo è consentito esclusivamente al destinatario del messaggio,
per le finalità indicate nel messaggio stesso. Qualora riceviate questo
messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
darcene notizia via e-mail e di procedere alla distruzione del messaggio
stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
utilizzarlo per finalità diverse, costituisce comportamento contrario ai
principi dettati dal D.Lgs. 196/2003.
The information in this message and/or attachments, is intended solely for
the attention and use of the named addressee(s) and may be confidential or
proprietary in nature or covered by the provisions of privacy act
(Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
Code).Any use not in accord with its purpose, any disclosure, reproduction,
copying, distribution, or either dissemination, either whole or partial, is
strictly forbidden except previous formal approval of the named
addressee(s). If you are not the intended recipient, please contact
immediately the sender by telephone, fax or e-mail and delete the
information in this message that has been received in error. The sender
does not give any warranty or accept liability as the content, accuracy or
completeness of sent messages and accepts no responsibility for changes
made after they were sent or for other risks which arise as a result of
e-mail transmission, viruses, etc.
-------------------------------------------------------
On 22/12/15 02:21, Andrea Aime wrote:
If you have doubts other have made mistakes
No, just a discussion of how to check in the context of a manual Jira release. I am happy for a release manager to check any fixVersions I set. I am just suggesting one way it might be done.
So yes, the commit is not in 2.7.5 and the ticket it's thus correctly
tagged for 2.7.6 (unless Ian needs to rebuild from a newer revision, but
it does not seem that's the case).
Great!
Kind regards,
--
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/>
New Zealand