Re: Problem when trying to connect to GitHub from a Windows slave

[Sébastien Hinderer]

Hello David,

Many thanks for your response!

eyal david (2019/05/27 18:37 +0300):
> Hi
> Try to recreate new keys from the windows slave using the git bash ...

What do you mean by git bash ?

> than create credentails id in jenkins master based on the your private key
> created on the windows slave

And hten of course the public key needs to be added on GitHub. Well
since the manual clone worked I'm a bit reluctant to do all this, I have
to say.

Sébastien.

-- 
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...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/20190527204254.GA2102%40prajna.paris.inria.fr.
For more options, visit https://groups.google.com/d/optout.

Re: Problem when trying to connect to GitHub from a Windows slave

[Sébastien Hinderer]

Hi,

Many thanks for your response.

Geoffroy J (2019/05/27 09:18 -0700):
> Hello
> 
> Have you tried cloning manually using the ssh key on windows?

Yes, and it worked.
Sorry I forgot to mention this.

> Also, what username have you configured for your git credential on
> Jenkins?

The GitHub user name. But the 'git@' part in the URL of the repository.
Additionnally, as I mentionned, this setting works perfectly well for
the Unix machines.

> I faced ssh issues on windows because of change in SSH/GIT and it was 
> necessary to set credential username to 'git' instead of the real github 
> username. See https://issues.jenkins-ci.org/browse/JENKINS-50573

Thanks! Actually, my GitHub plugin is up-to-date so I'd expect this to
be fixed, right?

Also my error message is different from the one reported in the bug,
mine explicitly mentions an "invalid format" in the keyfile.

But many thanks for helping out, I really appreciate and hope we willl
find the problem!

Sébastien.

-- 
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...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/20190527203246.GB1939%40prajna.paris.inria.fr.
For more options, visit https://groups.google.com/d/optout.

Re: Problem when trying to connect to GitHub from a Windows slave

[Geoffroy J]

Hello

Have you tried cloning manually using the ssh key on windows?

Also, what username have you configured for your git credential on Jenkins?
I faced ssh issues on windows because of change in SSH/GIT and it was 
necessary to set credential username to 'git' instead of the real github 
username. See https://issues.jenkins-ci.org/browse/JENKINS-50573

BR

On Monday, 27 May 2019 16:50:59 UTC+2, Sébastien Hinderer wrote:
>
> Dear all, 
>
> Recently, I wanted my slaves to fetch our GitHub repository through 
> authenticated ssh coneections rather than through HTTPS unauthenticated 
> connections. 
>
> I created the appropriate Jenkins credential with ssh keys, replaced the 
> HTTPS URL of the repo by an ssh-based one and requested the use of the 
> newly created credential. 
>
> On our Unix machines everything works like a charm. 
>
> On our Windows machines, though, I get an "invalid format" message while 
> trying to read a .key file. 
>
> In case it's useful, our Windows hosts are running git 2.17.0 and 
> OpenSSH 7.8p1. 
>
> Many thanks in advance for any hint! 
>
> Sébastien. 
>

>

-- 
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...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/ddb9de8e-9a6d-4c3a-892d-4a08c9501322%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Problem when trying to connect to GitHub from a Windows slave

[Sébastien Hinderer]

Dear all,

Recently, I wanted my slaves to fetch our GitHub repository through
authenticated ssh coneections rather than through HTTPS unauthenticated
connections.

I created the appropriate Jenkins credential with ssh keys, replaced the
HTTPS URL of the repo by an ssh-based one and requested the use of the
newly created credential.

On our Unix machines everything works like a charm.

On our Windows machines, though, I get an "invalid format" message while
trying to read a .key file.

In case it's useful, our Windows hosts are running git 2.17.0 and
OpenSSH 7.8p1.

Many thanks in advance for any hint!

Sébastien.

-- 
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...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/20190527135323.GA32420%40prajna.paris.inria.fr.
For more options, visit https://groups.google.com/d/optout.

Need help with Multi module maven project

[Sakshi Arora]

Hi All,

I have create a multi module maven project using git submodules. How do I
configure that in Jenkins so that whenever commit happens in any of the
modules,  a trigger of the Jenkins job happens which builds and tests the
parent module.

Tried creating a scripted pipeline, and triggering is happening whenever
there is a commit in the parent module.

Expected :
Triggering should happen when there is a commit in any of the submodules as
well.

Please help. Badly stuck.

Thanks & Regards,
Sakshi

-- 
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...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CALD16FxbEA_Ru_so1GSSP6PyRAzeNLoBZsYzEB9zNHyjvgFspg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Advanced Project Options -> Display Name with a variable in it ?!?

[b o b i]

Advanced Project Options -> Display Name

Is there a way to introduce a variable in the display name, so that is 
displayed depending on this variable ?


-- 
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...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/90031264-e0a5-4475-a303-b72cf5b5d1b2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Pipeline: The sh step does not show all output

[Sverre Moe]

I got it to work by modifying my original sh step. I had to remove 
returnStdout

sh(label: "Build and Package", script: "make 2>&1 | tee buildOutputFile.txt"
)



mandag 27. mai 2019 15.50.07 UTC+2 skrev Sverre Moe følgende:
>
> Not sure I understand that workaround.
>
> "$@" 2>&1; echo $? >&3) | tee "$LOGFILE" >&4) 3>&1) | (read xs; exit 
> $xs)) 4>&1
>
> I tried to modify this to work with my example:
>
>
> final def output = sh(returnStdout: true, script: "make >&3) | tee 
> buildOutput.txt >&4) 3>&1) | (read xs; exit $xs)) 4>&1")
>
>
> Not quite sure how!
>
>
> mandag 27. mai 2019 12.57.28 UTC+2 skrev Ullrich Hafner følgende:
>>
>> Would a workaround as shown in 
>> https://issues.jenkins-ci.org/browse/JENKINS-54832 help?
>>
>> Am 27.05.2019 um 12:51 schrieb Sverre Moe :
>>
>> I found a way to ouput both stdout and stderr, but then I didn't get 
>> either in Jenkins Console.
>> sh("make 2>&1 | tee buildOutputFile.txt")
>>
>> mandag 27. mai 2019 12.20.17 UTC+2 skrev Sverre Moe følgende:
>>>
>>> The standard output from the sh-step does not show all the output:
>>> final def output = sh(returnStdout: true, label: "Build and Package", 
>>> script: "make")
>>> writeFile(file: 'buildOutputFile.txt', text: output)
>>>
>>> The Blue Ocean log output from a single Node shows all the warnings, but 
>>> the output from the sh step does not:
>>>
>>> https://JENKINS_URL/blue/rest/organizations/jenkins/pipelines/PROJECT/branches/BRANCH/runs/2/nodes/56/log/?start=0
>>>  
>>> 
>>>
>>> Could it be that the actual output is not stdout, but stderr? 
>>> Unfortunately sh does not have an returnStderr.
>>>
>>> I am using this output for the Warnings Plugin, since I want warning for 
>>> each build node, and the plugin default reads the entire console output.
>>> recordIssues(tools: [gcc4(id: "gcc-${buildHost}", name: "${buildHost}", 
>>> pattern: "buildOutputFile.txt")])
>>>
>>
>> -- 
>> 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...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/5efbb0ab-54e9-462c-86f6-2ff0593a88fa%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>>
>>

-- 
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...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/d92ff0fd-f8b3-4cdd-8203-9f7b56567798%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Pipeline: The sh step does not show all output

[Sverre Moe]

Not sure I understand that workaround.

"$@" 2>&1; echo $? >&3) | tee "$LOGFILE" >&4) 3>&1) | (read xs; exit $xs)) 
4>&1

I tried to modify this to work with my example:


final def output = sh(returnStdout: true, script: "make >&3) | tee 
buildOutput.txt >&4) 3>&1) | (read xs; exit $xs)) 4>&1")


Not quite sure how!


mandag 27. mai 2019 12.57.28 UTC+2 skrev Ullrich Hafner følgende:
>
> Would a workaround as shown in 
> https://issues.jenkins-ci.org/browse/JENKINS-54832 help?
>
> Am 27.05.2019 um 12:51 schrieb Sverre Moe 
> >:
>
> I found a way to ouput both stdout and stderr, but then I didn't get 
> either in Jenkins Console.
> sh("make 2>&1 | tee buildOutputFile.txt")
>
> mandag 27. mai 2019 12.20.17 UTC+2 skrev Sverre Moe følgende:
>>
>> The standard output from the sh-step does not show all the output:
>> final def output = sh(returnStdout: true, label: "Build and Package", 
>> script: "make")
>> writeFile(file: 'buildOutputFile.txt', text: output)
>>
>> The Blue Ocean log output from a single Node shows all the warnings, but 
>> the output from the sh step does not:
>>
>> https://JENKINS_URL/blue/rest/organizations/jenkins/pipelines/PROJECT/branches/BRANCH/runs/2/nodes/56/log/?start=0
>>  
>> 
>>
>> Could it be that the actual output is not stdout, but stderr? 
>> Unfortunately sh does not have an returnStderr.
>>
>> I am using this output for the Warnings Plugin, since I want warning for 
>> each build node, and the plugin default reads the entire console output.
>> recordIssues(tools: [gcc4(id: "gcc-${buildHost}", name: "${buildHost}", 
>> pattern: "buildOutputFile.txt")])
>>
>
> -- 
> 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...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-users/5efbb0ab-54e9-462c-86f6-2ff0593a88fa%40googlegroups.com
>  
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
>
>

-- 
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...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/17a84031-c584-4a8b-a5a5-309d21b0e46e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Error: Access denied connecting to TFS server http://dev.azure.com/

[Eoin Rockall]

Fixed it. I created a Personal Access Token and passed that in as the 
password instead. I can now access dev.azure but there is no mapping due to 
the working folder already being in use in the workspace. Is the only way 
to get around that error by deleting the workspace and creating a new 
mapping? 

Thanks



On Monday, 27 May 2019 12:37:43 UTC+1, Eoin Rockall wrote:
>
> Hi,
>
> My company has just migrated to DevOps from TFS and I have run into a few 
> problems with Jenkins and the running of the automated tests. 
>
> I changed the 'Collection URL' in the Source Code Management section from: 
>  
>
> http://tfs2010:8080/tfs/defaultCollection -> https://dev.azure.com/COMPANY
>
>
> But I am getting an error when I try to build the workspace, that access 
> to the server has been denied. I am 100% able to access the server using 
> the credentials.
>
> Has anyone seen an error like this before?
>
> Thanks
>
>  
>

-- 
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...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/83862616-6628-4642-a2af-9ab7ed05fa7f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Error: Access denied connecting to TFS server http://dev.azure.com/

[Eoin Rockall]

Hi,

My company has just migrated to DevOps from TFS and I have run into a few 
problems with Jenkins and the running of the automated tests. 

I changed the 'Collection URL' in the Source Code Management section from: 
 

http://tfs2010:8080/tfs/defaultCollection -> https://dev.azure.com/COMPANY


But I am getting an error when I try to build the workspace, that access to 
the server has been denied. I am 100% able to access the server using the 
credentials.

Has anyone seen an error like this before?

Thanks

 

-- 
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...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/19785688-f546-4d63-bb03-1e22aa686383%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins ParameterizedRemoteTrigger fails calling a job (but job runs ok)

[Elhanan Maayan]

turns out, if i use the actuall ip and the dns name when referring to the 
server it works
git commits: 
https://github.com/jenkinsci/parameterized-remote-trigger-plugin/commit/1cfeab90798f3c1af42241c39c2fe173f2e47016

 seems to show there was a change , but i'm not sure what that was.
On Monday, May 27, 2019 at 2:01:39 AM UTC+3, Elhanan Maayan wrote:
>
> hi..
>
> i'm keep getting this exception when calling a remote job from jenkins 
> (version 2.164.1) on a remote server version (2.174) 
>
>
> however when installing a new jenkins 2.174  on my own machine the remote 
> call works.
>
>
> the job itself is very simple no parameters, or anything, but it still fails. 
>
>
>
> java.lang.NullPointerException
>   at java.util.regex.Matcher.appendReplacement(Unknown Source)
>   at java.util.regex.Matcher.replaceAll(Unknown Source)
>   at java.lang.String.replaceAll(Unknown Source)
>   at 
> org.jenkinsci.plugins.ParameterizedRemoteTrigger.RemoteBuildConfiguration.updateBuildInfo(RemoteBuildConfiguration.java:826)
>   at 
> org.jenkinsci.plugins.ParameterizedRemoteTrigger.RemoteBuildConfiguration.performTriggerAndGetQueueId(RemoteBuildConfiguration.java:647)
>   at 
> org.jenkinsci.plugins.ParameterizedRemoteTrigger.RemoteBuildConfiguration.perform(RemoteBuildConfiguration.java:591)
>   at 
> org.jenkinsci.plugins.ParameterizedRemoteTrigger.RemoteBuildConfiguration.perform(RemoteBuildConfiguration.java:557)
>   at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
>   at 
> hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744)
>   at hudson.model.Build$BuildExecution.build(Build.java:206)
>   at hudson.model.Build$BuildExecution.doRun(Build.java:163)
>   at 
> hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504)
>   at hudson.model.Run.execute(Run.java:1816)
>   at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
>   at hudson.model.ResourceController.execute(ResourceController.java:97)
>   at hudson.model.Executor.run(Executor.java:429)
> Build step 'Trigger a remote parameterized job' marked build as failure
>
>

-- 
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...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/5c184d3b-6f92-4384-a894-c4786d5dd546%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Writing a stream of logs from a shared library so they appear under one collapsible panel in Blue Ocean

[Peter Goodman]

Hi,
So I have written some Groovy code in a shared library. I want that library 
to be able to write lots of logs (by polling an external api for the 
service I am integrating).

However, if I use echo or println they appear as new sections in the Blue 
Ocean UI.

[image: echo_in_blue_ocean.png]


What I want though is something more like the shell task output where it is 
under a single grouping/section and I can keep appending inside the section 
as I fetch more logs from the ongoing job in the external api.


I've tried getting a hold of TaskListener with getLogger but no joy.


Any ideas?



-- 
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...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/60b3373f-a294-4923-bdbe-48037722943d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Pipeline: The sh step does not show all output

[Ullrich Hafner]

Would a workaround as shown in 
https://issues.jenkins-ci.org/browse/JENKINS-54832 
 help?

> Am 27.05.2019 um 12:51 schrieb Sverre Moe :
> 
> I found a way to ouput both stdout and stderr, but then I didn't get either 
> in Jenkins Console.
> sh("make 2>&1 | tee buildOutputFile.txt")
> 
> mandag 27. mai 2019 12.20.17 UTC+2 skrev Sverre Moe følgende:
> The standard output from the sh-step does not show all the output:
> final def output = sh(returnStdout: true, label: "Build and Package", script: 
> "make")
> writeFile(file: 'buildOutputFile.txt', text: output)
> 
> The Blue Ocean log output from a single Node shows all the warnings, but the 
> output from the sh step does not:
> https://JENKINS_URL/blue/rest/organizations/jenkins/pipelines/PROJECT/branches/BRANCH/runs/2/nodes/56/log/?start=0
>  
> 
> 
> Could it be that the actual output is not stdout, but stderr? Unfortunately 
> sh does not have an returnStderr.
> 
> I am using this output for the Warnings Plugin, since I want warning for each 
> build node, and the plugin default reads the entire console output.
> recordIssues(tools: [gcc4(id: "gcc-${buildHost}", name: "${buildHost}", 
> pattern: "buildOutputFile.txt")])
> 
> -- 
> 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...@googlegroups.com 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-users/5efbb0ab-54e9-462c-86f6-2ff0593a88fa%40googlegroups.com
>  
> .
> For more options, visit https://groups.google.com/d/optout 
> .

-- 
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...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/C70314E1-145F-4C34-AFB6-B9813F209629%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Pipeline: The sh step does not show all output

[Sverre Moe]

I found a way to ouput both stdout and stderr, but then I didn't get either 
in Jenkins Console.
sh("make 2>&1 | tee buildOutputFile.txt")

mandag 27. mai 2019 12.20.17 UTC+2 skrev Sverre Moe følgende:
>
> The standard output from the sh-step does not show all the output:
> final def output = sh(returnStdout: true, label: "Build and Package", 
> script: "make")
> writeFile(file: 'buildOutputFile.txt', text: output)
>
> The Blue Ocean log output from a single Node shows all the warnings, but 
> the output from the sh step does not:
>
> https://JENKINS_URL/blue/rest/organizations/jenkins/pipelines/PROJECT/branches/BRANCH/runs/2/nodes/56/log/?start=0
>
> Could it be that the actual output is not stdout, but stderr? 
> Unfortunately sh does not have an returnStderr.
>
> I am using this output for the Warnings Plugin, since I want warning for 
> each build node, and the plugin default reads the entire console output.
> recordIssues(tools: [gcc4(id: "gcc-${buildHost}", name: "${buildHost}", 
> pattern: "buildOutputFile.txt")])
>

-- 
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...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/5efbb0ab-54e9-462c-86f6-2ff0593a88fa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Pipeline: The sh step does not show all output

[Sverre Moe]

The standard output from the sh-step does not show all the output:
final def output = sh(returnStdout: true, label: "Build and Package", script
: "make")
writeFile(file: 'buildOutputFile.txt', text: output)

The Blue Ocean log output from a single Node shows all the warnings, but 
the output from the sh step does not:
https://JENKINS_URL/blue/rest/organizations/jenkins/pipelines/PROJECT/branches/BRANCH/runs/2/nodes/56/log/?start=0

Could it be that the actual output is not stdout, but stderr? Unfortunately 
sh does not have an returnStderr.

I am using this output for the Warnings Plugin, since I want warning for 
each build node, and the plugin default reads the entire console output.
recordIssues(tools: [gcc4(id: "gcc-${buildHost}", name: "${buildHost}", 
pattern: "buildOutputFile.txt")])

-- 
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...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/0d105336-5172-4a18-b071-e4641357a4d2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Warnings Next Generation Plugin: Keep its history after discard builds

[Ullrich Hafner]

The trend charts are created dynamically using the available build results. So 
if you delete builds, then those results are also not available anymore. (This 
concept should be similar for all Jenkins plugins, or are e.g. test results 
shown for deleted builds?). 

One workaround would be to delete unused data in the build folders (e.g. 
artifacts, etc.), but not the build.xml files. 

An alternative approach would be 
a) Store the data of the visible trend information in the current build as 
well. Then you cannot remove builds with broken warning results anymore from 
the charts. I’m not sure if that is something we should consider?
b) Create a new Jenkins Visualizer App - independent of the Jenkins UI, that 
renders the results of various plugins. The shown data could be stored in an 
associated build artifacts database. Then we could have a headless Jenkins on 
the one side and a modern UI app on the other side. 
 
> Am 27.05.2019 um 10:38 schrieb Sverre Moe :
> 
> The "Warnings Trend" graphs are empty.
> 
> From out last build:
> sles15.0-x86_64: No warnings
> No warnings for 28 builds, i.e. since build 3
> 
> This might be because we delete old builds. We keep only the last 10 builds.
> In this case build #3 has been deleted.
> 
> Is there a workaround for this? We do not want to keep all builds in Build 
> History. As it requires much more disk space and (perhaps could slow down 
> Jenkins ((a guess)).
> 
> -- 
> 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...@googlegroups.com 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-users/1edbe937-2d9a-4dba-9a72-d4b567299bab%40googlegroups.com
>  
> .
> For more options, visit https://groups.google.com/d/optout 
> .

-- 
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...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/8C298C1F-B433-473A-9674-5DFBDA405D85%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

editable parameters, dependent on previous parameter choices?

[b o b i]

We have the active choice plug-in to create dynamically parameter choices 
dependent on previous parameter choices. These choices are not editable.

We have the extensible choice plug-in to create editable parameter. But you 
cannot create depended choices on previous parameters.

So, how you do combine both worlds?

-- 
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...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/31229a90-7b72-43fe-8fdb-4a6a43a11a21%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Warnings Next Generation Plugin: Keep its history after discard builds

[Sverre Moe]

The "Warnings Trend" graphs are empty.

>From out last build:
sles15.0-x86_64: No warnings
No warnings for 28 builds, i.e. since build 3

This might be because we delete old builds. We keep only the last 10 builds.
In this case build #3 has been deleted.

Is there a workaround for this? We do not want to keep all builds in Build 
History. As it requires much more disk space and (perhaps could slow down 
Jenkins ((a guess)).

-- 
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...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/1edbe937-2d9a-4dba-9a72-d4b567299bab%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.