Re: [opnfv-tech-discuss] [opnfvdocs] About docs CI jobs

2017-03-14 Thread Julien 
Hi Sofia,

"number of executors" can be increased in Jenkins master. If it is
required, we can seek help from Aric.

Thanks,
Julien

Sofia Wallin 于2017年3月14日周二 下午6:46写道：

> Hi Julien,
>
> We currently have 2 jobs running since we are migrating all documentation
> to readthedocs, opnfv-docs-verify-master will be disable by the end of
> Danube release cycle.
>
> Today we are forcing the builds to run on particular machines (lf-build1
> or lf-build2) since these support submodules. I don’t know if it’s
> possible to increase the number of executors, if this could be an easy
> solution.
>
>
>
> I happily welcome all feedback and potential improvements for the E
> release.
>
>
>
> Regards,
>
> Sofia
>
>
>
> *From:* Julien [mailto:julien...@gmail.com]
> *Sent:* den 10 mars 2017 10:30
> *To:* Sofia Wallin ; TECH-DISCUSS OPNFV (
> opnfv-tech-discuss@lists.opnfv.org) ;
> Fatih Degirmenci 
> *Subject:* [opnfvdocs] About docs CI jobs
>
>
>
> Hi Sofia,
>
>
>
> Currently there are two verify docs jobs in OPNFV:
>
> 1. opnfv-docs-verify-master
>
> 2. docs-verify-rtd-master
>
>
>
>
>
> The first job existed earlier before the *opnfvdocs* project created, and
> they works for the same purpose. Shall we merge them two?
>
>
>
> The other issues existed :
>
> 1. The job 'docs-verify-rtd-master' uses submodule to fetch all the OPNFV
> projects' docs triggered by any project, which makes the projects affected
> by each other. Any issue in one project will affect others. It is not
> necessary. This will also make the building process occupy more time. The
> jobs 'opnfv-docs-verify-master' does well.
>
> 2. opnfv-docs-verify-master does not output the building result to the
> artifactory, so we can not check the results.
>
> 3. the jobs of opnfvdoc fixed the Jenkins slave's label with lf-build1 or
> lf-build2 .  Currently, the resources in lf-build are in short and the many
> jobs are in the queue. Shall we set it to opnfv-build to all the jobs.
>
> 4. There are lots of warnings in logs of Job 'docs-verify-rtd-master'.
>
>
>
> In next release I hope I can introduce sphinx docker to faster current
> verify job.
>
>
>
> Best Regards,
>
> Julien
>
>
>
>
>
>
>
>
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [opnfvdocs] About docs CI jobs

2017-03-14 Thread Sofia Wallin 
Hi Julien,
We currently have 2 jobs running since we are migrating all documentation to 
readthedocs, opnfv-docs-verify-master will be disable by the end of Danube 
release cycle.
Today we are forcing the builds to run on particular machines (lf-build1 or 
lf-build2) since these support submodules. I don’t know if it’s possible to 
increase the number of executors, if this could be an easy solution.

I happily welcome all feedback and potential improvements for the E release.

Regards,
Sofia

From: Julien [mailto:julien...@gmail.com]
Sent: den 10 mars 2017 10:30
To: Sofia Wallin ; TECH-DISCUSS OPNFV 
(opnfv-tech-discuss@lists.opnfv.org) ; 
Fatih Degirmenci 
Subject: [opnfvdocs] About docs CI jobs

Hi Sofia,

Currently there are two verify docs jobs in OPNFV:
1. opnfv-docs-verify-master
2. docs-verify-rtd-master


The first job existed earlier before the *opnfvdocs* project created, and they 
works for the same purpose. Shall we merge them two?

The other issues existed :
1. The job 'docs-verify-rtd-master' uses submodule to fetch all the OPNFV 
projects' docs triggered by any project, which makes the projects affected by 
each other. Any issue in one project will affect others. It is not necessary. 
This will also make the building process occupy more time. The jobs 
'opnfv-docs-verify-master' does well.
2. opnfv-docs-verify-master does not output the building result to the 
artifactory, so we can not check the results.
3. the jobs of opnfvdoc fixed the Jenkins slave's label with lf-build1 or 
lf-build2 .  Currently, the resources in lf-build are in short and the many 
jobs are in the queue. Shall we set it to opnfv-build to all the jobs.
4. There are lots of warnings in logs of Job 'docs-verify-rtd-master'.

In next release I hope I can introduce sphinx docker to faster current verify 
job.

Best Regards,
Julien



___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [opnfvdocs] About docs CI jobs

2017-03-10 Thread Julien 
Hi Sofia,

Currently there are two verify docs jobs in OPNFV:
1. opnfv-docs-verify-master
2. docs-verify-rtd-master


The first job existed earlier before the *opnfvdocs* project created, and
they works for the same purpose. Shall we merge them two?

The other issues existed :
1. The job 'docs-verify-rtd-master' uses submodule to fetch all the OPNFV
projects' docs triggered by any project, which makes the projects affected
by each other. Any issue in one project will affect others. It is not
necessary. This will also make the building process occupy more time. The
jobs 'opnfv-docs-verify-master' does well.
2. opnfv-docs-verify-master does not output the building result to the
artifactory, so we can not check the results.
3. the jobs of opnfvdoc fixed the Jenkins slave's label with lf-build1 or
lf-build2 .  Currently, the resources in lf-build are in short and the many
jobs are in the queue. Shall we set it to opnfv-build to all the jobs.
4. There are lots of warnings in logs of Job 'docs-verify-rtd-master'.

In next release I hope I can introduce sphinx docker to faster current
verify job.

Best Regards,
Julien



>
>
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss