Hi,
Last night a build (#468) of one of our Maven projects was started by an
user manually by clicking on 'Rebuild Last'.
The build was marked as FAILED although the build log says "Finished:
UNSTABLE" (two tests failed).
While looking at the "Module Builds" view I saw that one of the modules w
Hi,
the 'Module Builds' view of one of our Maven jobs show modules which have
been deleted a while ago.
The module names have a grey ball prepended and '(didn’t run)' append.
I clicked on 'Delete All Disabled Modules' in the left menu which removed
some modules from the view but not all.
The
In the following workflow I need to get the hostname of the parent node.
node('clifford') {
sh "sh create-modules-list.sh > modules.txt"
}
def branches = [:]
branches["build1"] = {
node('clifford') {
ws {
sh "ssh build@${PARENT_HOST} 'bash -s' < get-next-module.sh
/var/lib/buil
Thanks Baptiste,
sounds like the solution. I will try that.
Clifford
Am Samstag, 28. März 2015 13:53:15 UTC+1 schrieb Baptiste Mathus:
>
> You can use try/catch/finally constructs.
>
> Cheers
>
> 2015-03-26 17:49 GMT+01:00 Clifford Sanders >:
>
>> Hi,
>>
&g
You can use the 'Timer Trigger Slicer' of 'Configuration Slicing Plugin'
https://wiki.jenkins-ci.org/display/JENKINS/Configuration+Slicing+Plugin
Clifford
Am Dienstag, 24. März 2015 23:54:59 UTC+1 schrieb LesMikesell:
>
> On a system with a large number of jobs configured, is there a way to
> f
Hi,
I'm currently migrating a Maven job to a Workflow job.
There are UI tests so one of the first steps is to start Xvfb before
executing the Maven command and stopping it afterwards.
sh "sudo /sbin/service xvfbd start"
sh "mvn clean verify -Dmaven.test.failure.ignore=true"
sh "sudo /sbin/servi
Thanks Daniel. I also found this related Jira isuue:
"Auto-installer for JDK no longer works":
https://issues.jenkins-ci.org/browse/JENKINS-26780
Am Dienstag, 24. März 2015 11:50:05 UTC+1 schrieb Daniel Beck:
>
>
> On 24.03.2015, at 11:39, Clifford Sanders > wrote:
>
Updating or restarting can't be done during office hours.
I solved it by copying the file 'hudson.tools.JDKInstaller' from my local
Jenkins to the 'updates' directory on the remote Jenkins.
Is there a Jira issue for the fix in 1.596? The original poster wrote that
the error still occures in 1.5
nstag, 24. März 2015 10:24:11 UTC+1 schrieb Daniel Beck:
>
> Go to Manage Jenkins » Manage Plugins » Advanced and click 'Check Now'.
>
> If that doesn't help, check the log at /log/all for possibly relevant
> messages.
>
> Are you in China or a neighboring countr
The JDKs that were already configured to download from java.sun now all
have the same 'JDK ID': jdk-8u40-oth-JPR (see attached screenshot)
Clifford
Am Dienstag, 24. März 2015 09:59:37 UTC+1 schrieb Clifford Sanders:
>
> We use version 1.594 and have the same problem. I attac
We use version 1.594 and have the same problem. I attached a screenshot.
Clifford
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@g
Hi Timur,
I had a similar problem with cloning into another directory. If you look
into the config.xml of a job where the GitSCM is used you see something
like this:
2
https://github.com/XX/XX.git'
*/master
Hi James,
try:
checkout changelog: true, poll: false, scm: [$class: 'GitSCM', branches:
[[name: '*/master']], doGenerateSubmoduleConfigurations: false, ,
extensions: [[$class:
'hudson.plugins.git.extensions.impl.RelativeTargetDirectory',
relativeTargetDir: 'myfunkydirectory']], submoduleCfg
13 matches
Mail list logo
