Date
1 - 8 of 8
[release] Oxygen jobs Status
Anil Belur
Hello everyone,
Last we were waiting on version bumps and in the middle of backporting some changes to Oxygen release. Can we know what is the status of this and if we are good to clean up all the Oxygen jobs from releng/builder moving forward? Also may help with saving some resource on the infra. ;-)
Thanks,
Anil
Robert Varga
On 17/01/2019 23:24, Anil Belur wrote:
patches are out there. yangtools-2.1.6.7 to go with that is also out and
I am preparing patches (should be a couple more minutes).
I will start merging them as soon as they verify.
Regards,
Robert
Hello everyone,Hello Anil,
Last we were waiting on version bumps and in the middle of backportingIt took a bit longer than expected, but odlparent-3.1.6 is out and the
some changes to Oxygen release. Can we know what is the status of this
and if we are good to clean up all the Oxygen jobs from releng/builder
moving forward? Also may help with saving some resource on the infra. ;-)
patches are out there. yangtools-2.1.6.7 to go with that is also out and
I am preparing patches (should be a couple more minutes).
I will start merging them as soon as they verify.
Regards,
Robert
Robert Varga
On 17/01/2019 23:24, Anil Belur wrote:
Oxygen branch is stable as of now in that it successfully underwent
merge jobs for all projects and resulted in a fresh distribution in
nexus. My work here is done :)
I would suggest spinning one more autorelease build and once we have a
successful build freeze the branches and deactivating all jobs.
Once Neon is out and our security support period for Oxygen is over, we
can delete the jobs.
Regards,
Robert
Hello everyone,Hello,
Last we were waiting on version bumps and in the middle of backporting
some changes to Oxygen release. Can we know what is the status of this
and if we are good to clean up all the Oxygen jobs from releng/builder
moving forward? Also may help with saving some resource on the infra. ;-)
Oxygen branch is stable as of now in that it successfully underwent
merge jobs for all projects and resulted in a fresh distribution in
nexus. My work here is done :)
I would suggest spinning one more autorelease build and once we have a
successful build freeze the branches and deactivating all jobs.
Once Neon is out and our security support period for Oxygen is over, we
can delete the jobs.
Regards,
Robert
Robert Varga
On 19/01/2019 19:49, Robert Varga wrote:
Regards,
Robert
Oxygen branch is stable as of now in that it successfully underwentAh, by the way, the new distribution is 14.8MiB (~4.2%) smaller than SR4.
merge jobs for all projects and resulted in a fresh distribution in
nexus. My work here is done :)
Regards,
Robert
Anil Belur
On Sun, Jan 20, 2019 at 4:49 AM Robert Varga <nite@...> wrote:
On 17/01/2019 23:24, Anil Belur wrote:
> Hello everyone,
>
> Last we were waiting on version bumps and in the middle of backporting
> some changes to Oxygen release. Can we know what is the status of this
> and if we are good to clean up all the Oxygen jobs from releng/builder
> moving forward? Also may help with saving some resource on the infra. ;-)
Hello,
Oxygen branch is stable as of now in that it successfully underwent
merge jobs for all projects and resulted in a fresh distribution in
nexus. My work here is done :)
I would suggest spinning one more autorelease build and once we have a
successful build freeze the branches and deactivating all jobs.
Once Neon is out and our security support period for Oxygen is over, we
can delete the jobs.
Excellent, I've triggered job AR Oxygen #556, and hopefully once this goes through we can merge the CR.
Thanks,
Anil
Abhijit Kumbhare
Great. Thanks Robert & Anil.
On Sat, Jan 19, 2019 at 1:29 PM Anil Belur <abelur@...> wrote:
_______________________________________________On Sun, Jan 20, 2019 at 4:49 AM Robert Varga <nite@...> wrote:On 17/01/2019 23:24, Anil Belur wrote:
> Hello everyone,
>
> Last we were waiting on version bumps and in the middle of backporting
> some changes to Oxygen release. Can we know what is the status of this
> and if we are good to clean up all the Oxygen jobs from releng/builder
> moving forward? Also may help with saving some resource on the infra. ;-)
Hello,
Oxygen branch is stable as of now in that it successfully underwent
merge jobs for all projects and resulted in a fresh distribution in
nexus. My work here is done :)
I would suggest spinning one more autorelease build and once we have a
successful build freeze the branches and deactivating all jobs.
Once Neon is out and our security support period for Oxygen is over, we
can delete the jobs.
Excellent, I've triggered job AR Oxygen #556, and hopefully once this goes through we can merge the CR.Thanks,Anil
integration-dev mailing list
integration-dev@...
https://lists.opendaylight.org/mailman/listinfo/integration-dev
Anil Belur
AR Oxygen #556 has passed sucessfully.
On Sun, Jan 20, 2019 at 7:28 AM Anil Belur <abelur@...> wrote:
On Sun, Jan 20, 2019 at 4:49 AM Robert Varga <nite@...> wrote:On 17/01/2019 23:24, Anil Belur wrote:
> Hello everyone,
>
> Last we were waiting on version bumps and in the middle of backporting
> some changes to Oxygen release. Can we know what is the status of this
> and if we are good to clean up all the Oxygen jobs from releng/builder
> moving forward? Also may help with saving some resource on the infra. ;-)
Hello,
Oxygen branch is stable as of now in that it successfully underwent
merge jobs for all projects and resulted in a fresh distribution in
nexus. My work here is done :)
I would suggest spinning one more autorelease build and once we have a
successful build freeze the branches and deactivating all jobs.
Once Neon is out and our security support period for Oxygen is over, we
can delete the jobs.
Excellent, I've triggered job AR Oxygen #556, and hopefully once this goes through we can merge the CR.Thanks,Anil
Anil Belur
On Sun, Jan 20, 2019 at 4:49 AM Robert Varga <nite@...> wrote:
On 17/01/2019 23:24, Anil Belur wrote:
> Hello everyone,
>
> Last we were waiting on version bumps and in the middle of backporting
> some changes to Oxygen release. Can we know what is the status of this
> and if we are good to clean up all the Oxygen jobs from releng/builder
> moving forward? Also may help with saving some resource on the infra. ;-)
Hello,
Oxygen branch is stable as of now in that it successfully underwent
merge jobs for all projects and resulted in a fresh distribution in
nexus. My work here is done :)
I would suggest spinning one more autorelease build and once we have a
successful build freeze the branches and deactivating all jobs.
Once Neon is out and our security support period for Oxygen is over, we
can delete the jobs.
As discssed, we have disabled all Oxygen jobs on Jenkins/releng, to make sure we are not running those jobs on the Infra. Also going forward we can remove all these jobs after the support period is completed. A minor caveat here JJB-{verify,merge} jobs would continue to run 33% longer than required (with these stable jobs in the code not being removed).
https://jenkins.opendaylight.org/releng/view/Oxygen/
Thanks,
Anil