Hello,
Yup *-site.jar are in each maven-module/target.
So it looks to be a nice use case to add a new feature in jenkins :-)
: creating an archive which will contains all site datas.
Could you please load an issue in jenkins jira [1] ? I will take care of it.
Thanks,
--
Olivier Lamy
http://twitt
Hi Olivier
Thanks for the hint, but the problem seems to be that the produced jar
https://builds.apache.org/job/clerezza-site/ws/trunk-1.6/target/parent-0.2-incubating-SNAPSHOT-site.jar
only contains the site of the parent so we would have to retrieve the jar
for every module.
Cheers,
Reto
On
Hello,
You can try the maven goal site:jar ([1]).
With this option you will a jar with the complete site content.
Maybe will be more easy to wget only this one and unzip ?
HTH,
--
Olivier Lamy
http://twitter.com/olamy | http://www.linkedin.com/in/olamy
[1] http://maven.apache.org/plugins/maven-s
On Mon, Jun 20, 2011 at 8:58 PM, Reto Bachmann-Gmuer
wrote:
> would setting up a cron-job on people.a.o to wget -r
> https://builds.apache.org/job/clerezza-site/site/ be an acceptable
> solutions?
As a stop-gap solution, it's fine from the Jenkins point-of-view.
/niklas
thanks for your help.
would setting up a cron-job on people.a.o to wget -r
https://builds.apache.org/job/clerezza-site/site/ be an acceptable
solutions?
Reto
On Thu, Jun 16, 2011 at 9:46 PM, Olivier Lamy wrote:
> 2011/6/16 Niklas Gustavsson :
> > On Thu, Jun 16, 2011 at 5:34 PM, Olivier Lamy
2011/6/16 Niklas Gustavsson :
> On Thu, Jun 16, 2011 at 5:34 PM, Olivier Lamy wrote:
>> If you use the maven native jenkins plugin, the maven plugin site is
>> intercepted and your job should have a link (with the label
>> "Maven-generated site" ) to the generated site during the build (the
>> sit
On Thu, Jun 16, 2011 at 5:08 PM, Reto Bachmann-Gmuer
wrote:
> I'm irritated that they are considered save enough for having credentials to
> deploy to the maven artifact repository but not to the website server.
I wasn't the one who set this up, so I can only speculate on the
reasoning. First of
On Thu, Jun 16, 2011 at 5:34 PM, Olivier Lamy wrote:
> If you use the maven native jenkins plugin, the maven plugin site is
> intercepted and your job should have a link (with the label
> "Maven-generated site" ) to the generated site during the build (the
> site is backuped and transfered to the
Hello,
If you use the maven native jenkins plugin, the maven plugin site is
intercepted and your job should have a link (with the label
"Maven-generated site" ) to the generated site during the build (the
site is backuped and transfered to the master node).
So why not having an .htaccess file on p.
On Thu, Jun 16, 2011 at 11:54 AM, Niklas Gustavsson wrote:
> On Thu, Jun 16, 2011 at 11:49 AM, Reto Bachmann-Gmuer
> wrote:
> > This works fine when rnning site-deploy locally but not when having it
> > executed on hudson. Would it be possible to give hudson the right to
> > access people.apach
On Thu, Jun 16, 2011 at 4:54 AM, Niklas Gustavsson wrote:
> On Thu, Jun 16, 2011 at 11:49 AM, Reto Bachmann-Gmuer
> wrote:
>> This works fine when rnning site-deploy locally but not when having it
>> executed on hudson. Would it be possible to give hudson the right to
>> access people.apache.or
On Thu, Jun 16, 2011 at 11:49 AM, Reto Bachmann-Gmuer
wrote:
> This works fine when rnning site-deploy locally but not when having it
> executed on hudson. Would it be possible to give hudson the right to
> access people.apache.org? Or should we configure things differently?
There's been a few
Hello,
In clerezza we have the following directive in the root pom for deploying
the site:
people.apache.org
scp://
people.apache.org/www/incubator.apache.org/clerezza/mvn-site/
This works fine when rnning site-deploy locally but not when havin
13 matches
Mail list logo
