|
Re: controller-csit-1node-akka1-all-{silicon,phosphorus} broken
Luis Gomez
Sure, will do.
toggle quoted messageShow quoted text
On Jul 13, 2021, at 8:11 AM, Robert Varga <nite@...> wrote:
|
|
|
|
controller-csit-1node-akka1-all-{silicon,phosphorus} broken
Robert Varga
Hello Luis, everyone,
patch https://git.opendaylight.org/gerrit/c/integration/distribution/+/95655 (Change Silicon version to 14.0.0) broke both these jobs: https://jenkins.opendaylight.org/releng/job/controller-csit-1node-akka1-all-silicon/ https://jenkins.opendaylight.org/releng/job/controller-csit-1node-akka1-all-phosphorus/ because it broke the logic here: https://github.com/opendaylight/integration-test/blob/master/csit/libraries/NexusKeywords.robot#L319-L327 i.e. it now fails with: Evaluating expression '14.0.0 > 14.0 and 14.0.0 < 15.0' failed: SyntaxError: invalid syntax (<string>, line 1)I have no idea how to fix this, can you please take a look? Thanks, Robert
|
|
|
|
Re: [release] [OpenDaylight TSC] Decommision SonarQube service (sonar.opendaylight.org)
Anil Belur
Hello Robert: Please confirm if you had a chance to test the sonarcube backup provided earlier. It's been a while sonar cube service has been idle and needs to be decommissioned ASAP, since we have migrated to sonarcloud.io. LF would be able to keep the sonarcube service running for another week until 30/June/2021 after which the service would be decommissioned. I would like to get your confirmation beforehand. Please let me know if we can proceed with removing the service. Cheers, Anil
On Wed, Apr 28, 2021 at 6:15 PM Robert Varga <nite@...> wrote: On 28/04/2021 01:27, Anil Belur wrote:
|
|
|
|
Re: [opendaylight-dev][release] OpenDaylight - Aluminium SR4 release status
Noted with thanks. We just need to update stable/aluminium downloads section and we will be good to go. Thank you all
On Mon, Jun 21, 2021 at 6:37 PM Luis Gomez <ecelgp@...> wrote:
|
|
|
|
Re: [opendaylight-dev][release] OpenDaylight - Aluminium SR4 release status
Luis Gomez
FYI Aluminium SR4 distro is available here: BR/Luis
|
|
|
|
Re: [opendaylight-dev][release] OpenDaylight - Aluminium SR4 release status
Thank you. @Luis Gomez I think we are ready to move forward with Aluminium SR4 official distribution
On Fri, Jun 18, 2021 at 6:02 AM <guillaume.lambert@...> wrote:
|
|
|
|
Re: [opendaylight-dev][release] OpenDaylight - Aluminium SR4 release status
Guillaume Lambert
Hello
Thanks for having unlocked the branch. I took care of merging the pending changes and of staging TPCE. Bala just managed to merge the release (2.4.0).
I think everything is fine. Please let us know if you see any problem.
Best Regards Guillaume
De : Daniel de la Rosa [mailto:ddelarosa0707@...]
@Anil Belur please unlock Aluminium branch ASAP, so we can move forward with releasing SM projects/Transport PCE
Thanks & Regards
On Mon, Jun 14, 2021 at 1:28 AM <guillaume.lambert@...> wrote:
_________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.
|
|
|
|
Re: [opendaylight-dev][release] OpenDaylight - Aluminium SR4 release status
@Anil Belur please unlock Aluminium branch ASAP, so we can move forward with releasing SM projects/Transport PCE Thanks & Regards
On Mon, Jun 14, 2021 at 1:28 AM <guillaume.lambert@...> wrote:
|
|
|
|
Re: Triggering rtd-merge job after release-merge?
Guillaume Lambert
Hello
+docs ML
I’ve noticed too the issue pointed by Robert. Because of inter-sphinx cross-references, this sometimes prevents the docs project from building fine, when old subprojects versions are removed because objects.inv configured in docs/conf.py can become suddently unavailable.
So automating the whole process would definitely make sense in my opinion, at least when distributions are created from integration/distribution. To my knowledge, only the account “odl-rtd” have the admins rights on all OpenDaylight subprojects in RTD. And I cannot see how this can be automated.
Hope this helps Guillaume
De : Anil Belur [mailto:abelur@...]
Greetings Robert:
I checked the JJB code for the controller rtd-merge-master, the Gerrit triggers seem to work as expected triggering the required jobs. Ex: Job #4 was triggered from a merge from the change request 94725. From what I understand, the release merge job are responsible for promoting the staging repo, which should create a new version ex: 3.0.6 in RTD.org/$project. Every new release on the self-managed projects would require activating the new version on RTD (as admin). That should trigger a new build to update the docs for the $project.
I am not sure if triggering rtd-merge as a downstream job on every release merge would be the right way for this. Will need to dig in a bit and get back to you.
+docs folks on any suggestions.
Cheers, Anil
On Wed, Jun 9, 2021 at 7:27 PM Robert Varga <nite@...> wrote:
_________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.
|
|
|
|
Re: [opendaylight-dev][release] OpenDaylight - Silicon SR1 release status
Guillaume Lambert
Hello
This is now fixed and the change is merged https://git.opendaylight.org/gerrit/c/docs/+/96421
The document was not referenced in any toctree , what generated a warning… … and warnings are now treated as errors.
Once this particular problem fixed, there were also some connectivity issues to IETF RFC links in Jenkins minions. Since this is very recurrent, I simply properly ignored these URLs as it is already done in the master branch. By the way I reintroduced the check to the OpenDaylight Silicon official web page, that is now published and reachable.
I’ve added also transportPCE release notes but I’ prefer to have a NACR on it. So I am waiting for Gilles or anyone else to check them before merging that. https://git.opendaylight.org/gerrit/c/docs/+/96521
To ease further failures analysis, I will reduce Sphinx logs verbosity as it is already done in the master branch. https://git.opendaylight.org/gerrit/c/docs/+/96526.
Hope this helps
BR Guillaume
De : Anil Belur [mailto:abelur@...]
The release notes are ready. However, the verify job is not going through.
On Thu, Jun 10, 2021 at 3:22 PM Daniel de la Rosa <ddelarosa0707@...> wrote:
_________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.
|
|
|
|
Re: [opendaylight-dev][release] OpenDaylight - Aluminium SR4 release status
Guillaume Lambert
Hello
As noticed by Christophe, it seems that transportpce stable/aluminium branch is still locked this morning. We can not perform the latest actions required such as merging odlparent and mdsal version bumps until the branch is unlocked or that someone merges the relation chain pushed by Christophe.
Best Regards Guillaume
De : Daniel de la Rosa [mailto:ddelarosa0707@...]
Thanks Anil. Guillaume, please let us when TransportPCE plans to release in Aluminium SR4
Daniel de la Rosa ODL Release Manager
On Tue, Jun 8, 2021 at 2:50 PM Anil Belur <abelur@...> wrote:
_________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.
|
|
|
|
Re: [opendaylight-dev][release] OpenDaylight - Silicon SR1 release status
Anil Belur
The release notes are ready. However, the verify job is not going through.
On Thu, Jun 10, 2021 at 3:22 PM Daniel de la Rosa <ddelarosa0707@...> wrote:
|
|
|
|
Re: [opendaylight-dev][release] OpenDaylight - Aluminium SR4 release status
Thanks Anil. Guillaume, please let us when TransportPCE plans to release in Aluminium SR4 Daniel de la Rosa ODL Release Manager
On Tue, Jun 8, 2021 at 2:50 PM Anil Belur <abelur@...> wrote:
|
|
|
|
Re: [opendaylight-dev][release] OpenDaylight - Silicon SR1 release status
Thanks Luis. Anil, I believe the release notes are ready and we just have to update the downloads page after that. Daniel de la Rosa ODL Release Manager
On Tue, Jun 8, 2021 at 10:52 PM Luis Gomez <ecelgp@...> wrote:
|
|
|
|
Re: Triggering rtd-merge job after release-merge?
Anil Belur
Greetings Robert: I checked the JJB code for the controller rtd-merge-master, the Gerrit triggers seem to work as expected triggering the required jobs. Ex: Job #4 was triggered from a merge from the change request 94725. From what I understand, the release merge job are responsible for promoting the staging repo, which should create a new version ex: 3.0.6 in RTD.org/$project. Every new release on the self-managed projects would require activating the new version on RTD (as admin). That should trigger a new build to update the docs for the $project. I am not sure if triggering rtd-merge as a downstream job on every release merge would be the right way for this. Will need to dig in a bit and get back to you. +docs folks on any suggestions. Cheers, Anil
On Wed, Jun 9, 2021 at 7:27 PM Robert Varga <nite@...> wrote: Hello,
|
|
|
|
Triggering rtd-merge job after release-merge?
Robert Varga
Hello,
while resolving docs.opendaylight.org links to MRI projects, I have come across a slight problem with having versions propagated. Since MRI projects produce versions rather more often than their documentation changes the admin interface does not see the new versions, for example in https://readthedocs.org/projects/odl-controller/versions/. The list of versions is updated by $project-rtd-merge jobs, hence for MRI projects (for example controller), I need to trigger https://jenkins.opendaylight.org/releng/view/controller/job/controller-rtd-merge-master/ whenever https://jenkins.opendaylight.org/releng/view/controller/job/controller-release-merge/ succeeds. The idea is that controller-release-merge produces the version tag in git repo, and controller-rtd-merge-master then picks it up and lets ReadTheDocs know about it. Is there a way to create this trigger in releng/builder's JJB? Thanks, Robert
|
|
|
|
Re: [opendaylight-dev][release] OpenDaylight - Silicon SR1 release status
Luis Gomez
OK, here is the distribution release:
toggle quoted messageShow quoted text
We can proceed with the post-release actions. BR/Luis
|
|
|
|
[opendaylight-dev][release] OpenDaylight - Aluminium SR4 release status
Anil Belur
Hello All, OpenDaylight Aluminium SR4 version bump is complete and the staging repository is been promoted. The 'stable/aluminum' branch is locked and ready for development. Pending activities that need to be completed for the release: 1. Self-managed projects release of Aluminum SR4. 2. Release Distribution once the 1. is complete. 3. Release notes - to be merged CR [1.] 4. Update ODL downloads page [1.]. Thanks to everyone who contributed to the release. Regards, Anil Belur [0.] https://docs.opendaylight.org/en/latest/downloads.html [1.] https://git.opendaylight.org/gerrit/c/docs/+/96491
|
|
|
|
Re: [opendaylight-dev][release] OpenDaylight - Silicon SR1 release status
Thank you Gilles. Luis, I think we can proceed with the official distribution of Silicon SR1
On Fri, Jun 4, 2021 at 2:54 AM <gilles.thouenon@...> wrote:
|
|
|
|
Re: [opendaylight-dev][release] OpenDaylight - Silicon SR1 release status
Gilles Thouenon
Hello,
I’ve released the TransportPCE artifacts in version 3.1.0 for Silicon SR1 (see https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/transportpce-release-merge/18/). Everything looks ok. However, let me know if you see anything wrong.
Best Regards,
Gilles Thouenon
De : integration-dev@... [mailto:integration-dev@...]
De la part de Anil Belur
Hello All, _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.
|
|
|