You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@brooklyn.apache.org by Geoff Macartney <ge...@cloudsoftcorp.com> on 2017/03/07 13:44:00 UTC
[NOTICE] switch to Java 8 as "official target" for Apache Brooklyn
Jenkins builds
hello all,
In the mail thread "[PROPOSAL] Remove java 7 support" [1] it has been
proposed to "1. Update our jenkins etc to always build/run with Java 8."
I intend to start changing the build configurations, and I'm going to
propose doing so from tomorrow (Wednesday) at 10.00 UTC.
I'm hoping that normal service should continue uninterrupted, but please
let me know if you want me to hold off doing this, and when would be
preferable.
kind regards
Geoff
[1]
https://lists.apache.org/thread.html/196c758afed8091ffefa8f3bdd4792fae6a29fa1cf6f0dd86e20f821@%3Cdev.brooklyn.apache.org%3E
Re: [NOTICE] switch to Java 8 as "official target" for Apache
Brooklyn Jenkins builds
Posted by Geoff Macartney <ge...@cloudsoftcorp.com>.
hi all,
I'm happy to report that the brooklyn-dist-master build has been switched
over to JDK 8 now. That's the last of the builds to switch over, so I hope
we can get on to the next of Aled's proposed steps as time permits.
regards
Geoff
On Fri, 10 Mar 2017 at 09:42 Geoff Macartney <
geoff.macartney@cloudsoftcorp.com> wrote:
> hello all,
>
> An update on this topic - I've investigated the problem with
> brooklyn-dist-master at Java 1.8 and it seems not to be related to the
> Apache Brooklyn code base, but is something to do with the Jenkins
> configuration. I have raised an INFRA issue [1] to request help resolving
> this.
>
> In the mean time I have set the build back to running with Java 1.7.
>
> Will post updates when there are further developments.
>
> best regards
> Geoff
>
> [1] https://issues.apache.org/jira/browse/INFRA-13638
>
> On Thu, 9 Mar 2017 at 10:11 Geoff Macartney <
> geoff.macartney@cloudsoftcorp.com> wrote:
>
> Thanks Richard, will do that.
>
> regards
> Geoff
>
> On Thu, 9 Mar 2017 at 09:43 Richard Downer <ri...@apache.org> wrote:
>
> Hi Geoff,
>
> Unless the situation has moved on while I've not been paying attention, the
> integration tests have always been a mixed bag, with several failures some
> of which are nondeterministic[1], so I wouldn't worry too much about those.
>
> I'd suggest you subscribe to the "builds@apache.org" list which is for
> discussion about the Jenkins build machines. If you're going to be working
> with Jenkins for a while it's worth subscribing so you will be aware of
> outages and changes. Archived at
> https://lists.apache.org/list.html?builds@apache.org
>
> Richard.
>
>
> [1] or at least deterministic under a set of characteristics that we don't
> understand...
>
>
> On 8 March 2017 at 17:36, Geoff Macartney <
> geoff.macartney@cloudsoftcorp.com
> > wrote:
>
> > An update on the above topic.
> >
> > I have updated (or not, as noted) the following builds to Java 8, giving
> > the results shown as compared against the status before I made the
> update,
> > where "ok" means successful build, "-" is disabled, "x" is failing, and
> > "unstable" is, er, unstable (yellow).
> >
> > Most builds look ok, the two of concern are brooklyn-dist-master and
> > brooklyn-master-build. Also the brooklyn-integration-tests had 28 test
> > failures rather than the previous 20, but I don't know how consistent the
> > number of failures are from run to run, will investigate further.
> >
> > For brooklyn-dist-master what seems to be happening is that the java
> build
> > of all modules succeeds but there are errors in the archiving stage, or
> the
> > job times out. (I do note that some runs get scheduled on slaves that
> > appear from the "System Information" tab to not have Java 8 on them, but
> > will need to look into that some more).
> >
> > For brooklyn-master-build again I've got timeouts.
> >
> > I shall continue investigating these tomorrow. Please be patient until
> we
> > get this sorted out. (And any advice is welcome!)
> >
> > regards
> > Geoff
> >
> > before after updated to 8? Name
> >
> > ok ok updated brooklyn-client-master
> > ok ok updated
> > brooklyn-client-pull-requests
> > ok x updated brooklyn-dist-master
> > ok ok updated
> brooklyn-dist-pull-requests
> > unstable unstable updated brooklyn-integration-tests
> > ok ok updated brooklyn-library-master
> > x ok updated
> > brooklyn-library-pull-requests
> > x rebuilding brooklyn-master-build
> > - - updated
> brooklyn-master-integration
> > x x updated
> > brooklyn-master-windows; same failure as before so looks ok
> > ok ok updated brooklyn-server-master
> > x ok updated
> > brooklyn-server-pull-requests
> > ok ok updated brooklyn-ui-master
> > ok ok updated brooklyn-ui-pull-requests
> > - not updated incubator-brooklyn-master-
> > build
> > - not updated
> > incubator-brooklyn-master-integration
> > - not updated incubator-brooklyn-master-
> > windows
> > - not updated incubator-brooklyn-pull-
> > requests
> >
> >
> >
> >
> >
> >
> >
> > On Tue, 7 Mar 2017 at 13:44 Geoff Macartney <
> > geoff.macartney@cloudsoftcorp.com> wrote:
> >
> > > hello all,
> > >
> > > In the mail thread "[PROPOSAL] Remove java 7 support" [1] it has been
> > > proposed to "1. Update our jenkins etc to always build/run with Java
> 8."
> > >
> > > I intend to start changing the build configurations, and I'm going to
> > > propose doing so from tomorrow (Wednesday) at 10.00 UTC.
> > >
> > > I'm hoping that normal service should continue uninterrupted, but
> please
> > > let me know if you want me to hold off doing this, and when would be
> > > preferable.
> > >
> > > kind regards
> > > Geoff
> > >
> > > [1]
> > > https://lists.apache.org/thread.html/196c758afed8091ffefa8f3bdd4792
> > fae6a29fa1cf6f0dd86e20f821@%3Cdev.brooklyn.apache.org%3E
> > >
> >
>
>
Re: [NOTICE] switch to Java 8 as "official target" for Apache
Brooklyn Jenkins builds
Posted by Geoff Macartney <ge...@cloudsoftcorp.com>.
hello all,
An update on this topic - I've investigated the problem with
brooklyn-dist-master at Java 1.8 and it seems not to be related to the
Apache Brooklyn code base, but is something to do with the Jenkins
configuration. I have raised an INFRA issue [1] to request help resolving
this.
In the mean time I have set the build back to running with Java 1.7.
Will post updates when there are further developments.
best regards
Geoff
[1] https://issues.apache.org/jira/browse/INFRA-13638
On Thu, 9 Mar 2017 at 10:11 Geoff Macartney <
geoff.macartney@cloudsoftcorp.com> wrote:
> Thanks Richard, will do that.
>
> regards
> Geoff
>
> On Thu, 9 Mar 2017 at 09:43 Richard Downer <ri...@apache.org> wrote:
>
> Hi Geoff,
>
> Unless the situation has moved on while I've not been paying attention, the
> integration tests have always been a mixed bag, with several failures some
> of which are nondeterministic[1], so I wouldn't worry too much about those.
>
> I'd suggest you subscribe to the "builds@apache.org" list which is for
> discussion about the Jenkins build machines. If you're going to be working
> with Jenkins for a while it's worth subscribing so you will be aware of
> outages and changes. Archived at
> https://lists.apache.org/list.html?builds@apache.org
>
> Richard.
>
>
> [1] or at least deterministic under a set of characteristics that we don't
> understand...
>
>
> On 8 March 2017 at 17:36, Geoff Macartney <
> geoff.macartney@cloudsoftcorp.com
> > wrote:
>
> > An update on the above topic.
> >
> > I have updated (or not, as noted) the following builds to Java 8, giving
> > the results shown as compared against the status before I made the
> update,
> > where "ok" means successful build, "-" is disabled, "x" is failing, and
> > "unstable" is, er, unstable (yellow).
> >
> > Most builds look ok, the two of concern are brooklyn-dist-master and
> > brooklyn-master-build. Also the brooklyn-integration-tests had 28 test
> > failures rather than the previous 20, but I don't know how consistent the
> > number of failures are from run to run, will investigate further.
> >
> > For brooklyn-dist-master what seems to be happening is that the java
> build
> > of all modules succeeds but there are errors in the archiving stage, or
> the
> > job times out. (I do note that some runs get scheduled on slaves that
> > appear from the "System Information" tab to not have Java 8 on them, but
> > will need to look into that some more).
> >
> > For brooklyn-master-build again I've got timeouts.
> >
> > I shall continue investigating these tomorrow. Please be patient until
> we
> > get this sorted out. (And any advice is welcome!)
> >
> > regards
> > Geoff
> >
> > before after updated to 8? Name
> >
> > ok ok updated brooklyn-client-master
> > ok ok updated
> > brooklyn-client-pull-requests
> > ok x updated brooklyn-dist-master
> > ok ok updated
> brooklyn-dist-pull-requests
> > unstable unstable updated brooklyn-integration-tests
> > ok ok updated brooklyn-library-master
> > x ok updated
> > brooklyn-library-pull-requests
> > x rebuilding brooklyn-master-build
> > - - updated
> brooklyn-master-integration
> > x x updated
> > brooklyn-master-windows; same failure as before so looks ok
> > ok ok updated brooklyn-server-master
> > x ok updated
> > brooklyn-server-pull-requests
> > ok ok updated brooklyn-ui-master
> > ok ok updated brooklyn-ui-pull-requests
> > - not updated incubator-brooklyn-master-
> > build
> > - not updated
> > incubator-brooklyn-master-integration
> > - not updated incubator-brooklyn-master-
> > windows
> > - not updated incubator-brooklyn-pull-
> > requests
> >
> >
> >
> >
> >
> >
> >
> > On Tue, 7 Mar 2017 at 13:44 Geoff Macartney <
> > geoff.macartney@cloudsoftcorp.com> wrote:
> >
> > > hello all,
> > >
> > > In the mail thread "[PROPOSAL] Remove java 7 support" [1] it has been
> > > proposed to "1. Update our jenkins etc to always build/run with Java
> 8."
> > >
> > > I intend to start changing the build configurations, and I'm going to
> > > propose doing so from tomorrow (Wednesday) at 10.00 UTC.
> > >
> > > I'm hoping that normal service should continue uninterrupted, but
> please
> > > let me know if you want me to hold off doing this, and when would be
> > > preferable.
> > >
> > > kind regards
> > > Geoff
> > >
> > > [1]
> > > https://lists.apache.org/thread.html/196c758afed8091ffefa8f3bdd4792
> > fae6a29fa1cf6f0dd86e20f821@%3Cdev.brooklyn.apache.org%3E
> > >
> >
>
>
Re: [NOTICE] switch to Java 8 as "official target" for Apache
Brooklyn Jenkins builds
Posted by Geoff Macartney <ge...@cloudsoftcorp.com>.
Thanks Richard, will do that.
regards
Geoff
On Thu, 9 Mar 2017 at 09:43 Richard Downer <ri...@apache.org> wrote:
> Hi Geoff,
>
> Unless the situation has moved on while I've not been paying attention, the
> integration tests have always been a mixed bag, with several failures some
> of which are nondeterministic[1], so I wouldn't worry too much about those.
>
> I'd suggest you subscribe to the "builds@apache.org" list which is for
> discussion about the Jenkins build machines. If you're going to be working
> with Jenkins for a while it's worth subscribing so you will be aware of
> outages and changes. Archived at
> https://lists.apache.org/list.html?builds@apache.org
>
> Richard.
>
>
> [1] or at least deterministic under a set of characteristics that we don't
> understand...
>
>
> On 8 March 2017 at 17:36, Geoff Macartney <
> geoff.macartney@cloudsoftcorp.com
> > wrote:
>
> > An update on the above topic.
> >
> > I have updated (or not, as noted) the following builds to Java 8, giving
> > the results shown as compared against the status before I made the
> update,
> > where "ok" means successful build, "-" is disabled, "x" is failing, and
> > "unstable" is, er, unstable (yellow).
> >
> > Most builds look ok, the two of concern are brooklyn-dist-master and
> > brooklyn-master-build. Also the brooklyn-integration-tests had 28 test
> > failures rather than the previous 20, but I don't know how consistent the
> > number of failures are from run to run, will investigate further.
> >
> > For brooklyn-dist-master what seems to be happening is that the java
> build
> > of all modules succeeds but there are errors in the archiving stage, or
> the
> > job times out. (I do note that some runs get scheduled on slaves that
> > appear from the "System Information" tab to not have Java 8 on them, but
> > will need to look into that some more).
> >
> > For brooklyn-master-build again I've got timeouts.
> >
> > I shall continue investigating these tomorrow. Please be patient until
> we
> > get this sorted out. (And any advice is welcome!)
> >
> > regards
> > Geoff
> >
> > before after updated to 8? Name
> >
> > ok ok updated brooklyn-client-master
> > ok ok updated
> > brooklyn-client-pull-requests
> > ok x updated brooklyn-dist-master
> > ok ok updated
> brooklyn-dist-pull-requests
> > unstable unstable updated brooklyn-integration-tests
> > ok ok updated brooklyn-library-master
> > x ok updated
> > brooklyn-library-pull-requests
> > x rebuilding brooklyn-master-build
> > - - updated
> brooklyn-master-integration
> > x x updated
> > brooklyn-master-windows; same failure as before so looks ok
> > ok ok updated brooklyn-server-master
> > x ok updated
> > brooklyn-server-pull-requests
> > ok ok updated brooklyn-ui-master
> > ok ok updated brooklyn-ui-pull-requests
> > - not updated incubator-brooklyn-master-
> > build
> > - not updated
> > incubator-brooklyn-master-integration
> > - not updated incubator-brooklyn-master-
> > windows
> > - not updated incubator-brooklyn-pull-
> > requests
> >
> >
> >
> >
> >
> >
> >
> > On Tue, 7 Mar 2017 at 13:44 Geoff Macartney <
> > geoff.macartney@cloudsoftcorp.com> wrote:
> >
> > > hello all,
> > >
> > > In the mail thread "[PROPOSAL] Remove java 7 support" [1] it has been
> > > proposed to "1. Update our jenkins etc to always build/run with Java
> 8."
> > >
> > > I intend to start changing the build configurations, and I'm going to
> > > propose doing so from tomorrow (Wednesday) at 10.00 UTC.
> > >
> > > I'm hoping that normal service should continue uninterrupted, but
> please
> > > let me know if you want me to hold off doing this, and when would be
> > > preferable.
> > >
> > > kind regards
> > > Geoff
> > >
> > > [1]
> > > https://lists.apache.org/thread.html/196c758afed8091ffefa8f3bdd4792
> > fae6a29fa1cf6f0dd86e20f821@%3Cdev.brooklyn.apache.org%3E
> > >
> >
>
Re: [NOTICE] switch to Java 8 as "official target" for Apache
Brooklyn Jenkins builds
Posted by Richard Downer <ri...@apache.org>.
Hi Geoff,
Unless the situation has moved on while I've not been paying attention, the
integration tests have always been a mixed bag, with several failures some
of which are nondeterministic[1], so I wouldn't worry too much about those.
I'd suggest you subscribe to the "builds@apache.org" list which is for
discussion about the Jenkins build machines. If you're going to be working
with Jenkins for a while it's worth subscribing so you will be aware of
outages and changes. Archived at
https://lists.apache.org/list.html?builds@apache.org
Richard.
[1] or at least deterministic under a set of characteristics that we don't
understand...
On 8 March 2017 at 17:36, Geoff Macartney <geoff.macartney@cloudsoftcorp.com
> wrote:
> An update on the above topic.
>
> I have updated (or not, as noted) the following builds to Java 8, giving
> the results shown as compared against the status before I made the update,
> where "ok" means successful build, "-" is disabled, "x" is failing, and
> "unstable" is, er, unstable (yellow).
>
> Most builds look ok, the two of concern are brooklyn-dist-master and
> brooklyn-master-build. Also the brooklyn-integration-tests had 28 test
> failures rather than the previous 20, but I don't know how consistent the
> number of failures are from run to run, will investigate further.
>
> For brooklyn-dist-master what seems to be happening is that the java build
> of all modules succeeds but there are errors in the archiving stage, or the
> job times out. (I do note that some runs get scheduled on slaves that
> appear from the "System Information" tab to not have Java 8 on them, but
> will need to look into that some more).
>
> For brooklyn-master-build again I've got timeouts.
>
> I shall continue investigating these tomorrow. Please be patient until we
> get this sorted out. (And any advice is welcome!)
>
> regards
> Geoff
>
> before after updated to 8? Name
>
> ok ok updated brooklyn-client-master
> ok ok updated
> brooklyn-client-pull-requests
> ok x updated brooklyn-dist-master
> ok ok updated brooklyn-dist-pull-requests
> unstable unstable updated brooklyn-integration-tests
> ok ok updated brooklyn-library-master
> x ok updated
> brooklyn-library-pull-requests
> x rebuilding brooklyn-master-build
> - - updated brooklyn-master-integration
> x x updated
> brooklyn-master-windows; same failure as before so looks ok
> ok ok updated brooklyn-server-master
> x ok updated
> brooklyn-server-pull-requests
> ok ok updated brooklyn-ui-master
> ok ok updated brooklyn-ui-pull-requests
> - not updated incubator-brooklyn-master-
> build
> - not updated
> incubator-brooklyn-master-integration
> - not updated incubator-brooklyn-master-
> windows
> - not updated incubator-brooklyn-pull-
> requests
>
>
>
>
>
>
>
> On Tue, 7 Mar 2017 at 13:44 Geoff Macartney <
> geoff.macartney@cloudsoftcorp.com> wrote:
>
> > hello all,
> >
> > In the mail thread "[PROPOSAL] Remove java 7 support" [1] it has been
> > proposed to "1. Update our jenkins etc to always build/run with Java 8."
> >
> > I intend to start changing the build configurations, and I'm going to
> > propose doing so from tomorrow (Wednesday) at 10.00 UTC.
> >
> > I'm hoping that normal service should continue uninterrupted, but please
> > let me know if you want me to hold off doing this, and when would be
> > preferable.
> >
> > kind regards
> > Geoff
> >
> > [1]
> > https://lists.apache.org/thread.html/196c758afed8091ffefa8f3bdd4792
> fae6a29fa1cf6f0dd86e20f821@%3Cdev.brooklyn.apache.org%3E
> >
>
Re: [NOTICE] switch to Java 8 as "official target" for Apache
Brooklyn Jenkins builds
Posted by Geoff Macartney <ge...@cloudsoftcorp.com>.
An update on the above topic.
I have updated (or not, as noted) the following builds to Java 8, giving
the results shown as compared against the status before I made the update,
where "ok" means successful build, "-" is disabled, "x" is failing, and
"unstable" is, er, unstable (yellow).
Most builds look ok, the two of concern are brooklyn-dist-master and
brooklyn-master-build. Also the brooklyn-integration-tests had 28 test
failures rather than the previous 20, but I don't know how consistent the
number of failures are from run to run, will investigate further.
For brooklyn-dist-master what seems to be happening is that the java build
of all modules succeeds but there are errors in the archiving stage, or the
job times out. (I do note that some runs get scheduled on slaves that
appear from the "System Information" tab to not have Java 8 on them, but
will need to look into that some more).
For brooklyn-master-build again I've got timeouts.
I shall continue investigating these tomorrow. Please be patient until we
get this sorted out. (And any advice is welcome!)
regards
Geoff
before after updated to 8? Name
ok ok updated brooklyn-client-master
ok ok updated brooklyn-client-pull-requests
ok x updated brooklyn-dist-master
ok ok updated brooklyn-dist-pull-requests
unstable unstable updated brooklyn-integration-tests
ok ok updated brooklyn-library-master
x ok updated brooklyn-library-pull-requests
x rebuilding brooklyn-master-build
- - updated brooklyn-master-integration
x x updated
brooklyn-master-windows; same failure as before so looks ok
ok ok updated brooklyn-server-master
x ok updated brooklyn-server-pull-requests
ok ok updated brooklyn-ui-master
ok ok updated brooklyn-ui-pull-requests
- not updated incubator-brooklyn-master-build
- not updated
incubator-brooklyn-master-integration
- not updated incubator-brooklyn-master-windows
- not updated incubator-brooklyn-pull-requests
On Tue, 7 Mar 2017 at 13:44 Geoff Macartney <
geoff.macartney@cloudsoftcorp.com> wrote:
> hello all,
>
> In the mail thread "[PROPOSAL] Remove java 7 support" [1] it has been
> proposed to "1. Update our jenkins etc to always build/run with Java 8."
>
> I intend to start changing the build configurations, and I'm going to
> propose doing so from tomorrow (Wednesday) at 10.00 UTC.
>
> I'm hoping that normal service should continue uninterrupted, but please
> let me know if you want me to hold off doing this, and when would be
> preferable.
>
> kind regards
> Geoff
>
> [1]
> https://lists.apache.org/thread.html/196c758afed8091ffefa8f3bdd4792fae6a29fa1cf6f0dd86e20f821@%3Cdev.brooklyn.apache.org%3E
>