Re: [VOTE] Release Apache Qpid JMS 0.53.0
On 7/24/20 12:37 PM, Robbie Gemmell wrote: Hi folks, I have put together a spin for a 0.53.0 Qpid JMS client release, please give it a test out and vote accordingly. The source and binary archives can be grabbed from: https://dist.apache.org/repos/dist/dev/qpid/jms/0.53.0-rc1/ The maven artifacts are also staged for now at: https://repository.apache.org/content/repositories/orgapacheqpid-1202 The JIRAs assigned are: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524&version=12348372 Regards, Robbie P.S. If you want to test it out using maven (e.g with the examples src, or your own things), you can temporarily add this to your poms to access the staging repo: staging https://repository.apache.org/content/repositories/orgapacheqpid-1202 The dependency for the client itself would then be: org.apache.qpid qpid-jms-client 0.53.0 - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org +1 * Validated signatures and checksums * Verified license and notice files in artifacts * Checked source for license headers using Apache Rat plugin * Built from source and ran the tests * Built ActiveMQ 5.x and Artemis master branches with staged artifacts and ran all AMQP tests. -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
Re: [VOTE] Release Apache Qpid JMS 0.53.0
On Fri, 24 Jul 2020 at 17:37, Robbie Gemmell wrote: > > Hi folks, > > I have put together a spin for a 0.53.0 Qpid JMS client release, > please give it a test out and vote accordingly. > > The source and binary archives can be grabbed from: > https://dist.apache.org/repos/dist/dev/qpid/jms/0.53.0-rc1/ > > The maven artifacts are also staged for now at: > https://repository.apache.org/content/repositories/orgapacheqpid-1202 > > The JIRAs assigned are: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524&version=12348372 > > Regards, > Robbie > > P.S. If you want to test it out using maven (e.g with the examples > src, or your own things), you can temporarily add this to your poms to > access the staging repo: > > > > staging > > https://repository.apache.org/content/repositories/orgapacheqpid-1202 > > > > The dependency for the client itself would then be: > > > org.apache.qpid > qpid-jms-client > 0.53.0 > +1 I checked things over as follows: - Verified the signature and checksum files. - Checked for LICENCE and NOTICE files in the archives. - Used "mvn apache-rat:check" to check licence headers in source archive. - Ran the source build and tests on JDK 8 and JDK 11. - Built Qpid Broker-J master with staged client, ran the systests. - Built ActiveMQ 5 + Artemis master with staged client, ran the AMQP tests. - Built the Quarkus extension for Qpid JMS using the staged bits and tested. - Ran the HelloWorld example against Qpid Dispatch 1.12.0. Robbie - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
[VOTE] Release Apache Qpid JMS 0.53.0
Hi folks, I have put together a spin for a 0.53.0 Qpid JMS client release, please give it a test out and vote accordingly. The source and binary archives can be grabbed from: https://dist.apache.org/repos/dist/dev/qpid/jms/0.53.0-rc1/ The maven artifacts are also staged for now at: https://repository.apache.org/content/repositories/orgapacheqpid-1202 The JIRAs assigned are: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524&version=12348372 Regards, Robbie P.S. If you want to test it out using maven (e.g with the examples src, or your own things), you can temporarily add this to your poms to access the staging repo: staging https://repository.apache.org/content/repositories/orgapacheqpid-1202 The dependency for the client itself would then be: org.apache.qpid qpid-jms-client 0.53.0 - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
Re: [NOTICE] Jenkins CI server change, manual job migrations required
On Fri, 24 Jul 2020 at 15:07, Jiri Daněk wrote: > > On Fri, Jul 24, 2020 at 2:39 PM Robbie Gemmell > wrote: > [...] > > > We must manually migrate any jobs we want to keep to the new system. > > > Are the job definitions in the new system under version control, or is > there expectation to manage jobs through the Web UI? > The job definitions are the same in both I believe, i.e you can make do things either way. Ours have mostly been done via the UI, which is how I am keeping the ones I migrate as they are trivial, simple to port quickly without learning the Jenkinsfile stuff right now, and the config is mostly all copied from one job to another during creation anyway (for me at least, on Maven jobs). Can always change it. > [...] > > > I asked for a Qpid folder and for all committers to have access to the > > jobs, where they will live under: > > https://ci-builds.apache.org/job/Qpid/ > > > > Our old jobs are at: https://builds.apache.org/view/M-R/view/Qpid/ > > > Are there any advantages to using the Apache infra, over Travis or AppVeyor > or GitHub Actions? So far I've managed to completely ignore the Apache > Jenkins, so I am wondering; am I missing something? Maybe some Cloudbees > proprietary plugins? > -- > Mit freundlichen Grüßen / Kind regards > Jiri Daněk It's just another env really. It was there before all the other options were available, and remains so. More envs is good, helps balance availability (Things go down), and latency (everyone flocks to the shiny new thing and overloads the shared capacity, making for queues), and provides more runs (better helps see when things break, ditto when things are fixed). It hasn't used Cloudbees before now. - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
Re: [NOTICE] Jenkins CI server change, manual job migrations required
On Fri, Jul 24, 2020 at 2:39 PM Robbie Gemmell wrote: [...] > We must manually migrate any jobs we want to keep to the new system. Are the job definitions in the new system under version control, or is there expectation to manage jobs through the Web UI? [...] > I asked for a Qpid folder and for all committers to have access to the > jobs, where they will live under: > https://ci-builds.apache.org/job/Qpid/ > > Our old jobs are at: https://builds.apache.org/view/M-R/view/Qpid/ Are there any advantages to using the Apache infra, over Travis or AppVeyor or GitHub Actions? So far I've managed to completely ignore the Apache Jenkins, so I am wondering; am I missing something? Maybe some Cloudbees proprietary plugins? -- Mit freundlichen Grüßen / Kind regards Jiri Daněk
Re: [NOTICE] Jenkins CI server change, manual job migrations required
Hi Roobie, Thanks for the update. I will try to migrate Qpid Broker-J jobs over next week-end. Kind Regards, Alex On Fri, 24 Jul 2020 at 13:30, Robbie Gemmell wrote: > The Jenkins setup at https://builds.apache.org is being replaced, > including a server migration to a new Cloudbees hosted Jenkins primary > at https://ci-builds.apache.org (both names will go there after the > old setup is turned off). > > We must manually migrate any jobs we want to keep to the new system. > > The old system is being switched off on August 15th, but with worker > nodes already gradually being migrated to the new setup now as > appropriate to balance demand from new migrated jobs. > > I asked for a Qpid folder and for all committers to have access to the > jobs, where they will live under: > https://ci-builds.apache.org/job/Qpid/ > > Our old jobs are at: https://builds.apache.org/view/M-R/view/Qpid/ > > I plan to migrate all the Qpid JMS and Proton-J jobs myself and I've > done a couple as a test. I don't plan on migrating most other jobs so > if you want to keep them then please migrate them. > > Full initial details are at [1], with more in other threads on > builds@a.o [2], such as the plugin installation request thread [3] for > any required plugins not yet installed (not sure we have any > requirements here though). > > Robbie > > [1] > https://lists.apache.org/thread.html/re974eed417a1bc294694701d5c91b4bf92689fcf32a4c91f169be87d%40%3Cbuilds.apache.org%3E > [2] https://lists.apache.org/list.html?bui...@apache.org > [3] > https://lists.apache.org/thread.html/r37c73263595b93c61c3d9b44e88a57f63edd28afa9aba3047259f4a4%40%3Cbuilds.apache.org%3E > > - > To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org > For additional commands, e-mail: users-h...@qpid.apache.org > >
[NOTICE] Jenkins CI server change, manual job migrations required
The Jenkins setup at https://builds.apache.org is being replaced, including a server migration to a new Cloudbees hosted Jenkins primary at https://ci-builds.apache.org (both names will go there after the old setup is turned off). We must manually migrate any jobs we want to keep to the new system. The old system is being switched off on August 15th, but with worker nodes already gradually being migrated to the new setup now as appropriate to balance demand from new migrated jobs. I asked for a Qpid folder and for all committers to have access to the jobs, where they will live under: https://ci-builds.apache.org/job/Qpid/ Our old jobs are at: https://builds.apache.org/view/M-R/view/Qpid/ I plan to migrate all the Qpid JMS and Proton-J jobs myself and I've done a couple as a test. I don't plan on migrating most other jobs so if you want to keep them then please migrate them. Full initial details are at [1], with more in other threads on builds@a.o [2], such as the plugin installation request thread [3] for any required plugins not yet installed (not sure we have any requirements here though). Robbie [1] https://lists.apache.org/thread.html/re974eed417a1bc294694701d5c91b4bf92689fcf32a4c91f169be87d%40%3Cbuilds.apache.org%3E [2] https://lists.apache.org/list.html?bui...@apache.org [3] https://lists.apache.org/thread.html/r37c73263595b93c61c3d9b44e88a57f63edd28afa9aba3047259f4a4%40%3Cbuilds.apache.org%3E - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
[RESULT][VOTE] Release Apache Qpid Proton-J 0.33.6
There were 4 binding +1 votes, and no other votes received. The vote has passed. I will add the files to the dist release repo and release the maven staging repo shortly. The website will be updated after the release has had time to sync to the mirrors and maven central. Robbie - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
