Re: Disable withMaven publishers default configuration

[ncosta]

>
> I still think that when pipeline-maven auxiliar plugins are not installed, 
> it shouldn't display that information on console log, when using this 
> logger:
> org.jenkinsci.plugins.pipeline.maven
>
> On logger output, one can see that the findbugs plugin is not found and 
> jgiven is not even shown here(it should !?). None of them is installed on 
> TEST instance.
>
> Dec 20, 2017 10:40:28 AM FINE 
> org.jenkinsci.plugins.pipeline.maven.publishers.FindbugsAnalysisPublisher
>
> No org.codehaus.mojo:findbugs-maven-plugin:findbugs execution found
>
>
> On console log, it could mention that they are not installed or even  not 
> shown at all. At the moment, there is no indication that the plugins are 
> not installed.
> In case of JGiven, it is not clear (at least for me) if the abort is due 
> to missing jenkins plugin or if the project being built, does not use 
> jgiven. In my understanding, I would assume the latter.
>
> [debug] [withMaven] Run 'Findbugs Publisher'...
> [debug] [withMaven] Run 'JGiven Publisher'...
> [debug] [withMaven] jgivenPublisher - JGiven not found within your project 
> dependencies, aborting.
>
>
> Not sure if this input is already being considered (our previsously 
> discarded) but if you think it should have a new bug report open, let me 
> know :)
>


Issues created for JGiven (JENKINS-48935 
) and FindBugs (
JENKINS-48937 ) 
improvements. 

-- 
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/727ebf69-d853-4571-b77e-460672905cb0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Disable withMaven publishers default configuration

[ncosta]

Hi Cyrille

Thanks for your clarification.

I now have the TEST and PROD using the same logger 
(org.jenkinsci.plugins.pipeline.maven.WithMavenStepExecution >> ALL).
Disabling the publishers on Global Tools Configuration screen, the 
publishers are shown as "Skip ... disabled by configuration" in Console 
output. Same as using the options from pipeline configuration.

Having the publishers disabled by default would be a better starting point, 
to avoid extra configuration. I'm now following JENKINS-46785.

I still think that when pipeline-maven auxiliar plugins are not installed, 
it shouldn't display that information on console log, when using this 
logger:
org.jenkinsci.plugins.pipeline.maven

On logger output, one can see that the findbugs plugin is not found and 
jgiven is not even shown here(it should !?). None of them is installed on 
TEST instance.

Dec 20, 2017 10:40:28 AM FINE 
org.jenkinsci.plugins.pipeline.maven.publishers.FindbugsAnalysisPublisher

No org.codehaus.mojo:findbugs-maven-plugin:findbugs execution found


On console log, it could mention that they are not installed or even  not 
shown at all. At the moment, there is no indication that the plugins are 
not installed.
In case of JGiven, it is not clear (at least for me) if the abort is due to 
missing jenkins plugin or if the project being built, does not use jgiven. 
In my understanding, I would assume the latter.

[debug] [withMaven] Run 'Findbugs Publisher'...
[debug] [withMaven] Run 'JGiven Publisher'...
[debug] [withMaven] jgivenPublisher - JGiven not found within your project 
dependencies, aborting.


Not sure if this input is already being considered (our previsously 
discarded) but if you think it should have a new bug report open, let me 
know :)

On Friday, 15 December 2017 00:53:50 UTC+1, Cyrille Le Clerc wrote:
>
> Hello,
>
> You had enabled logging on your test master and we display in the build 
> logs the logs of the plugin, this is why you had these messages on your 
> test masters.
>
> You can disable globally publishers through the Global Tools Configuration 
> screen.
>
> The message may not be intuitive but here is what happened:
>
>- "Use pipeline defined publisher for 'Findbugs Publisher'" --> the 
>config of the findbugs publisher is defined in the pipeline, in 
>"withMaven(options:[findbugsPublisher(...)]"
>- "Skip 'Findbugs Publisher' disabled by configuration" --> the 
>Findbugs Publisher is disabled
>- "pipelineGraphPublisher - triggerDownstreamPipelines" --> even if 
>you disable the "pipelineGraphPublisher" by configuration, we have a 
>listener of the pipeline build completion to decide if we trigger 
>downstream pipelines. We need to wait for the completion of the build 
>because the downstream pipeline trigger strategy is based on the result of 
>the upstream build, you probably don't want to trigger downstream 
> pipelines 
>if your build failed.
>
> Stephen Connolly mentioned another use case:disabling all the 
> publishers unless they are explicitly enabled in the pipeline 
> ("withMaven(options:[myPublisher(enabled: 
> true])"). James Nord had created a while ago the RFE JENKINS-46785 add a 
> way to disable all reporters (and selectively enable a few) 
> 
> .
> If have started to work on it with 
> https://github.com/jenkinsci/pipeline-maven-plugin/pull/116 and James 
> validated the user Experience. I'll provide details later.
>
> Did this clarify your messages?
>
> Cyrille 
>
>
>
> On Thursday, December 14, 2017 at 11:46:07 AM UTC+1, nco...@lbisa.com 
> wrote:
>>
>> Just noticed that PROD has a different logger. It is using:
>> org.jenkinsci.plugins.pipeline.maven.WithMavenStepExecution
>>
>> and test was using:
>> org.jenkinsci.plugins.pipeline.maven
>>
>> Both were set to log level ALL.
>> After set test instance to use the same logger, the output are similar in 
>> both instances.
>>
>> Additionally, tested remove the logger from test and seems that the 
>> default console output is the same as:
>> org.jenkinsci.plugins.pipeline.maven.WithMavenStepExecution
>>
>

-- 
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/1b928717-df20-41ae-82fa-c5b7b1b017db%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Disable withMaven publishers default configuration

[ncosta]

Just noticed that PROD has a different logger. It is using:
org.jenkinsci.plugins.pipeline.maven.WithMavenStepExecution

and test was using:
org.jenkinsci.plugins.pipeline.maven

Both were set to log level ALL.
After set test instance to use the same logger, the output are similar in 
both instances.

Additionally, tested remove the logger from test and seems that the default 
console output is the same as:
org.jenkinsci.plugins.pipeline.maven.WithMavenStepExecution

-- 
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/82ca84be-c8dd-43a4-b2e3-6a8874f205c4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Disable withMaven publishers default configuration

[ncosta]

Both PROD and test have the same Global Tool Configuration Maven 
Configuration (defaults and no publishers configured) and are running the 
same versions of Pipeline Maven Integration (3.0.3).
PROD is on Jenkins 2.92 and test on 2.93, so not sure if that and PROD not 
restarted after plugin updates could be triggering this difference in 
behaviour.

Using *withEnv(['JENKINS_MAVEN_AGENT_DISABLED=true'])* disables all 
publishers (and all configurantion entries are not seen) except 

[withMaven] pipelineGraphPublisher - triggerDownstreamPipelines
[withMaven] Skip downstream job triggering for upstream build with ignored 
result status...
...


You still need to disable pipelineGraphPublisher with option 
*pipelineGraphPublisher(disabled: 
true)*.
Also, it seems that pipelineGraphPublisher is not in the plugin 
documentation  but is available 
on Pipeline Syntax snippet generator.

On Wednesday, 13 December 2017 13:41:37 UTC+1, Stephen Connolly wrote:
>
> Is prod running an older version of the plugin. Disabling is only a recent 
> feature. Also see 
> https://issues.jenkins-ci.org/plugins/servlet/mobile#issue/JENKINS-46785 
> for a related request about being able to disable default publishers so 
> that options only specifies the ones you want configured.
>

-- 
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/9f302194-4b22-4b50-a2c2-4fe8f125ee0d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Disable withMaven publishers default configuration

[ncosta]

Hi

Does any one knows what provides and how to disable Maven not to trigger 
"*Maven 
Publishers with default configuration*:" info in Console Output?

If I run the same code on 2 different Jenkins instances, one of them do not 
have this kind of diferenciation between Maven Publishers set by Default, 
Global or Pipeline configuration.

Console ouput from my test Jenkins:

[withMaven] Maven Publishers with configuration provided by the pipeline: 
[org.jenkinsci.plugins.pipeline.maven.publishers.DependenciesFingerprintPublisher[disabled=true,
 scopes=[compile, provided, runtime], versions={snapshot:true, release:false}], 
org.jenkinsci.plugins.pipeline.maven.publishers.FindbugsAnalysisPublisher[disabled=true],
 
org.jenkinsci.plugins.pipeline.maven.publishers.GeneratedArtifactsPublisher[disabled=true],
 
org.jenkinsci.plugins.pipeline.maven.publishers.JGivenTestsPublisher[disabled=true],
 
org.jenkinsci.plugins.pipeline.maven.publishers.PipelineGraphPublisher[disabled=true,
 scopes=[compile, provided, runtime], versions={snapshot:true, release:false}, 
skipDownstreamTriggers=false, lifecycleThreshold=deploy, 
ignoreUpstreamTriggers=false], 
org.jenkinsci.plugins.pipeline.maven.publishers.JunitTestsPublisher[disabled=true],
 
org.jenkinsci.plugins.pipeline.maven.publishers.InvokerRunsPublisher[disabled=true],
 
org.jenkinsci.plugins.pipeline.maven.publishers.TasksScannerPublisher[disabled=true],
 
org.jenkinsci.plugins.pipeline.maven.publishers.ConcordionTestsPublisher[disabled=true]]
[withMaven] Maven Publishers with configuration defined globally: []
[withMaven] Maven Publishers with default configuration: 
[org.jenkinsci.plugins.pipeline.maven.publishers.DependenciesFingerprintPublisher[disabled=false,
 scopes=[compile, provided, runtime], versions={snapshot:true, release:false}], 
org.jenkinsci.plugins.pipeline.maven.publishers.FindbugsAnalysisPublisher[disabled=false],
 
org.jenkinsci.plugins.pipeline.maven.publishers.GeneratedArtifactsPublisher[disabled=false],
 
org.jenkinsci.plugins.pipeline.maven.publishers.JGivenTestsPublisher[disabled=false],
 
org.jenkinsci.plugins.pipeline.maven.publishers.PipelineGraphPublisher[disabled=false,
 scopes=[compile, provided, runtime], versions={snapshot:true, release:false}, 
skipDownstreamTriggers=false, lifecycleThreshold=deploy, 
ignoreUpstreamTriggers=false], 
org.jenkinsci.plugins.pipeline.maven.publishers.InvokerRunsPublisher[disabled=false],
 
org.jenkinsci.plugins.pipeline.maven.publishers.JunitTestsPublisher[disabled=false],
 
org.jenkinsci.plugins.pipeline.maven.publishers.TasksScannerPublisher[disabled=false],
 
org.jenkinsci.plugins.pipeline.maven.publishers.ConcordionTestsPublisher[disabled=false]]
[withMaven] Use pipeline defined publisher for 'Dependencies Fingerprint 
Publisher'
[withMaven] Use pipeline defined publisher for 'Findbugs Publisher'
[withMaven] Use pipeline defined publisher for 'Generated Artifacts Publisher'
[withMaven] Use pipeline defined publisher for 'JGiven Publisher'
[withMaven] Use pipeline defined publisher for 'Pipeline Graph Publisher'
[withMaven] Use pipeline defined publisher for 'Invoker Publisher'
[withMaven] Use pipeline defined publisher for 'Junit Publisher'
[withMaven] Use pipeline defined publisher for 'Open Task Scanner Publisher'
[withMaven] Use pipeline defined publisher for 'Concordion Publisher'
[withMaven] Skip 'Generated Artifacts Publisher' disabled by configuration
[withMaven] Skip 'Invoker Publisher' disabled by configuration
[withMaven] Skip 'Junit Publisher' disabled by configuration
[withMaven] Skip 'Concordion Publisher' disabled by configuration
[withMaven] Skip 'Dependencies Fingerprint Publisher' disabled by configuration
[withMaven] Skip 'Findbugs Publisher' disabled by configuration
[withMaven] Skip 'JGiven Publisher' disabled by configuration
[withMaven] Skip 'Pipeline Graph Publisher' disabled by configuration
[withMaven] Skip 'Open Task Scanner Publisher' disabled by configuration


withMaven config:
withMaven(mavenSettingsConfig: "${mvnsettingsid}", options: [
openTasksPublisher(disabled: true), 
dependenciesFingerprintPublisher(disabled: true), 
artifactsPublisher(disabled: true), 
junitPublisher(disabled: true), 
jgivenPublisher(disabled: true), 
invokerPublisher(disabled: true), 
findbugsPublisher(disabled: true),
concordionPublisher(disabled: true), 
pipelineGraphPublisher(disabled: true)
]) { 

On the PROD instance, I do not see this entries in console output:

Maven Publishers with configuration provided by the pipeline: 
[org.jenkinsci.plugins.pipeline.maven.publishers.DependenciesFingerprintPublisher[disabled=true,
 scopes=[compile, provided, runtime], versions={snapshot:true, release:false}], 

Track docker images usage

[ncosta]

Hi

Is there any tips on how to be able to track the overall docker image usage 
in a Jenkins server?

Like X image is being used by Y or Y and Z projects.

Tried using the CloudBees Docker Traceability 
 plugin 
but the link to it is not shown on the left menu, as displayed in the 
readme file on readme file 

.

If i go to http://localhost:8080/docker-traceability/ manually, it displays 
the page correctly.

Docker commands are run on a different server than Jenkins and containers 
are only used to compile software and discarded when finished.

Any tips or suggestions?

Thanks
Nuno

-- 
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/c1f3b9cb-5b82-4a78-9a7d-bf167dd7f2aa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Job properties are not (should be !?) cumulative

[ncosta]

Project properties are not cumulative when additional settings are set 
during the pipeline.


For example, if setting a Parameterized build and later in the pipeline, 
a Discard Old Builds is set, the Parameterized build is unset.

I had this happening when the Discard Old Builds were used in a Shared 
library, later in the pipeline.


When a additional propertie is set, it shouldn't unset all the previous 
properties, if they are not the same type (discard builds vs parameters).


Someone know if this is working as designed or is something that could be 
implemented?

-- 
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/f4ad1274-d5ad-470c-9c8a-6e8f7a3483b9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Pipeline one-liner causes hanging job ?

[ncosta]

>
> This caused my Pipeline Job to hang - so I have to kill it. 
>
 
As mentioned in this  
issue, you can use as workaround

assert false : 'oh no!'


Not sure if the resolution was already released.

-- 
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/a1019ca5-c93f-46bb-9368-6289e9ec348d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Techniques for managing an scp call to a remote box, with a specific principal

[ncosta]

>
> Yes, I've seen those two plugins, but I don't understand how I would use 
> either of these from a pipeline job.

  
As Rachel mentioned, Publish over ssh is still lacking pipeline support. 
You can check additional pipeline plugins compatibility here 


You can check the Pipeline Syntax link on you Pipeline script, on how to 
use the sh: Shell script step, to pass a normal scp/ssh command. 

-- 
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/05a23acd-1a2d-4af6-ae75-003d5cfa5281%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.