[documentation] RTD Job - automation rule to activate branch/tag


Luis Gomez
 

Hi Anil,

Is there anyone in ODL with admin permissions on all the RTD projects? If so, can this person generate a token and run this script to activate the stable-phosphorus branch on all the projects:


I only have admin rights on distribution and I do not think at this moment we can afford to wait for all the project maintainers to do this individually.

Additionally, this admin person can add the rule you suggest to all the projects so that we do not need to run the script in future.

Once this is done, we can unblock this gerrit:


BR/Luis


On Jan 12, 2022, at 3:53 PM, Anil Belur <abelur@...> wrote:

Hi all,

As discussed on the LFN Dev and testing forums, some of the RTD branches were not activated by default therefore the docs were not getting created. This can be solved by using Automation rules. 

For instance, I have created automation rules for Netconf project for activating
all tags/branch matching this regex: "^[vV]"

Custom match: ^[vV]
Version type: Tag
Action: Activate version

Custom match: ^[vV]
Version type: Branch
Action: Activate version


I've created the activation rules for Netconf branch hopefully, this should work.

Regards,
Anil Belur





Anil Belur
 

Greetings Luis:

I've run the script to activate all the projects. Please check and let me know if all the versions are active. 

Regards,
Anil


On Sun, Jan 23, 2022 at 4:39 AM Luis Gomez <ecelgp@...> wrote:
Hi Anil,

Is there anyone in ODL with admin permissions on all the RTD projects? If so, can this person generate a token and run this script to activate the stable-phosphorus branch on all the projects:


I only have admin rights on distribution and I do not think at this moment we can afford to wait for all the project maintainers to do this individually.

Additionally, this admin person can add the rule you suggest to all the projects so that we do not need to run the script in future.

Once this is done, we can unblock this gerrit:


BR/Luis


On Jan 12, 2022, at 3:53 PM, Anil Belur <abelur@...> wrote:

Hi all,

As discussed on the LFN Dev and testing forums, some of the RTD branches were not activated by default therefore the docs were not getting created. This can be solved by using Automation rules. 

For instance, I have created automation rules for Netconf project for activating
all tags/branch matching this regex: "^[vV]"

Custom match: ^[vV]
Version type: Tag
Action: Activate version

Custom match: ^[vV]
Version type: Branch
Action: Activate version


I've created the activation rules for Netconf branch hopefully, this should work.

Regards,
Anil Belur





Luis Gomez
 

Yeah, I do not see daexim stable/phosphorus docs for example: https://docs.opendaylight.org/projects/daexim/en/latest/, so it did not work, at least fully :(

Can you please make sure at least these MSI projects get the stable/phosphorous branch activated:

    odl-daexim
    odl-jsonrpc
    odl-lispflowmapping
    odl-openflowplugin
    opendaylight-ovsdb
    odl-transportpce



On Jan 24, 2022, at 3:43 PM, Anil Shashikumar Belur <abelur@...> wrote:

Greetings Luis:

I've run the script to activate all the projects. Please check and let me know if all the versions are active. 

Regards,
Anil


On Sun, Jan 23, 2022 at 4:39 AM Luis Gomez <ecelgp@...> wrote:
Hi Anil,

Is there anyone in ODL with admin permissions on all the RTD projects? If so, can this person generate a token and run this script to activate the stable-phosphorus branch on all the projects:


I only have admin rights on distribution and I do not think at this moment we can afford to wait for all the project maintainers to do this individually.

Additionally, this admin person can add the rule you suggest to all the projects so that we do not need to run the script in future.

Once this is done, we can unblock this gerrit:


BR/Luis


On Jan 12, 2022, at 3:53 PM, Anil Belur <abelur@...> wrote:

Hi all,

As discussed on the LFN Dev and testing forums, some of the RTD branches were not activated by default therefore the docs were not getting created. This can be solved by using Automation rules. 

For instance, I have created automation rules for Netconf project for activating
all tags/branch matching this regex: "^[vV]"

Custom match: ^[vV]
Version type: Tag
Action: Activate version

Custom match: ^[vV]
Version type: Branch
Action: Activate version


I've created the activation rules for Netconf branch hopefully, this should work.

Regards,
Anil Belur






Anil Belur
 

Hi Luis: odl-daexim is already activated for the stable/phosphorus branch and rest of the projects listed are already activated with the script was run.
Let me know if you are still unable to see that.
 


Luis Gomez
 

Looks like jsonrpc is missing phosphorus brach too: https://docs.opendaylight.org/projects/jsonrpc/en/latest/

On Feb 1, 2022, at 4:31 PM, Anil Shashikumar Belur <abelur@linuxfoundation.org> wrote:

Hi Luis: odl-daexim is already activated for the stable/phosphorus branch and rest of the projects listed are already activated with the script was run.
Let me know if you are still unable to see that.