date:20181030

RE: Jenkins Administration - Role-based Authorization Strategy - Manage & Assign Roles list really big

2018-10-30 Thread Beushausen, Christian

Hi,

We set up dedicated AD groups for different types of users (developers, users, 
integrators) and only those groups are maintained on Jenkins. Everything else 
is done via the AD groups.

Maybe also not the best approach, but this way we were able to mostly 
centralize all access requests to one single point of entry.

Br,
Christian

From: jenkinsci-users@googlegroups.com  On 
Behalf Of gotviser...@gmail.com
Sent: Mittwoch, 24. Oktober 2018 21:50
To: Jenkins Users 
Subject: Jenkins Administration - Role-based Authorization Strategy - Manage & 
Assign Roles list really big

We use Role-based Authorization Strategy plugin and when we go to Assign Roles, 
the list is really huge and it's becoming hard day by day to add users.  Is 
there a way to address this issue?

1) We are currently handling these manually.  Is there a way to handle this 
manual (like freeze panes in Windows Excel or something of that sort)?
2) Can we automate this using Ansible as we are going to have Ansible setup 
soon?
--
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/43505685-e9c9-41ab-8ba7-312859a42f80%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/AM0PR0302MB3410369F9F3E6291B21D4145CFCC0%40AM0PR0302MB3410.eurprd03.prod.outlook.com.
For more options, visit https://groups.google.com/d/optout.

Re: Connecting Jenkins to GitHub

2018-10-30 Thread Mark Waite

If Jenkins is running under your user id and the GitHub repository URL is
using SSH and you're using command line git as the git implementation, then
command line git fallback to use your default ssh private key.  That's a
behavior of command line git more than a behavior of Jenkins.

If Jenkins is running under your user id and the GitHub repository https
repository credentials have been permanently stored with git credentials,
then command line git will use those credentials.

If Jenkins is running under another user id or the GitHub repository URL is
using https without stored credentials or you're using JGit, then a
credential will need to be provided.

It is usually best to provide those credentials and not rely on command
line git defaults.

Mark Waite

On Mon, Oct 29, 2018 at 1:56 PM HB  wrote:

> Thank you.  After installing the GitHub integration plugin and watching
> the video, I was able to create a project just as in the video.
>
> My GitHub repository contains only the README.md file as well, however the
> difference is that my repo is private.  The item I create to my private
> repo on GitHub is not requiring that I add any credentials.  Despite not
> creating any credentials after clicking the git radio button under 'Source
> Code Management', I can just save the item successfully.  I can also click
> on the GitHub link within the project and it takes me right to the repo in
> GitHub.
>
> Does this sound correct?  I feel like it should require defining
> credentials to successfully connect to GitHub.  Or is it that I am being
> successfully connected via the public key that I put in place on the GitHub
> side?  Or is it possibly a cookie that is allowing the connection?  Is that
> something I can verify some how?
>
> Thanks,
>
> HB
>
> On Sunday, October 28, 2018 at 8:32:54 PM UTC-7, sagar utekar wrote:
>>
>> Hi,
>>
>> Search for a GitHub integration plugin.
>>
>> Here is a YouTube video link you can refer -
>> https://youtu.be/Z3S2gMBUkBo
>>
>> Thank you.
>>
>> On Mon, 29 Oct 2018, 08:55 HB,  wrote:
>>
>>> Thank you for the reply.  I am not seeing 'gith' plugin, is that short
>>> for a plugin?  Here are the plugins that I have installed referring to git
>>> and ssh:
>>>
>>> Git client plugin
>>> 2.7.3
>>> Git plugin
>>> 3.9.1
>>> GIT server Plugin
>>> 1.7
>>> GitHub API Plugin
>>> 1.92
>>> GitHub Branch Source Plugin
>>> 2.4.1
>>> GitHub plugin
>>> 1.29.3
>>>
>>> SSH Credentials Plugin
>>> 1.14
>>> SSH Slaves plugin
>>> 1.28.1
>>>
>>> Am I missing plugins that you are referring to?  Thanks again, any
>>> guidance is greatly appreciated..
>>>
>>> HB
>>>
>>> On Sunday, October 28, 2018 at 7:07:08 PM UTC-7, Robert Rajendra wrote:

 To integrate Jenkins with github. You need to install gith , github
 plugins with ssh plugin you can read the docs regarding these and get the
 work done

 On Mon, 29 Oct 2018, 3:06 am HB,  wrote:

> All,
>
> I am completely new to Jenkins but am tasked with getting a working
> environment up and running.
>
> Everything appears to running well as follows:
>
> RHEL 7.5
> Jenkins ver 2.148
>
> Installed using the below yum repo:
> [jenkins]
> name=Jenkins
> baseurl=http://pkg.jenkins.io/redhat
> gpgcheck=1
>
> I have it configured to use Active Directory for user authentication
> and roles.
>
> My questions revolve around getting Jenkins connected to GitHub.  I am
> following these steps:
>
> https://gist.github.com/misterbrownlee/3708738
>
> I have created a 'utility user' (say git-jenkins) in GitHub that will
> ideally be the user that Jenkins uses to connect to GitHub.  I also have
> created a key pair for the connection.  Since Jenkins runs as user
> 'jenkins' on the server, I created the key pair as this user and imported
> the public key to the 'git-jenkins' utility user in GitHub.
>
> I also set:
>
> Global Config user.name Value
> Global Config user.email Value
>
> to the 'git-jenkins' GitHub utility user via: Manage Jenkins -->
> Configure System.
>
>
> I am trying to follow these steps:
>
> - Make sure the Manage Jenkins > Configure System has the right path
> to git
> - Set the global git user.name and user.email to match your global
> config options
> - Configure GitHub Web Hook to Manually manage hook urls
> - Click the (?) icon next to the manual option and copy the hook URL
> you see there
> - Optionally set the service account email as the Jenkins sender email
> address
>
> However, I am not able to successfully 'test connection' to GitHub in
> Manage Jenkins --> Configure System..
>
> I am able to clone the repository from the command line with a
> different user than the 'git-jenkins' utility user via Jenkins.  But since
> the 'jenkins' user on the server does not have a login shell out of the
>

Re: Problem with Java 8 update 191?

2018-10-30 Thread Mark Waite

Those workspace names are not an indication of an incompatibility.  If
Jenkins needs to allocate a workspace and it detects that the default named
workspace is already in use, it will allocate a second workspace adjacent
to the first, with a digit appended to the workspace name.

Mark Waite

On Mon, Oct 29, 2018 at 11:28 PM James Fairweather <
james.fairweat...@blackbirdinteractive.com> wrote:

> Today I installed the version of Java from 8 build 181 to 8 build 191 on
> several build slaves.  After doing that, Jenkins started allocating a 2nd
> workspace on the some of the build agents.  For example, instead of running
> here:
>
> D:\projects\lion\main
>
> They were running here:
>
> D:\projects\lion\main@2
>
> Each build agent has been allocated a single executor.  We are running
> Jenkins 2.138.2.  I rolled the version of Java on the non-working agents
> back to Update 181 and the problem went away.
>
> Does anyone know if Java 8 Update 191 has some kind of incompatibility
> problem with Jenkins?
>
> --
> 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/CALg80NUJuzJ8nsMkTqwewuLn4UFvATinP0rvA%3DcMv_n-_WmPfg%40mail.gmail.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/CAO49JtEJaL1wyweKHmt-11-R2BbZ4ujy45hD1T-r6oc6uhz6BQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Making the jenkins scm checkout smart

2018-10-30 Thread Mark Waite

Replies inline

On Tue, Oct 30, 2018 at 7:43 AM touseef  wrote:

> Hi ,
>
> I have a source code repository having multiple branches say branch1,
> branch2 and so on.
>
> Currently i have a jenkins jobs which builds the master or whatever i
> specify in job configuration.Now what i wish to achieve is if i commit my
> changes to branch 1 , my jenkins job should automatically context switch
> from master to branch1 and build that, and in the next step if i commit on
> branch2 it should  build branch 2.
>
> i am able to make rest calls via DSL script to get the branch names and
> then use job dsl  to create  the jobs  as the number of branches are
> present.
> However i don't want multiple jobs. What i am looking is having a single
> intelligent job to do the context switching between jobs.
>
>

Can you further explain why you want a "single intelligent job to do the
context switching"?

That is a technique that was used in the past with Jenkins freestyle jobs.
The technique makes it very hard to diagnose the locations of test
failures, or the place where a compilation failure happened, or the
differences from one job to the next.

If you're not using Pipeline jobs, then having a single job which builds
any of several branches is relatively easy (add the branch names to build),
though it will tend to confuse most users.

If you're using Pipeline jobs, you'll likely be much happier with a
multibranch pipeline so that each branch gets its own job and job history
and so that new jobs are created automatically for new branches and are
automatically destroyed for deleted branches.

Mark Waite

> Any idea or help will be appreciated.
>
> Thanks,
> Touseef
>
> --
> 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/3543d8da-3c80-4764-bc7c-092053f8c103%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/CAO49JtHHTJeWtSCsU5gGfCKf-qhH0OH21fGW1gDNteU%2BD4oLvw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: java.lang.NoSuchMethodError: No such DSL method 'scanForIssues' found among steps

2018-10-30 Thread deanwarrenuk

Ok found it here
https://updates.jenkins.io/experimental/latest/

On Monday, 29 October 2018 16:28:31 UTC, Ullrich Hafner wrote:

> You need to point your update center to the experimental update center 
> url, see 
> https://jenkins.io/doc/developer/publishing/releasing-experimental-updates/
>
> Von meinem iPad gesendet
>
> Am 29.10.2018 um 15:43 schrieb dean warren  >:
>
> Thanks @sagar for your reply.
>
> But the link https://updates.jenkins.io/download/plugins/warnings/ does 
> not contain version 5.0. Perhaps because this is a beta?
>
> So do I have to build / repackage it, of is there another link that will 
> give me the .hpi file?
>
> On Mon, Oct 29, 2018 at 2:22 PM sagar utekar  > wrote:
>
>> from here you can download hpi file for warnings plugin 
>> https://updates.jenkins.io/download/plugins/warnings/
>>
>> and add it using upload section of manage plugin -> advanced section
>>
>> On Mon, Oct 29, 2018 at 7:39 PM def > 
>> wrote:
>>
>>> OK, from here:
>>> https://github.com/jenkinsci/warnings-plugin/tree/5.0
>>>
>>> But Jnekins requires a .*hpi* file.
>>> Do I have to build this, or package it somehow?
>>>
>>> On Monday, 29 October 2018 14:02:45 UTC, def wrote:
>>>
 Thanks @ulli for your reply.

 *'Did you install the 5.0 beta version of the plugin? This step is not 
 available in the 4.x version.*'
 Ahh... :) No. Where do I get that from and how to install in Jenkins?

 On Sat, Oct 27, 2018 at 6:07 PM Ulli Hafner >>> > wrote:

>
>
> Von meinem iPad gesendet
>
> Am 26.10.2018 um 09:50 schrieb dean warren  >:
>
> I am trying to get the Warnings plugin collecting CheckStyle results 
> within a pipeline.
>
> I believe I am using all the latest versions of pipeline related 
> modules, and the warnings modules.
>
>  
>
> A simplified version of my Jenkinsfile is something like:
>
> timestamps {
> node ('name') {
> try
> {
> stage ('Checkout') {
> checkout scm
> }
> stage ('Build & Test') {
> sh 'bash -x test.sh'
> }
> stage ('CheckStyle') {
> sh 'java -jar 
> /home/user/checkstyle/checkstyle-6.5-all.jar -c /home/user/checkstyle.xml 
> -f xml -c target/checkstyle-results.xml src'
> // Doesn't work
> //step([$class: 'CheckStylePublisher',
> //canRunOnFailed: true,
> //defaultEncoding: '',
> //healthy: '100',
> //pattern: '**/target/checkstyle-result.xml',
> //unHealthy: '90',
> //useStableBuildAsReference: true
> //])
>
>
> This publisher requires the CheckStyle plugin.
>
> // Doesn't work
> //step([$class: 'WarningsPublisher', 
> consoleParsers: [[parserName: 'CheckStyle']]])
> 
>
>
> The warnings publisher from the 4.x version does not support 
> CheckStyle yet.
>  
>
> // Doesn't work
> def checkstyle = scanForIssues tool: [$class: 
> 'CheckStyle'], pattern: '**/target/checkstyle-result.xml'
> publishIssues issues:[checkstyle]
> }
> }
> catch (caughtErr)
> {
> }
> finally
> {
> }
> }
> }
>
>
> Did you install the 5.0 beta version of the plugin? This step is not 
> available in the 4.x version.
>
> Where I have tried three different methods to collect the checkstype 
> results, none of which work (I have left two of them commented out for 
> reference - but beleive these are methods for the legacy checkstyle 
> plugin, 
> not the newly integrated warnigns plugin?).
>
>
> I believe the last method using scanForIssues is the correct method as 
> per here:
>
>
> https://github.com/jenkinsci/warnings-plugin/blob/master/Jenkinsfile.local
>
>  
>
> However on build, I see the checkstyle results being generated, but 
> get the following error message
> java.lang.NoSuchMethodError: No such DSL method 'scanForIssues' found 
> among steps
>
> Any ideas?
> Thanks in advance!
>
>
> -- 
> 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-use...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-users/00750112-2e37-4213-91b3-01c87686433c%40googlegroups.co

Re: java.lang.NoSuchMethodError: No such DSL method 'scanForIssues' found among steps

2018-10-30 Thread dean warren

Awesome, that works! Thanks guys.

One last question... :) Where can I find info for the 'pattern' part of the
line
e.g.
def checkstyle = scanForIssues tool: [$class: 'CheckStyle'], pattern:
'**/target/checkstyle-result.xml'


As my resutls are created in the dersired place (I can see them), but
scanForIssues isn't finding the checkstyle-results.xml (I think)
i.e.
[CheckStyle] [ERROR] No files found for pattern
'**/target/checkstyle-result.xml'. Configuration error?


On Tue, Oct 30, 2018 at 9:48 AM deanwarrenuk 
wrote:

> Ok found it here
> https://updates.jenkins.io/experimental/latest/
>
> On Monday, 29 October 2018 16:28:31 UTC, Ullrich Hafner wrote:
>
>> You need to point your update center to the experimental update center
>> url, see
>> https://jenkins.io/doc/developer/publishing/releasing-experimental-updates/
>>
>> Von meinem iPad gesendet
>>
>> Am 29.10.2018 um 15:43 schrieb dean warren :
>>
>> Thanks @sagar for your reply.
>>
>> But the link https://updates.jenkins.io/download/plugins/warnings/ does
>> not contain version 5.0. Perhaps because this is a beta?
>>
>> So do I have to build / repackage it, of is there another link that will
>> give me the .hpi file?
>>
>> On Mon, Oct 29, 2018 at 2:22 PM sagar utekar 
>> wrote:
>>
>>> from here you can download hpi file for warnings plugin
>>> https://updates.jenkins.io/download/plugins/warnings/
>>>
>>> and add it using upload section of manage plugin -> advanced section
>>>
>>> On Mon, Oct 29, 2018 at 7:39 PM def  wrote:
>>>
 OK, from here:
 https://github.com/jenkinsci/warnings-plugin/tree/5.0

 But Jnekins requires a .*hpi* file.
 Do I have to build this, or package it somehow?

 On Monday, 29 October 2018 14:02:45 UTC, def wrote:

> Thanks @ulli for your reply.
>
> *'Did you install the 5.0 beta version of the plugin? This step is not
> available in the 4.x version.*'
> Ahh... :) No. Where do I get that from and how to install in Jenkins?
>
> On Sat, Oct 27, 2018 at 6:07 PM Ulli Hafner 
> wrote:
>
>>
>>
>> Von meinem iPad gesendet
>>
>> Am 26.10.2018 um 09:50 schrieb dean warren :
>>
>> I am trying to get the Warnings plugin collecting CheckStyle results
>> within a pipeline.
>>
>> I believe I am using all the latest versions of pipeline related
>> modules, and the warnings modules.
>>
>>
>>
>> A simplified version of my Jenkinsfile is something like:
>>
>> timestamps {
>> node ('name') {
>> try
>> {
>> stage ('Checkout') {
>> checkout scm
>> }
>> stage ('Build & Test') {
>> sh 'bash -x test.sh'
>> }
>> stage ('CheckStyle') {
>> sh 'java -jar
>> /home/user/checkstyle/checkstyle-6.5-all.jar -c /home/user/checkstyle.xml
>> -f xml -c target/checkstyle-results.xml src'
>> // Doesn't work
>> //step([$class: 'CheckStylePublisher',
>> //canRunOnFailed: true,
>> //defaultEncoding: '',
>> //healthy: '100',
>> //pattern: '**/target/checkstyle-result.xml',
>> //unHealthy: '90',
>> //useStableBuildAsReference: true
>> //])
>>
>>
>> This publisher requires the CheckStyle plugin.
>>
>> // Doesn't work
>> //step([$class: 'WarningsPublisher',
>> consoleParsers: [[parserName: 'CheckStyle']]])
>>
>>
>>
>> The warnings publisher from the 4.x version does not support
>> CheckStyle yet.
>>
>>
>> // Doesn't work
>> def checkstyle = scanForIssues tool: [$class:
>> 'CheckStyle'], pattern: '**/target/checkstyle-result.xml'
>> publishIssues issues:[checkstyle]
>> }
>> }
>> catch (caughtErr)
>> {
>> }
>> finally
>> {
>> }
>> }
>> }
>>
>>
>> Did you install the 5.0 beta version of the plugin? This step is not
>> available in the 4.x version.
>>
>> Where I have tried three different methods to collect the checkstype
>> results, none of which work (I have left two of them commented out for
>> reference - but beleive these are methods for the legacy checkstyle 
>> plugin,
>> not the newly integrated warnigns plugin?).
>>
>>
>> I believe the last method using scanForIssues is the correct method
>> as per here:
>>
>>
>> https://github.com/jenkinsci/warnings-plugin/blob/master/Jenkinsfile.local
>>
>>
>>

Re: java.lang.NoSuchMethodError: No such DSL method 'scanForIssues' found among steps

2018-10-30 Thread Ullrich Hafner

You should see an info message in the snippet generator. The default (if left 
empty) is '**/checkstyle-result.xml‘. Or you can view the JavaDoc documentation 
(or documentation in 
https://github.com/jenkinsci/warnings-ng-plugin/blob/master/doc/Documentation.md).

Is your file called checkstyle-result.xml or checkstyle-result*s*.xml?

> Am 30.10.2018 um 11:48 schrieb dean warren :
> 
> Awesome, that works! Thanks guys.
> 
> One last question... :) Where can I find info for the 'pattern' part of the 
> line
> e.g.
> def checkstyle = scanForIssues tool: [$class: 'CheckStyle'], pattern: 
> '**/target/checkstyle-result.xml' 
> 
> 
> As my resutls are created in the dersired place (I can see them), but 
> scanForIssues isn't finding the checkstyle-results.xml (I think)
> i.e.
> [CheckStyle] [ERROR] No files found for pattern 
> '**/target/checkstyle-result.xml'. Configuration error?
> 
> 
> On Tue, Oct 30, 2018 at 9:48 AM deanwarrenuk  > wrote:
> Ok found it here
> https://updates.jenkins.io/experimental/latest/ 
> 
> 
> On Monday, 29 October 2018 16:28:31 UTC, Ullrich Hafner wrote:
> You need to point your update center to the experimental update center url, 
> see 
> https://jenkins.io/doc/developer/publishing/releasing-experimental-updates/ 
> 
> 
> Von meinem iPad gesendet
> 
> Am 29.10.2018 um 15:43 schrieb dean warren >:
> 
>> Thanks @sagar for your reply.
>> 
>> But the link https://updates.jenkins.io/download/plugins/warnings/ 
>>  does not contain 
>> version 5.0. Perhaps because this is a beta?
>> 
>> So do I have to build / repackage it, of is there another link that will 
>> give me the .hpi file?
>> 
>> On Mon, Oct 29, 2018 at 2:22 PM sagar utekar > wrote:
>> from here you can download hpi file for warnings plugin
>> https://updates.jenkins.io/download/plugins/warnings/ 
>> 
>> 
>> and add it using upload section of manage plugin -> advanced section
>> 
>> On Mon, Oct 29, 2018 at 7:39 PM def > wrote:
>> OK, from here:
>> https://github.com/jenkinsci/warnings-plugin/tree/5.0 
>> 
>> 
>> But Jnekins requires a .hpi file.
>> Do I have to build this, or package it somehow?
>> 
>> On Monday, 29 October 2018 14:02:45 UTC, def wrote:
>> Thanks @ulli for your reply.
>> 
>> 'Did you install the 5.0 beta version of the plugin? This step is not 
>> available in the 4.x version.'
>> Ahh... :) No. Where do I get that from and how to install in Jenkins?
>> 
>> On Sat, Oct 27, 2018 at 6:07 PM Ulli Hafner > wrote:
>> 
>> 
>> Von meinem iPad gesendet
>> 
>> Am 26.10.2018 um 09:50 schrieb dean warren >:
>> 
>>> I am trying to get the Warnings plugin collecting CheckStyle results within 
>>> a pipeline.
>>> I believe I am using all the latest versions of pipeline related modules, 
>>> and the warnings modules.
>>> 
>>> A simplified version of my Jenkinsfile is something like:
>>> 
>>> timestamps {
>>> node ('name') {
>>> try
>>> {
>>> stage ('Checkout') {
>>> checkout scm
>>> }
>>> stage ('Build & Test') {
>>> sh 'bash -x test.sh'
>>> }
>>> stage ('CheckStyle') {
>>> sh 'java -jar 
>>> /home/user/checkstyle/checkstyle-6.5-all.jar -c /home/user/checkstyle.xml 
>>> -f xml -c target/checkstyle-results.xml src'
>>> // Doesn't work
>>> //step([$class: 'CheckStylePublisher',
>>> //canRunOnFailed: true,
>>> //defaultEncoding: '',
>>> //healthy: '100',
>>> //pattern: '**/target/checkstyle-result.xml',
>>> //unHealthy: '90',
>>> //useStableBuildAsReference: true
>>> //])
>> 
>> This publisher requires the CheckStyle plugin.
>> 
>>> // Doesn't work
>>> //step([$class: 'WarningsPublisher', consoleParsers: 
>>> [[parserName: 'CheckStyle']]])
>>> 
>> 
>> The warnings publisher from the 4.x version does not support CheckStyle yet.
>> 
>>> // Doesn't work
>>> def checkstyle = scanForIssues tool: [$class: 
>>> 'CheckStyle'], pattern: '**/target/checkstyle-result.xml'
>>> publishIssues issues:[checkstyle]
>>> }
>>> }
>>> catch (caughtErr)
>>> {
>>> }
>>> finally
>>> {
>>> }
>>> }
>>> }
>>> 
>> 
>> Did you install the 5.0 beta version of the plugin? This step is not 
>> available in the 4.x version.
>> 
>>> Where I have tried three different m

jacoco report not found

2018-10-30 Thread Pradeep Drall

I am using SonarQube with scanner, jenkins, maven, gradle and wants to 
display code coverage report in SonarQube. 

I am getting error "Jacoco report not found"

[INFO] Sensor JaCoCoSensor [java]
[INFO] JaCoCo report not found: 'E:\pradeep 
doc\sonarQube\javaproject\cucumberba
sic\target\jacoco.exec'
[INFO] JaCoCo UT report not found: 'E:\pradeep 
doc\sonarQube\javaproject\cucumbe
rbasic\target/jacoco-ut.exec'
[INFO] JaCoCo IT report not found: 'E:\pradeep 
doc\sonarQube\javaproject\cucumbe
rbasic\target/jacoco-it.exec'

// pom.xml

jacoco
reuseReports
E:\pradeep 
doc\sonarQube\javaproject\cucumberbasic\target\jacoco.exec
java


I mentioned below details in sonar-project.properties
sonar.java.binaries=.
sonar.sourceEncoding=UTF-8
sonar.language=java
sonar.verbose=true
sonar.dynamicAnalysis=reuseReports
sonar.junit.reportsPath=target/surefire-reports
sonar.java.coveragePlugin=jacoco
sonar.jacoco.reportPath=target/jacoco.exec

Please do let me know how to resolve this issue and report. 

Regards,
Pradeep

-- 
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/02d1c8d7-64f4-4354-beb2-46f3c084f3d7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: java.lang.NoSuchMethodError: No such DSL method 'scanForIssues' found among steps

2018-10-30 Thread Ullrich Hafner

This looks like an exception from one of the steps. Is there a stacktrace? If 
there is no result visible then this is due to an exception.

> Am 30.10.2018 um 12:16 schrieb dean warren :
> 
> And also noted this for the same some, following emailing results
> 
> 10:58:11 Sending e-mails to: 
> [Pipeline] }
> [Pipeline] // node
> [Pipeline] }
> [Pipeline] // timestamps
> [Pipeline] End of Pipeline
> java.nio.charset.MalformedInputException: Input length = 1
> 
> 
> On Tue, Oct 30, 2018 at 11:15 AM dean warren  > wrote:
> 
> Ahh... I am clearly a doofus 's' !
> Sorry, you know what its like, doing one thing with left hand, something else 
> with other... and miss things.
> 
> So now I see the following
> 10:58:10 [CheckStyle] Searching for all files in 
> '/home/user/workspace/TG.integrate_jenkins_ci-TKKXRODLMWWUDKMVKENHFQYQ7E2ZP5QAC72HYNHV6PXXEX75DW2Q'
>  that match the pattern '**/target/checkstyle-results.xml'
> 10:58:10 [CheckStyle] -> found 1 file
> 10:58:10 [CheckStyle] Successfully parsed file 
> /home/user/workspace/TG.integrate_jenkins_ci-TKKXRODLMWWUDKMVKENHFQYQ7E2ZP5QAC72HYNHV6PXXEX75DW2Q/target/checkstyle-results.xml
> 10:58:10 [CheckStyle] -> found 2983 issues (skipped 0 duplicates)
> 
> However the build now fails,I assume because of all of the checkstyle issues 
> (all 2983 of them!) - this is fine.
> 
> But the checkstyle icon has dissapeared for this build.
> e.g. a good build, but not finding the checkstyle file, so no build failure 
> and the checkstyle icons appear but with no warnings/errors.
> 
> But on the failed build the icons have dissappeared.
> 
> How do I view the checkstyle warnings/errors in Jenksin?
> 
> On Tue, Oct 30, 2018 at 10:57 AM Ullrich Hafner  > wrote:
> You should see an info message in the snippet generator. The default (if left 
> empty) is '**/checkstyle-result.xml‘. Or you can view the JavaDoc 
> documentation (or documentation in 
> https://github.com/jenkinsci/warnings-ng-plugin/blob/master/doc/Documentation.md
>  
> ).
> 
> Is your file called checkstyle-result.xml or checkstyle-result*s*.xml?
> 
>> Am 30.10.2018 um 11:48 schrieb dean warren > >:
>> 
>> Awesome, that works! Thanks guys.
>> 
>> One last question... :) Where can I find info for the 'pattern' part of the 
>> line
>> e.g.
>> def checkstyle = scanForIssues tool: [$class: 'CheckStyle'], pattern: 
>> '**/target/checkstyle-result.xml' 
>> 
>> 
>> As my resutls are created in the dersired place (I can see them), but 
>> scanForIssues isn't finding the checkstyle-results.xml (I think)
>> i.e.
>> [CheckStyle] [ERROR] No files found for pattern 
>> '**/target/checkstyle-result.xml'. Configuration error?
>> 
>> 
>> On Tue, Oct 30, 2018 at 9:48 AM deanwarrenuk > > wrote:
>> Ok found it here
>> https://updates.jenkins.io/experimental/latest/ 
>> 
>> 
>> On Monday, 29 October 2018 16:28:31 UTC, Ullrich Hafner wrote:
>> You need to point your update center to the experimental update center url, 
>> see 
>> https://jenkins.io/doc/developer/publishing/releasing-experimental-updates/ 
>> 
>> 
>> Von meinem iPad gesendet
>> 
>> Am 29.10.2018 um 15:43 schrieb dean warren >:
>> 
>>> Thanks @sagar for your reply.
>>> 
>>> But the link https://updates.jenkins.io/download/plugins/warnings/ 
>>>  does not contain 
>>> version 5.0. Perhaps because this is a beta?
>>> 
>>> So do I have to build / repackage it, of is there another link that will 
>>> give me the .hpi file?
>>> 
>>> On Mon, Oct 29, 2018 at 2:22 PM sagar utekar > 
>>> wrote:
>>> from here you can download hpi file for warnings plugin
>>> https://updates.jenkins.io/download/plugins/warnings/ 
>>> 
>>> 
>>> and add it using upload section of manage plugin -> advanced section
>>> 
>>> On Mon, Oct 29, 2018 at 7:39 PM def > wrote:
>>> OK, from here:
>>> https://github.com/jenkinsci/warnings-plugin/tree/5.0 
>>> 
>>> 
>>> But Jnekins requires a .hpi file.
>>> Do I have to build this, or package it somehow?
>>> 
>>> On Monday, 29 October 2018 14:02:45 UTC, def wrote:
>>> Thanks @ulli for your reply.
>>> 
>>> 'Did you install the 5.0 beta version of the plugin? This step is not 
>>> available in the 4.x version.'
>>> Ahh... :) No. Where do I get that from and how to install in Jenkins?
>>> 
>>> On Sat, Oct 27, 2018 at 6:07 PM Ulli Hafner > wrote:
>>> 
>>> 
>>> Von meinem iPad gesendet
>>> 
>>> Am 26.10.2018 um 09:50 schrieb dean warren >:
>>> 
 I am trying to get the Warnings plugin collecting Check

Re: java.lang.NoSuchMethodError: No such DSL method 'scanForIssues' found among steps

2018-10-30 Thread dean warren

StackTrace:

java.nio.charset.MalformedInputException: Input length = 1
at java.nio.charset.CoderResult.throwException(CoderResult.java:281)
at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:339)
at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:178)
at java.io.InputStreamReader.read(InputStreamReader.java:184)
at java.io.BufferedReader.fill(BufferedReader.java:161)
at java.io.BufferedReader.readLine(BufferedReader.java:324)
at java.io.BufferedReader.readLine(BufferedReader.java:389)
at java.io.BufferedReader$1.hasNext(BufferedReader.java:571)
Also:   hudson.remoting.Channel$CallSiteStackTrace: Remote call to moftpa
at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1693)
at hudson.remoting.UserResponse.retrieve(UserRequest.java:310)
at hudson.remoting.Channel.call(Channel.java:908)
at hudson.FilePath.act(FilePath.java:986)
at hudson.FilePath.act(FilePath.java:975)
at
io.jenkins.plugins.analysis.core.steps.IssuesScanner.postProcess(IssuesScanner.java:148)
at
io.jenkins.plugins.analysis.core.steps.IssuesScanner.scanInWorkspace(IssuesScanner.java:92)
at
io.jenkins.plugins.analysis.core.steps.IssuesScanner.scan(IssuesScanner.java:71)
at
io.jenkins.plugins.analysis.core.steps.ScanForIssuesStep$Execution.run(ScanForIssuesStep.java:173)
at
io.jenkins.plugins.analysis.core.steps.ScanForIssuesStep$Execution.run(ScanForIssuesStep.java:138)
at
org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1$1.call(SynchronousNonBlockingStepExecution.java:50)
at hudson.security.ACL.impersonate(ACL.java:260)
at
org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1.run(SynchronousNonBlockingStepExecution.java:47)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused: java.io.UncheckedIOException
at java.io.BufferedReader$1.hasNext(BufferedReader.java:574)
at
java.util.Spliterators$IteratorSpliterator.tryAdvance(Spliterators.java:1811)
at java.util.Spliterators$1Adapter.hasNext(Spliterators.java:681)
at
edu.hm.hafner.analysis.FullTextFingerprint.extractContext(FullTextFingerprint.java:111)
at
edu.hm.hafner.analysis.FullTextFingerprint.createFingerprint(FullTextFingerprint.java:84)
at
edu.hm.hafner.analysis.FullTextFingerprint.compute(FullTextFingerprint.java:73)
at
edu.hm.hafner.analysis.FingerprintGenerator.run(FingerprintGenerator.java:35)
at
io.jenkins.plugins.analysis.core.steps.IssuesScanner$ReportPostProcessor.createFingerprints(IssuesScanner.java:237)
at
io.jenkins.plugins.analysis.core.steps.IssuesScanner$ReportPostProcessor.invoke(IssuesScanner.java:195)
at
io.jenkins.plugins.analysis.core.steps.IssuesScanner$ReportPostProcessor.invoke(IssuesScanner.java:170)
at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2760)
at hudson.remoting.UserRequest.perform(UserRequest.java:207)
at hudson.remoting.UserRequest.perform(UserRequest.java:53)
at hudson.remoting.Request$2.run(Request.java:358)
at
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Finished: FAILURE


On Tue, Oct 30, 2018 at 11:41 AM Ullrich Hafner 
wrote:

> This looks like an exception from one of the steps. Is there a stacktrace?
> If there is no result visible then this is due to an exception.
>
> Am 30.10.2018 um 12:16 schrieb dean warren :
>
> And also noted this for the same some, following emailing results
>
> *10:58:11* Sending e-mails to: 
> [Pipeline] }
> [Pipeline] // node
> [Pipeline] }
> [Pipeline] // timestamps
> [Pipeline] End of Pipeline
> java.nio.charset.MalformedInputException: Input length = 1
>
>
> On Tue, Oct 30, 2018 at 11:15 AM dean warren 
> wrote:
>
>>
>> Ahh... I am clearly a doofus 's' !
>> Sorry, you know what its like, doing one thing with left hand, something
>> else with other... and miss things.
>>
>> So now I see the following
>> *10:58:10* [CheckStyle] Searching for all files in
>> '/home/user/workspace/TG.integrate_jenkins_ci-TKKXRODLMWWUDKMVKENHFQYQ7E2ZP5QAC72HYNHV6PXXEX75DW2Q'
>> that match the pattern '**/target/checkstyle-results.xml'
>> *10:58:10* [CheckStyle] -> found 1 file
>> *10:58:10* [CheckStyle] Successfully parsed file /home/user
>> /workspace/TG.integrate_jenkins_ci-TKKXRODLMWWUDKMVKENHFQYQ7E2ZP5QAC72HYNHV6PXXEX75DW2Q/target/checkstyle-results.xml
>> *10:58:10* [CheckStyle] -> found 2983 issues (skipped 0 duplicates)
>>
>> However the build now fails,I assume because of all of the checkstyle
>> issues (all 2983 of them!) - this is fine.
>>
>> But the check

Re: java.lang.NoSuchMethodError: No such DSL method 'scanForIssues' found among steps

2018-10-30 Thread deanwarrenuk

Looks like this is def an issue with the line
def checkstyle = scanForIssues tool: [$class: 'CheckStyle'], pattern: 
'**/mof-api/target/checkstyle-results.xml'

As removed all steps except that above and issue still occurs.


Do you have a known working checkstyle-results.xml file, just in case 
somethink funny with mine?


On Tuesday, 30 October 2018 11:46:24 UTC, deanwarrenuk wrote:

> StackTrace:
>
> java.nio.charset.MalformedInputException: Input length = 1
> at java.nio.charset.CoderResult.throwException(CoderResult.java:281)
> at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:339)
> at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:178)
> at java.io.InputStreamReader.read(InputStreamReader.java:184)
> at java.io.BufferedReader.fill(BufferedReader.java:161)
> at java.io.BufferedReader.readLine(BufferedReader.java:324)
> at java.io.BufferedReader.readLine(BufferedReader.java:389)
> at java.io.BufferedReader$1.hasNext(BufferedReader.java:571)
> Also:   hudson.remoting.Channel$CallSiteStackTrace: Remote call to moftpa
> at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1693)
> at hudson.remoting.UserResponse.retrieve(UserRequest.java:310)
> at hudson.remoting.Channel.call(Channel.java:908)
> at hudson.FilePath.act(FilePath.java:986)
> at hudson.FilePath.act(FilePath.java:975)
> at 
> io.jenkins.plugins.analysis.core.steps.IssuesScanner.postProcess(IssuesScanner.java:148)
> at 
> io.jenkins.plugins.analysis.core.steps.IssuesScanner.scanInWorkspace(IssuesScanner.java:92)
> at 
> io.jenkins.plugins.analysis.core.steps.IssuesScanner.scan(IssuesScanner.java:71)
> at 
> io.jenkins.plugins.analysis.core.steps.ScanForIssuesStep$Execution.run(ScanForIssuesStep.java:173)
> at 
> io.jenkins.plugins.analysis.core.steps.ScanForIssuesStep$Execution.run(ScanForIssuesStep.java:138)
> at 
> org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1$1.call(SynchronousNonBlockingStepExecution.java:50)
> at hudson.security.ACL.impersonate(ACL.java:260)
> at 
> org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1.run(SynchronousNonBlockingStepExecution.java:47)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused: java.io.UncheckedIOException
> at java.io.BufferedReader$1.hasNext(BufferedReader.java:574)
> at 
> java.util.Spliterators$IteratorSpliterator.tryAdvance(Spliterators.java:1811)
> at java.util.Spliterators$1Adapter.hasNext(Spliterators.java:681)
> at 
> edu.hm.hafner.analysis.FullTextFingerprint.extractContext(FullTextFingerprint.java:111)
> at 
> edu.hm.hafner.analysis.FullTextFingerprint.createFingerprint(FullTextFingerprint.java:84)
> at 
> edu.hm.hafner.analysis.FullTextFingerprint.compute(FullTextFingerprint.java:73)
> at 
> edu.hm.hafner.analysis.FingerprintGenerator.run(FingerprintGenerator.java:35)
> at 
> io.jenkins.plugins.analysis.core.steps.IssuesScanner$ReportPostProcessor.createFingerprints(IssuesScanner.java:237)
> at 
> io.jenkins.plugins.analysis.core.steps.IssuesScanner$ReportPostProcessor.invoke(IssuesScanner.java:195)
> at 
> io.jenkins.plugins.analysis.core.steps.IssuesScanner$ReportPostProcessor.invoke(IssuesScanner.java:170)
> at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2760)
> at hudson.remoting.UserRequest.perform(UserRequest.java:207)
> at hudson.remoting.UserRequest.perform(UserRequest.java:53)
> at hudson.remoting.Request$2.run(Request.java:358)
> at 
> hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Finished: FAILURE
>
>
> On Tue, Oct 30, 2018 at 11:41 AM Ullrich Hafner  
> wrote:
>
>> This looks like an exception from one of the steps. Is there a 
>> stacktrace? If there is no result visible then this is due to an exception.
>>
>> Am 30.10.2018 um 12:16 schrieb dean warren :
>>
>> And also noted this for the same some, following emailing results
>>
>> *10:58:11* Sending e-mails to: 
>> [Pipeline] }
>> [Pipeline] // node
>> [Pipeline] }
>> [Pipeline] // timestamps
>> [Pipeline] End of Pipeline
>> java.nio.charset.MalformedInputException: Input length = 1
>>
>>
>> On Tue, Oct 30, 2018 at 11:15 AM dean warren  
>> wrote:
>>
>>>
>>> Ahh... I am clearly a doofus 's' !
>>> Sorry, you know what its like, doing one thing with left hand, something 
>>> else with other... and miss things.
>>>
>>> So now I see the following
>>> *10:58:10* [CheckStyle] Searching for all files in 
>>> '/home/user

Re: java.lang.NoSuchMethodError: No such DSL method 'scanForIssues' found among steps

2018-10-30 Thread deanwarrenuk

Have reduced the check-style from 200+ issues to just two. Works fine now.

So something incompatible with checkstyle-resutls.xml generated and the 
scanForIssues.
@Ullrich, can I send you the checkstyle-resutls.xml to debug (email? would 
prefer not to post file directly here)?

Or perhpas advise on how I can progress?


On Tuesday, 30 October 2018 12:16:41 UTC, deanwarrenuk wrote:

> Looks like this is def an issue with the line
> def checkstyle = scanForIssues tool: [$class: 'CheckStyle'], pattern: 
> '**/mof-api/target/checkstyle-results.xml'
>
> As removed all steps except that above and issue still occurs.
>
>
> Do you have a known working checkstyle-results.xml file, just in case 
> somethink funny with mine?
>
>
> On Tuesday, 30 October 2018 11:46:24 UTC, deanwarrenuk wrote:
>
>> StackTrace:
>>
>> java.nio.charset.MalformedInputException: Input length = 1
>> at java.nio.charset.CoderResult.throwException(CoderResult.java:281)
>> at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:339)
>> at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:178)
>> at java.io.InputStreamReader.read(InputStreamReader.java:184)
>> at java.io.BufferedReader.fill(BufferedReader.java:161)
>> at java.io.BufferedReader.readLine(BufferedReader.java:324)
>> at java.io.BufferedReader.readLine(BufferedReader.java:389)
>> at java.io.BufferedReader$1.hasNext(BufferedReader.java:571)
>> Also:   hudson.remoting.Channel$CallSiteStackTrace: Remote call to moftpa
>> at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1693)
>> at hudson.remoting.UserResponse.retrieve(UserRequest.java:310)
>> at hudson.remoting.Channel.call(Channel.java:908)
>> at hudson.FilePath.act(FilePath.java:986)
>> at hudson.FilePath.act(FilePath.java:975)
>> at 
>> io.jenkins.plugins.analysis.core.steps.IssuesScanner.postProcess(IssuesScanner.java:148)
>> at 
>> io.jenkins.plugins.analysis.core.steps.IssuesScanner.scanInWorkspace(IssuesScanner.java:92)
>> at 
>> io.jenkins.plugins.analysis.core.steps.IssuesScanner.scan(IssuesScanner.java:71)
>> at 
>> io.jenkins.plugins.analysis.core.steps.ScanForIssuesStep$Execution.run(ScanForIssuesStep.java:173)
>> at 
>> io.jenkins.plugins.analysis.core.steps.ScanForIssuesStep$Execution.run(ScanForIssuesStep.java:138)
>> at 
>> org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1$1.call(SynchronousNonBlockingStepExecution.java:50)
>> at hudson.security.ACL.impersonate(ACL.java:260)
>> at 
>> org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1.run(SynchronousNonBlockingStepExecution.java:47)
>> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>> at 
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>> at 
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>> at java.lang.Thread.run(Thread.java:745)
>> Caused: java.io.UncheckedIOException
>> at java.io.BufferedReader$1.hasNext(BufferedReader.java:574)
>> at 
>> java.util.Spliterators$IteratorSpliterator.tryAdvance(Spliterators.java:1811)
>> at java.util.Spliterators$1Adapter.hasNext(Spliterators.java:681)
>> at 
>> edu.hm.hafner.analysis.FullTextFingerprint.extractContext(FullTextFingerprint.java:111)
>> at 
>> edu.hm.hafner.analysis.FullTextFingerprint.createFingerprint(FullTextFingerprint.java:84)
>> at 
>> edu.hm.hafner.analysis.FullTextFingerprint.compute(FullTextFingerprint.java:73)
>> at 
>> edu.hm.hafner.analysis.FingerprintGenerator.run(FingerprintGenerator.java:35)
>> at 
>> io.jenkins.plugins.analysis.core.steps.IssuesScanner$ReportPostProcessor.createFingerprints(IssuesScanner.java:237)
>> at 
>> io.jenkins.plugins.analysis.core.steps.IssuesScanner$ReportPostProcessor.invoke(IssuesScanner.java:195)
>> at 
>> io.jenkins.plugins.analysis.core.steps.IssuesScanner$ReportPostProcessor.invoke(IssuesScanner.java:170)
>> at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2760)
>> at hudson.remoting.UserRequest.perform(UserRequest.java:207)
>> at hudson.remoting.UserRequest.perform(UserRequest.java:53)
>> at hudson.remoting.Request$2.run(Request.java:358)
>> at 
>> hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
>> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>> at 
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>> at 
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>> at java.lang.Thread.run(Thread.java:748)
>> Finished: FAILURE
>>
>>
>> On Tue, Oct 30, 2018 at 11:41 AM Ullrich Hafner  
>> wrote:
>>
>>> This looks like an exception from one of the steps. Is there a 
>>> stacktrace? If there is no result visible then this is due to an exception.
>>>
>>> Am 30.10.2018 um 12:16 schrieb dean warren :
>>>
>>> And also noted this for the same some, following emailing results
>>>
>>> *10:58:11* Sending e-mails to: 
>>> [Pipeline] }
>>

Ansible for administering Jenkins

2018-10-30 Thread gotviseryon

Hi,

Can we administer Jenkins using Ansible scripts?  If so, any pointers or 
can I get some sample scripts?

-- 
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/8140e51d-3fd9-48bb-bd79-0e65587c0a88%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

RE: Ansible for administering Jenkins

2018-10-30 Thread Samuli Saarinen

Hi,

Would these help: 
https://galaxy.ansible.com/search?keywords=jenkins&order_by=-relevance&page_size=10

br,
Samuli

From: jenkinsci-users@googlegroups.com  On 
Behalf Of gotviser...@gmail.com
Sent: 30. lokakuutata 2018 15:53
To: Jenkins Users 
Subject: Ansible for administering Jenkins

Hi,

Can we administer Jenkins using Ansible scripts?  If so, any pointers or can I 
get some sample scripts?
--
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/8140e51d-3fd9-48bb-bd79-0e65587c0a88%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/HE1PR03MB1161CDF26F9F2895A49D17158BCC0%40HE1PR03MB1161.eurprd03.prod.outlook.com.
For more options, visit https://groups.google.com/d/optout.

Re: java.lang.NoSuchMethodError: No such DSL method 'scanForIssues' found among steps

2018-10-30 Thread Ullrich Hafner

Can you add the encoding property:

checkstyle = scanForIssues reportEncoding='YOUR-ENCODING‘, ...

and replace YOUR-ENCODING with the encoding that is defined in the xml line of 
your checkstyle results.xml file?

If this does not work, please create an issue in our issue tracker and attach 
the XML file. (Or if it is confidential you may also send it via email).


> Am 30.10.2018 um 13:47 schrieb deanwarrenuk :
> 
> Have reduced the check-style from 200+ issues to just two. Works fine now.
> 
> So something incompatible with checkstyle-resutls.xml generated and the 
> scanForIssues.
> @Ullrich, can I send you the checkstyle-resutls.xml to debug (email? would 
> prefer not to post file directly here)?
> 
> Or perhpas advise on how I can progress?
> 
> 
> On Tuesday, 30 October 2018 12:16:41 UTC, deanwarrenuk wrote:
> Looks like this is def an issue with the line
> def checkstyle = scanForIssues tool: [$class: 'CheckStyle'], pattern: 
> '**/mof-api/target/checkstyle-results.xml'
> 
> As removed all steps except that above and issue still occurs.
> 
> 
> Do you have a known working checkstyle-results.xml file, just in case 
> somethink funny with mine?
> 
> 
> On Tuesday, 30 October 2018 11:46:24 UTC, deanwarrenuk wrote:
> StackTrace:
> 
> java.nio.charset.MalformedInputException: Input length = 1
>   at java.nio.charset.CoderResult.throwException(CoderResult.java:281)
>   at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:339)
>   at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:178)
>   at java.io.InputStreamReader.read(InputStreamReader.java:184)
>   at java.io.BufferedReader.fill(BufferedReader.java:161)
>   at java.io.BufferedReader.readLine(BufferedReader.java:324)
>   at java.io.BufferedReader.readLine(BufferedReader.java:389)
>   at java.io.BufferedReader$1.hasNext(BufferedReader.java:571)
> Also:   hudson.remoting.Channel$CallSiteStackTrace: Remote call to moftpa
>   at 
> hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1693)
>   at hudson.remoting.UserResponse.retrieve(UserRequest.java:310)
>   at hudson.remoting.Channel.call(Channel.java:908)
>   at hudson.FilePath.act(FilePath.java:986)
>   at hudson.FilePath.act(FilePath.java:975)
>   at 
> io.jenkins.plugins.analysis.core.steps.IssuesScanner.postProcess(IssuesScanner.java:148)
>   at 
> io.jenkins.plugins.analysis.core.steps.IssuesScanner.scanInWorkspace(IssuesScanner.java:92)
>   at 
> io.jenkins.plugins.analysis.core.steps.IssuesScanner.scan(IssuesScanner.java:71)
>   at 
> io.jenkins.plugins.analysis.core.steps.ScanForIssuesStep$Execution.run(ScanForIssuesStep.java:173)
>   at 
> io.jenkins.plugins.analysis.core.steps.ScanForIssuesStep$Execution.run(ScanForIssuesStep.java:138)
>   at 
> org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1$1.call(SynchronousNonBlockingStepExecution.java:50)
>   at hudson.security.ACL.impersonate(ACL.java:260)
>   at 
> org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1.run(SynchronousNonBlockingStepExecution.java:47)
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)
> Caused: java.io.UncheckedIOException
>   at java.io.BufferedReader$1.hasNext(BufferedReader.java:574)
>   at 
> java.util.Spliterators$IteratorSpliterator.tryAdvance(Spliterators.java:1811)
>   at java.util.Spliterators$1Adapter.hasNext(Spliterators.java:681)
>   at 
> edu.hm.hafner.analysis.FullTextFingerprint.extractContext(FullTextFingerprint.java:111)
>   at 
> edu.hm.hafner.analysis.FullTextFingerprint.createFingerprint(FullTextFingerprint.java:84)
>   at 
> edu.hm.hafner.analysis.FullTextFingerprint.compute(FullTextFingerprint.java:73)
>   at 
> edu.hm.hafner.analysis.FingerprintGenerator.run(FingerprintGenerator.java:35)
>   at 
> io.jenkins.plugins.analysis.core.steps.IssuesScanner$ReportPostProcessor.createFingerprints(IssuesScanner.java:237)
>   at 
> io.jenkins.plugins.analysis.core.steps.IssuesScanner$ReportPostProcessor.invoke(IssuesScanner.java:195)
>   at 
> io.jenkins.plugins.analysis.core.steps.IssuesScanner$ReportPostProcessor.invoke(IssuesScanner.java:170)
>   at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2760)
>   at hudson.remoting.UserRequest.perform(UserRequest.java:207)
>   at hudson.remoting.UserRequest.perform(UserRequest.java:53)
>   at hudson.remoting.Request$2.run(Request.java:358)
>   at 
> hudson.remoting.InterceptingE

Re: java.lang.NoSuchMethodError: No such DSL method 'scanForIssues' found among steps

2018-10-30 Thread Ullrich Hafner

and one additional question: how is the checkstyle file created?

> Am 30.10.2018 um 15:30 schrieb Ullrich Hafner :
> 
> Can you add the encoding property:
> 
> checkstyle = scanForIssues reportEncoding='YOUR-ENCODING‘, ...
> 
> and replace YOUR-ENCODING with the encoding that is defined in the xml line 
> of your checkstyle results.xml file?
> 
> If this does not work, please create an issue in our issue tracker and attach 
> the XML file. (Or if it is confidential you may also send it via email).
> 
> 
>> Am 30.10.2018 um 13:47 schrieb deanwarrenuk > >:
>> 
>> Have reduced the check-style from 200+ issues to just two. Works fine now.
>> 
>> So something incompatible with checkstyle-resutls.xml generated and the 
>> scanForIssues.
>> @Ullrich, can I send you the checkstyle-resutls.xml to debug (email? would 
>> prefer not to post file directly here)?
>> 
>> Or perhpas advise on how I can progress?
>> 
>> 
>> On Tuesday, 30 October 2018 12:16:41 UTC, deanwarrenuk wrote:
>> Looks like this is def an issue with the line
>> def checkstyle = scanForIssues tool: [$class: 'CheckStyle'], pattern: 
>> '**/mof-api/target/checkstyle-results.xml'
>> 
>> As removed all steps except that above and issue still occurs.
>> 
>> 
>> Do you have a known working checkstyle-results.xml file, just in case 
>> somethink funny with mine?
>> 
>> 
>> On Tuesday, 30 October 2018 11:46:24 UTC, deanwarrenuk wrote:
>> StackTrace:
>> 
>> java.nio.charset.MalformedInputException: Input length = 1
>>  at java.nio.charset.CoderResult.throwException(CoderResult.java:281)
>>  at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:339)
>>  at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:178)
>>  at java.io.InputStreamReader.read(InputStreamReader.java:184)
>>  at java.io.BufferedReader.fill(BufferedReader.java:161)
>>  at java.io.BufferedReader.readLine(BufferedReader.java:324)
>>  at java.io.BufferedReader.readLine(BufferedReader.java:389)
>>  at java.io.BufferedReader$1.hasNext(BufferedReader.java:571)
>> Also:   hudson.remoting.Channel$CallSiteStackTrace: Remote call to moftpa
>>  at 
>> hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1693)
>>  at hudson.remoting.UserResponse.retrieve(UserRequest.java:310)
>>  at hudson.remoting.Channel.call(Channel.java:908)
>>  at hudson.FilePath.act(FilePath.java:986)
>>  at hudson.FilePath.act(FilePath.java:975)
>>  at 
>> io.jenkins.plugins.analysis.core.steps.IssuesScanner.postProcess(IssuesScanner.java:148)
>>  at 
>> io.jenkins.plugins.analysis.core.steps.IssuesScanner.scanInWorkspace(IssuesScanner.java:92)
>>  at 
>> io.jenkins.plugins.analysis.core.steps.IssuesScanner.scan(IssuesScanner.java:71)
>>  at 
>> io.jenkins.plugins.analysis.core.steps.ScanForIssuesStep$Execution.run(ScanForIssuesStep.java:173)
>>  at 
>> io.jenkins.plugins.analysis.core.steps.ScanForIssuesStep$Execution.run(ScanForIssuesStep.java:138)
>>  at 
>> org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1$1.call(SynchronousNonBlockingStepExecution.java:50)
>>  at hudson.security.ACL.impersonate(ACL.java:260)
>>  at 
>> org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1.run(SynchronousNonBlockingStepExecution.java:47)
>>  at 
>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>>  at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>>  at 
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>>  at 
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>>  at java.lang.Thread.run(Thread.java:745)
>> Caused: java.io.UncheckedIOException
>>  at java.io.BufferedReader$1.hasNext(BufferedReader.java:574)
>>  at 
>> java.util.Spliterators$IteratorSpliterator.tryAdvance(Spliterators.java:1811)
>>  at java.util.Spliterators$1Adapter.hasNext(Spliterators.java:681)
>>  at 
>> edu.hm.hafner.analysis.FullTextFingerprint.extractContext(FullTextFingerprint.java:111)
>>  at 
>> edu.hm.hafner.analysis.FullTextFingerprint.createFingerprint(FullTextFingerprint.java:84)
>>  at 
>> edu.hm.hafner.analysis.FullTextFingerprint.compute(FullTextFingerprint.java:73)
>>  at 
>> edu.hm.hafner.analysis.FingerprintGenerator.run(FingerprintGenerator.java:35)
>>  at 
>> io.jenkins.plugins.analysis.core.steps.IssuesScanner$ReportPostProcessor.createFingerprints(IssuesScanner.java:237)
>>  at 
>> io.jenkins.plugins.analysis.core.steps.IssuesScanner$ReportPostProcessor.invoke(IssuesScanner.java:195)
>>  at 
>> io.jenkins.plugins.analysis.core.steps.IssuesScanner$ReportPostProcessor.invoke(IssuesScanner.java:170)
>>  at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2760)
>>  at hu

Re: curl syntax to send and receive REST Service API response (xml) from jenkins

2018-10-30 Thread Martin d'Anjou

I wrote a proposal 

 
to create a plugin to wrap the jenkins-rest library 
 inside a jenkins plugin for Google 
Summer of Code 2019 (GSoC). This would eliminate the need to parse XML 
responses and deal with errors. It would make the pipeline scripts simpler. 
I would need someone to co-mentor this project. If you want to know more 
let me know. There are other projects 

 
too.

Martin


On Monday, October 29, 2018 at 9:02:30 PM UTC-4, panneerrselvam natarajan 
wrote:
>
> Hi Prasad,
>
> Thanks for your response.
>
> I am getting response using HTTP instead of HTTPS and stored in xml file.. 
> How do i read the xml file? 
> The new XmlParser().parseText() displayed some error
>
> Regards
> Panneer
>
>
>
> panneerrselvam natarajan wrote:
>
>> Hi All,
>>
>> I need to execute the test suite using jenkins pipeline, The test suites  
>> which has developed using pega (REST service API). Please do let me know 
>> syntax to get the xml based response.
>>
>> Regards
>> Panneer
>>
>>

-- 
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/56d13d7a-d7ee-4c44-a391-0c3bbeff3759%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Problem with Java 8 update 191?

2018-10-30 Thread James Fairweather

Is there some way for me to find out *why* Jenkins thought the default
named workspace was already in use?  Our scripts make assumptions about the
workspace location and if Jenkins appends something ("@2") to the name of
the folder it won't work.

On Tue, Oct 30, 2018 at 2:25 AM Mark Waite 
wrote:

> Those workspace names are not an indication of an incompatibility.  If
> Jenkins needs to allocate a workspace and it detects that the default named
> workspace is already in use, it will allocate a second workspace adjacent
> to the first, with a digit appended to the workspace name.
>
> Mark Waite
>
> On Mon, Oct 29, 2018 at 11:28 PM James Fairweather <
> james.fairweat...@blackbirdinteractive.com> wrote:
>
>> Today I installed the version of Java from 8 build 181 to 8 build 191 on
>> several build slaves.  After doing that, Jenkins started allocating a 2nd
>> workspace on the some of the build agents.  For example, instead of running
>> here:
>>
>> D:\projects\lion\main
>>
>> They were running here:
>>
>> D:\projects\lion\main@2
>>
>> Each build agent has been allocated a single executor.  We are running
>> Jenkins 2.138.2.  I rolled the version of Java on the non-working agents
>> back to Update 181 and the problem went away.
>>
>> Does anyone know if Java 8 Update 191 has some kind of incompatibility
>> problem with Jenkins?
>>
>> --
>> 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/CALg80NUJuzJ8nsMkTqwewuLn4UFvATinP0rvA%3DcMv_n-_WmPfg%40mail.gmail.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/CAO49JtEJaL1wyweKHmt-11-R2BbZ4ujy45hD1T-r6oc6uhz6BQ%40mail.gmail.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/CALg80NUAJKSanpr_50wPoEusVQn0LCvN_10C81rZ2EewzjzdjA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

RE: Problem with Java 8 update 191?

2018-10-30 Thread matthew.web...@diamond.ac.uk

>> Is there some way for me to find out *why* Jenkins thought the default named 
>> workspace was already in use?  Our scripts make assumptions about the 
>> workspace location and if Jenkins appends something ("@2") to the name of 
>> the folder it won't work.

It's very strange that Jenkins thought the workspace was in use, since you only 
have one executor on the agent. However, leaving that aside for the moment, why 
not use $WORKSPACE to get the name of the folder? Hard-coding the name is an 
anti-pattern that will be a problem if you ever want to use concurrent builds, 
or (I think) matrix builds.

-- 
This e-mail and any attachments may contain confidential, copyright and or 
privileged material, and are for the use of the intended addressee only. If you 
are not the intended addressee or an authorised recipient of the addressee 
please notify us of receipt by returning the e-mail and do not use, copy, 
retain, distribute or disclose the information in or attached to the e-mail.
Any opinions expressed within this e-mail are those of the individual and not 
necessarily of Diamond Light Source Ltd. 
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments 
are free from viruses and we cannot accept liability for any damage which you 
may sustain as a result of software viruses which may be transmitted in or with 
the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and 
Wales with its registered office at Diamond House, Harwell Science and 
Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom

-- 
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/790ba44d8a6e4fe7aa588abeff23e121%40Diamond.ac.uk.
For more options, visit https://groups.google.com/d/optout.

Re: Ansible for administering Jenkins

2018-10-30 Thread gotviseryon

Thanks for the link Samuli.  I found this link.  But, am looking for a 
playbook to maintain the groups created and authenticated through Manage 
and Assign Roles (Role based authorization strategy).

On Tuesday, October 30, 2018 at 10:17:29 AM UTC-4, Samuli Saarinen wrote:
>
> Hi,
>
>  
>
> Would these help: 
> https://galaxy.ansible.com/search?keywords=jenkins&order_by=-relevance&page_size=10
>
>  
>
> br, 
>
> Samuli
>
>  
>
> *From:* jenkins...@googlegroups.com  <
> jenkins...@googlegroups.com > *On Behalf Of *
> gotvi...@gmail.com 
> *Sent:* 30. lokakuutata 2018 15:53
> *To:* Jenkins Users >
> *Subject:* Ansible for administering Jenkins
>
>  
>
> Hi,
>
>
> Can we administer Jenkins using Ansible scripts?  If so, any pointers or 
> can I get some sample scripts?
>
> -- 
> 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-use...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-users/8140e51d-3fd9-48bb-bd79-0e65587c0a88%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/355a2e2f-8baa-4268-ac6c-d6936a84d1bf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Making the jenkins scm checkout smart

2018-10-30 Thread Ivan Fernandez Calvo

you need to take a look to multibranch pipelines and blueocean, i think it 
makes what you want
https://jenkins.io/projects/blueocean/
https://jenkins.io/doc/book/pipeline/multibranch/
https://jenkins.io/doc/tutorials/build-a-multibranch-pipeline-project/

-- 
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/37601fdb-8f44-4226-b91f-1e459150d33c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Problem with build step - Windows Batch Command

2018-10-30 Thread Jorge Nuñez

You have to looking in your Jenkins Job if you´r using any step for 
"windows" and change it to a "shell"

El miércoles, 20 de diciembre de 2017, 13:16:13 (UTC-3), vikash singh 
escribió:
>
> I am facing the same problem.
>>
>> Can you tell me how did you resolve it.?
> How can i change the workspace to run windows batch 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/93bffb42-4f94-4406-a518-65125b7f7bb9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Ansible for administering Jenkins

2018-10-30 Thread Victor Martinez

JCasC might be a good way of automating it
- https://wiki.jenkins.io/display/JENKINS/Configuration+as+Code+Plugin

There are some examples about configuring the Roles:
- 
https://github.com/jenkinsci/configuration-as-code-plugin/blob/master/integrations/src/test/resources/io/jenkins/plugins/casc/RoleStrategy1.yml
- 
https://github.com/jenkinsci/configuration-as-code-plugin/blob/master/integrations/src/test/resources/io/jenkins/plugins/casc/RoleStrategy2.yml

You can easily run the CLI, once installed the JCasC plugin to validate and 
apply the above configuration on the fly!
- /cli/command/apply-configuration
- /cli/command/check-configuration


And on the top of that if you'd like to use ansible you could write your 
own playbook/role to use it as wrapper

My 2 cents

-- 
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/06c58cbb-a7a9-46a4-ac33-c2cb832fcf6c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins Administration - Role-based Authorization Strategy - Manage & Assign Roles list really big

2018-10-30 Thread Victor Martinez

Already addressed in another thread:
- https://groups.google.com/d/msg/jenkinsci-users/uznqn8Y3NRw/ghn1gFROCgAJ

-- 
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/0f337d4d-3de7-4187-b0b9-f7cb2990a9c9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: jacoco report not found

2018-10-30 Thread Victor Martinez

No enough details to understand whether the issue is within the maven 
project (maybe missing the jacaco configuration), sonar or a 
misconfiguration within the Jenkins instance somehow, or even some 
environmental issue.

My first approach would be to run the mvn locally and ensure the jacoco 
reports are generated fine, then repeat the same steps using Jenkins and 
validate whether the configuration is exactly the same in both systems your 
local environment and the Jenkins one.

Cheers

-- 
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/e2167313-dfa7-4d04-8945-a14f4847612a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Problem with Java 8 update 191?

2018-10-30 Thread James Fairweather

Thanks for the suggestion of using $WORKSPACE, that's an improvement.  I
still don't know why Jenkins thought the primary workspace was in use but
since the problem has disappeared, I won't worry about it for now.

On Tue, Oct 30, 2018 at 10:09 AM matthew.web...@diamond.ac.uk <
matthew.web...@diamond.ac.uk> wrote:

> >> Is there some way for me to find out *why* Jenkins thought the default
> named workspace was already in use?  Our scripts make assumptions about the
> workspace location and if Jenkins appends something ("@2") to the name of
> the folder it won't work.
>
> It's very strange that Jenkins thought the workspace was in use, since you
> only have one executor on the agent. However, leaving that aside for the
> moment, why not use $WORKSPACE to get the name of the folder? Hard-coding
> the name is an anti-pattern that will be a problem if you ever want to use
> concurrent builds, or (I think) matrix builds.
>
> --
> This e-mail and any attachments may contain confidential, copyright and or
> privileged material, and are for the use of the intended addressee only. If
> you are not the intended addressee or an authorised recipient of the
> addressee please notify us of receipt by returning the e-mail and do not
> use, copy, retain, distribute or disclose the information in or attached to
> the e-mail.
> Any opinions expressed within this e-mail are those of the individual and
> not necessarily of Diamond Light Source Ltd.
> Diamond Light Source Ltd. cannot guarantee that this e-mail or any
> attachments are free from viruses and we cannot accept liability for any
> damage which you may sustain as a result of software viruses which may be
> transmitted in or with the message.
> Diamond Light Source Limited (company no. 4375679). Registered in England
> and Wales with its registered office at Diamond House, Harwell Science and
> Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
>
> --
> 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/790ba44d8a6e4fe7aa588abeff23e121%40Diamond.ac.uk
> .
> 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/CALg80NUNcUuP_sR7_ZfVrpNqnQgrywEZUrRtm49ivw%2BfV4LFbA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

RE: Jenkins Administration - Role-based Authorization Strategy - Manage & Assign Roles list really big

Re: Connecting Jenkins to GitHub

Re: Problem with Java 8 update 191?

Re: Making the jenkins scm checkout smart

Re: java.lang.NoSuchMethodError: No such DSL method 'scanForIssues' found among steps

Re: java.lang.NoSuchMethodError: No such DSL method 'scanForIssues' found among steps

Re: java.lang.NoSuchMethodError: No such DSL method 'scanForIssues' found among steps

jacoco report not found

Re: java.lang.NoSuchMethodError: No such DSL method 'scanForIssues' found among steps

Re: java.lang.NoSuchMethodError: No such DSL method 'scanForIssues' found among steps

Re: java.lang.NoSuchMethodError: No such DSL method 'scanForIssues' found among steps

Re: java.lang.NoSuchMethodError: No such DSL method 'scanForIssues' found among steps

Ansible for administering Jenkins

RE: Ansible for administering Jenkins

Re: java.lang.NoSuchMethodError: No such DSL method 'scanForIssues' found among steps

Re: java.lang.NoSuchMethodError: No such DSL method 'scanForIssues' found among steps

Re: curl syntax to send and receive REST Service API response (xml) from jenkins

Re: Problem with Java 8 update 191?

RE: Problem with Java 8 update 191?

Re: Ansible for administering Jenkins

Re: Making the jenkins scm checkout smart

Re: Problem with build step - Windows Batch Command

Re: Ansible for administering Jenkins

Re: Jenkins Administration - Role-based Authorization Strategy - Manage & Assign Roles list really big

Re: jacoco report not found

Re: Problem with Java 8 update 191?

26 matches

Site Navigation

Mail list logo

Footer information