could elaborate there how we could fix this.
Which Jar needs the manifest, which library needs to be whitelisted and how
can we achieve this?
Cheers,
Johannes
Am Donnerstag, 1. März 2018 20:23:15 UTC+1 schrieb Kohsuke Kawaguchi:
>
> Jenkinsfile Runner is an experiment to package Jenkins pipeli
Jenkinsfiles from
>> the shared libraries pipeline and failing the build if the IT fails.
>>
>
> That'd be really cool, isn't it!?
>
>> Of course, this would be very basic testing. For more sophistiated
>> testing we would want to
>>
>>
>>
sults as JUnit XML.
So, yes, we're not there yet. But we now have a foundation to build all
this upon.
Thanks for that & best regards,
Johannes
Am Donnerstag, 1. März 2018 20:23:15 UTC+1 schrieb Kohsuke Kawaguchi:
>
> Jenkinsfile Runner is an experiment to package Jenkins pipeli
/eXistence/valgrind-plugin.git
greetings,
Johannes
release (with some other
small changes) over the course of the day.
Johannes
Am Mittwoch, 9. Mai 2012 09:44:02 UTC+2 schrieb asmundo:
I have been hoping this should be created! On [1] it states that it needs
Jenkins core 1.455 is this actually needed? I ask because my production
environment
,
Johannes
Hi Chris,
Thanks for your answer, that helped a lot :)
Regards,
Johannes
Am Montag, 14. Mai 2012 14:24:51 UTC+2 schrieb cjo:
Kind and stapler-class are used by the stapler to bind the configuration
section to the correct class (in this case your plugin), this also enabled
the stapler
builds for all jobs? My initial
(naive?) expectation was that jenkins would only deserialize a build when a
user opens it in the browser.
Or am i doing something fundamentally wrong with the way the plugin stores
its data?
Regards,
Johannes
System - Maven
Project Configuration
a. Add -Djdk.lang.Process.allowAmbigousCommands to the Global
MAVEN_OPTS
Regards,
Johannes
--
You received this message because you are subscribed to the Google Groups
Jenkins Developers group.
To unsubscribe from this group and stop receiving emails
to be
done.
1) %base%\jenkins.xml
a. Add -Djdk.lang.Process.allowAmbigousCommands to the arguments
2) In the configuration Manage Jenkins - Configure System - Maven
Project Configuration
a. Add -Djdk.lang.Process.allowAmbigousCommands to the Global
MAVEN_OPTS
Regards,
Johannes
Hi Jesse,
could you give me a hint how to try it out?
I tried
mvn hpi:run -Djenkins.version=2.154-rc27545.0e85c9fb206a
which does not work (of course) because I don't have a snapshot repository
configured. A quick search didn't give me
the the URL for the snapshot repository. Could you help
But where are the snapshots published to? I can't find the version
2.154-rc27545.0e85c9fb206a
on
https://repo.jenkins-ci.org/incrementals/org/jenkins-ci/main/jenkins-core/
I am running:
mvn hpi:run -Djenkins.version=2.154-rc27545.0e85c9fb206a
-Pconsume-incrementals
Which does not work since
I will try
> 2.154-rc27545.0e85c9fb206a
>
as soon as it is build.
One question: What are the workarounds? What can be done?
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails
tion class.
Running the job a second time on the same computer works just fine.
The exception occurs after the job has finished.
Any idea how to solve that?
Regards,
Johannes
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
14 matches
Mail list logo