On Mon, Jan 16, 2023 at 10:00 AM geoffroy...@gmail.com <
geoffroy.jabou...@gmail.com> wrote:
> you need to relax CSP rules for proper display, as mentioned by Xavier.
>
The recommended alternative for more than three years is to configure the
resource root URL as explained on
Hello
I confirm that the publishHTML plugin will provide you with the needed
feature. And also that you need to relax CSP rules for proper display, as
mentioned by Xavier.
we use an init.groovy.d script
email.com' via Jenkins Users"
To: "Jenkins Users"
Sent: Friday, January 13, 2023 3:51:12 PM
Subject: Re: HTML pages as archived artifacts
Hi Jochen,
one of my jobs generates a html-report as output from source code documentation
(doxygen). Instead of archiving I hand the
Hi Jochen,
one of my jobs generates a html-report as output from source code
documentation (doxygen). Instead of archiving I hand the html over to
publishHTML. Therefore displaying from the job works perfectly. I did not
care for downloading the html though so you might need to do both.
BR,
Hi,
one of my build jobs is creating a few reports (HTML pages), that are being
archived as artifacts.
The created pages appear to be perfectly fine: If I download, and open
them, then thy look exactly as expected.
Unfortunately, they don't look the same, if I view them within Jenkins by
jenkins version 1.642 on centos 7.1
As a post build step we archive about 30 zips, gzs and isos to a mounted
nfs filesytem on the jenkin server. We are starting to find some of the
archived files are corrupted. Its a random occurence. This is verified
because we do a checksum on the files
Hi -
We have many jobs that work correctly, but one maven (integration) job is
displaying weird behaviour.
It runs correctly, it reports 'artifacts being archived'. These appear in
the .jenkins directory in the place I'd expect. However, the left-hand
sidebar reports a build size of '1 MB', and
-hand sidebar reports a build size of '1 MB', and there are no
links to be able to download those modules. As far as I can tell,
there's nothing special with the configuration of this project (it was
likely cloned from a different build).
The archived artifacts can be found under each module. I
Domi, I think this is the solution to my problem. I will try this.
Thanks!
On Tue, Dec 18, 2012 at 1:04 PM, domi d...@fortysix.ch wrote:
In the advanced section of your maven build, you can Disable automatic
artifact archiving
With the Create Job Advanced Plugin you can disable this setting
You use maven style project, it saves build artifacts. If you have problems
with space, decrease history.
On 10.12.2012, at 20:41, Nicky Ramone nixe...@gmail.com wrote:
Hello.
I noticed that despite my configuration is defined so that no artifacts are
archived, the artifacts are stored in
In the advanced section of your maven build, you can Disable automatic
artifact archiving
With the Create Job Advanced Plugin you can disable this setting per default
for new jobs:
https://wiki.jenkins-ci.org/display/JENKINS/Create+Job+Advanced+Plugin
/Domi
On 18.12.2012, at 16:26,
Hi Nicky,
is the comma set on purpose?
dummy,tar.gz - look between dummy and tar
Regards
Jan
Am Montag, 10. Dezember 2012 18:41:36 UTC+1 schrieb Nicky Ramone:
Hello.
I noticed that despite my configuration is defined so that no artifacts
are archived, the artifacts are stored in the disk
Did anyone notice the same behavior?
On Mon, Dec 10, 2012 at 2:41 PM, Nicky Ramone nixe...@gmail.com wrote:
Hello.
I noticed that despite my configuration is defined so that no artifacts
are archived, the artifacts are stored in the disk anyway for all builds.
Example:
Hello.
I noticed that despite my configuration is defined so that no artifacts are
archived, the artifacts are stored in the disk anyway for all builds.
Example:
$JENKINS_HOME/jobs/dummy/modules/com.dummy/builds/2012-07-12_10-24-06/archive/com.dummy/dummy/dummy,tar.gz
Is this due to
14 matches
Mail list logo
