Both would be good solutions. Especially the first so I don't have to run 
that job on my own build server :-)

Unfortunately, for the second one, I cannot log in to jenkins.ci to exclude 
gh-pages, so this is something someone at cloudbees would have to do (maybe 
globally for all jenkins plugin jobs build on that jenkins instance?)

Regards,
Hakan

On Thursday, October 31, 2013 1:48:57 PM UTC+1, nicolas de loof wrote:
>
> This is to publish maven generated site, isn't it ?
> Maybe we could just add this to the ci job and publish on 
> jenkins.ci.cloudbees.com using html report plugin, so you don't have to 
> manage it and update gh-pages 
>
> other option is to exclude gh-pages from monitored branches, git-plugin 
> allows to pass a regex, need to double check how to get "all branches but 
> gh-pages"
>
>
> 2013/10/31 Hakan Tandoğan <[email protected] <javascript:>>
>
>> Hi,
>>
>> I keep the maven site report of my transifex plugin ( 
>> https://github.com/jenkinsci/transifex-plugin ) in the gh-pages branch 
>> of my source repository. Unfortunately, any site generation and push to 
>> this branch causes a build to be performed on cloudbees ( 
>> https://jenkins.ci.cloudbees.com/job/plugins/job/transifex-plugin/ ).
>>
>> Is there a way to tell cloudbees that certain branches should not be 
>> built?
>>
>> I already thought about putting a very basic, nearly empty pom into the 
>> gh-pages as well but this would dilute any build success information I 
>> would have on the cloudbees job.
>>
>> Regards,
>> Hakan
>>
>>  -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to [email protected] <javascript:>.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to