[JIRA] (JENKINS-39511) Error with TFS Plugin with Jenkins

2016-11-04 Thread sipand...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Siddharth Pandey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39511  
 
 
  Error with TFS Plugin with Jenkins   
 

  
 
 
 
 

 
Change By: 
 Siddharth Pandey  
 
 
Priority: 
 Minor Blocker  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-37276) Path attributes can change values if reordered

2016-11-04 Thread vinc...@latombe.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Vincent Latombe updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37276  
 
 
  Path attributes can change values if reordered   
 

  
 
 
 
 

 
Change By: 
 Vincent Latombe  
 
 
Summary: 
 Path  atributes  attributes  can change values if reordered  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-33691) URLTrigger Plugin doesn't work in jenkins 2.0 alpha 3 when using job type Pipeline

2016-11-04 Thread jenkin...@daumiller.eu (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Dorian Daumiller commented on  JENKINS-33691  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: URLTrigger Plugin doesn't work in jenkins 2.0 alpha 3 when using job type Pipeline   
 

  
 
 
 
 

 
 Same error for Jenkins 2.7.4 with URLTrigger Plug-in 0.41  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-39514) Changes view lists extra files when using shallow clone

2016-11-04 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39514  
 
 
  Changes view lists extra files when using shallow clone   
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 
 
Assignee: 
 Mark Waite  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-39514) Changes view lists extra files when using shallow clone

2016-11-04 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite commented on  JENKINS-39514  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Changes view lists extra files when using shallow clone   
 

  
 
 
 
 

 
 Any chance that you're using a shallow clone depth of 1, and those 350 files were included in other commits since the last build? The recent changes display shows what has changed since the last commit to the repository. If the initial shallow clone included commit "C1", then there were commits "C2", "C3", and "C4" added, then you ran the job again, I would expect the shallow clone would attempt to copy "C4" but would compute the differences between "C1" and "C4" (thus showing more changes than were in the "C4" commit.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-38928) Apply button behaviour broken

2016-11-04 Thread vinc...@latombe.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Vincent Latombe commented on  JENKINS-38928  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Apply button behaviour broken   
 

  
 
 
 
 

 
 Released in 1.8  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-38928) Apply button behaviour broken

2016-11-04 Thread vinc...@latombe.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Vincent Latombe updated  JENKINS-38928  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38928  
 
 
  Apply button behaviour broken   
 

  
 
 
 
 

 
Change By: 
 Vincent Latombe  
 
 
Status: 
 In Review Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-38471) Git parameterized job always builds master

2016-11-04 Thread yahia.bi...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bilel Yahia commented on  JENKINS-38471  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Git parameterized job always builds master   
 

  
 
 
 
 

 
 I was having the same problem after plugins upgrade, and I had it fixed by changing the Git parameter in the downstream job to use the SHA1 commit Id (Revision), instead of the branch name.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-39456) Pipeline Flownodes Generate Many Instances of Identical Strings

2016-11-04 Thread svano...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sam Van Oort started work on  JENKINS-39456  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Sam Van Oort  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-39456) Pipeline Flownodes Generate Many Instances of Identical Strings

2016-11-04 Thread svano...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sam Van Oort updated  JENKINS-39456  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39456  
 
 
  Pipeline Flownodes Generate Many Instances of Identical Strings   
 

  
 
 
 
 

 
Change By: 
 Sam Van Oort  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-39456) Pipeline Flownodes Generate Many Instances of Identical Strings

2016-11-04 Thread svano...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sam Van Oort updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39456  
 
 
  Pipeline Flownodes Generate Many Instances of Identical Strings   
 

  
 
 
 
 

 
Change By: 
 Sam Van Oort  
 
 
Component/s: 
 workflow-support-plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-34973) RejectedAccessException thrown but no pending script approval added

2016-11-04 Thread tom.fenne...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tom FENNELLY commented on  JENKINS-34973  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: RejectedAccessException thrown but no pending script approval added   
 

  
 
 
 
 

 
 Yeah, seems like it should get registered immediately at the point of detection Vs throwing something that then needs to be caught by whatever does the registering.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-34973) RejectedAccessException thrown but no pending script approval added

2016-11-04 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-34973  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: RejectedAccessException thrown but no pending script approval added   
 

  
 
 
 
 

 
 So either SandboxContinuable.findRejectedAccessException is not working, or SandboxContinuable.run0 is not getting called as expected. Possibly I could just make ScriptApproval.accessRejected be automatic at the throw site rather than requiring integrators to catch and rethrow.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-39514) Changes view lists extra files when using shallow clone

2016-11-04 Thread bochenski.kuba+jenk...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jakub Bochenski created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39514  
 
 
  Changes view lists extra files when using shallow clone   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Mark Waite  
 
 
Components: 
 git-plugin  
 
 
Created: 
 2016/Nov/04 3:26 PM  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Jakub Bochenski  
 

  
 
 
 
 

 
 Doing a regular build triggered by a single commit I get something like this: 

SuccessChanges Summary 
 acme-24689 ignore failing test (details) 
Commit 22d966caa8f2f3e9cdb29776f745eda38d2aa99a by jbochenski 
acme-24689 ignore failing test 
The file was modified module/server/src_test/com/acme/metadata/helper/FileMetadataRestServiceHelperFuncTest.java
 however with shallow clone option turned on the changes view lists 350 files as added under this commit: 

SuccessChanges Summary 
 acme-24689 ignore failing test (details) 
Commit 22d966caa8f2f3e9cdb29776f745eda38d2aa99a by jbochenski 
acme-24689 ignore failing test 
The file was added module/common-audit/src/test/java/com/acme/audit/model/UserAuditReportCriteriaMapperUnitTest.java The file was added module/common_platform/src/com/acme/common/util/UriBuilders.java The file was added module/common_platform/src/com/acme/index/documenthandler/DocumentHandlerFactory.java [ ... ] 

[JIRA] (JENKINS-34973) RejectedAccessException thrown but no pending script approval added

2016-11-04 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-34973  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: RejectedAccessException thrown but no pending script approval added   
 

  
 
 
 
 

 
 Code changed in jenkins User: tfennelly Path: Jenkinsfile http://jenkins-ci.org/commit/blueocean-acceptance-test/540dc68522d2ceac177eae5141b8ad4fe564117f Log: Fix URLEncoder issue related to JENKINS-34973  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-34973) RejectedAccessException thrown but no pending script approval added

2016-11-04 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-34973  
 
 
  RejectedAccessException thrown but no pending script approval added   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Component/s: 
 script-security-plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-39514) Changes view lists extra files when using shallow clone

2016-11-04 Thread bochenski.kuba+jenk...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jakub Bochenski updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39514  
 
 
  Changes view lists extra files when using shallow clone   
 

  
 
 
 
 

 
Change By: 
 Jakub Bochenski  
 

  
 
 
 
 

 
 Doing a regular build triggered by a single commit I get something like this:{quote}SuccessChangesSummaryacme-24689 ignore failing test (details)Commit 22d966caa8f2f3e9cdb29776f745eda38d2aa99a by jbochenskiacme-24689 ignore failing testThe file was modified module/server/src_test/com/acme/metadata/helper/FileMetadataRestServiceHelperFuncTest.java{quote}however with shallow clone option turned on the changes view lists 350 files as added under this commit:{quote}SuccessChangesSummaryacme-24689 ignore failing test (details)Commit 22d966caa8f2f3e9cdb29776f745eda38d2aa99a by jbochenskiacme-24689 ignore failing testThe file was added module/common-audit/src/test/java/com/acme/audit/model/UserAuditReportCriteriaMapperUnitTest.javaThe file was added module/common_platform/src/com/acme/common/util/UriBuilders.javaThe file was added module/common_platform/src/com/acme/index/documenthandler/DocumentHandlerFactory.java[ ... ] {quote} I don't see how doing a shallow clone would prevent showing proper contents of the HEAD commit  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
   

[JIRA] (JENKINS-39513) Prompted to enable pull requests when they're already enabled

2016-11-04 Thread ty...@monkeypox.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 R. Tyler Croy created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39513  
 
 
  Prompted to enable pull requests when they're already enabled   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 pull-requests-enabled.png  
 
 
Components: 
 blueocean-plugin  
 
 
Created: 
 2016/Nov/04 3:23 PM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 R. Tyler Croy  
 

  
 
 
 
 

 
 Maybe you folks don't see this ever, but sometimes I get to PULL REQUEST ZERO (woot). Even if you have pull request integration enabled, having zero pull requests means you're prompted to enable pull requests by Blue Ocean. Derp.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
   

[JIRA] (JENKINS-39232) unable to start slave after installing version 2.27 on master + new 3.0 slave.jar on slave

2016-11-04 Thread afisc...@pcsoft.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alexander Fischer commented on  JENKINS-39232  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: unable to start slave after installing version 2.27 on master + new 3.0 slave.jar on slave   
 

  
 
 
 
 

 
 You are right, I have overread the detail-comments about the bug. So I will try the new version 2.28.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-38928) Apply button behaviour broken

2016-11-04 Thread vinc...@latombe.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Vincent Latombe updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38928  
 
 
  Apply button behaviour broken   
 

  
 
 
 
 

 
Change By: 
 Vincent Latombe  
 
 
Summary: 
 When save a job you lose the changes if someone is reading the job Apply button behaviour broken  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-34973) RejectedAccessException thrown but no pending script approval added

2016-11-04 Thread tom.fenne...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tom FENNELLY commented on  JENKINS-34973  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: RejectedAccessException thrown but no pending script approval added   
 

  
 
 
 
 

 
 So basically, it appears as though the RejectedAccessException must be thrown all the way out in order for the approval request to get registered.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-34973) RejectedAccessException thrown but no pending script approval added

2016-11-04 Thread tom.fenne...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tom FENNELLY commented on  JENKINS-34973  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: RejectedAccessException thrown but no pending script approval added   
 

  
 
 
 
 

 
 I have seen this too and in my case it was not added for script approval (to /scriptApproval) because the RejectedAccessException was getting swallowed in a try catch. So the following would result in URLEncoder.encode getting added for script approval in /scriptApproval 

 

node {
def encodedMessage = URLEncoder.encode('Hello World', 'UTF-8');
}
 

 But the following would not  

 

node {
try {
def encodedMessage = URLEncoder.encode('Hello World', 'UTF-8');
} catch(err) {
echo 'There was an error';
}
}
 

  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-39512) Blue Ocean should allow me to get to the GitHub link for a Pipeline

2016-11-04 Thread ty...@monkeypox.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 R. Tyler Croy created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39512  
 
 
  Blue Ocean should allow me to get to the GitHub link for a Pipeline   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 prs-on-the-land.png, prs-on-the-ocean.png  
 
 
Components: 
 blueocean-plugin  
 
 
Created: 
 2016/Nov/04 2:56 PM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 R. Tyler Croy  
 

  
 
 
 
 

 
 Pretty straight-forward. Every GitHub Organization Folder project I have, or for every Freestyle job where I have configured a "GitHub Repository" there is a useful link which takes you back to that pull request. This is especially useful when looking at an overview of a number of pull requests in the Blue Ocean view, otherwise I have to go back to classic or god forbid search on GitHub directly for the code behind the Pipeline run  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

[JIRA] (JENKINS-39338) Pipeline config "cog" to link to classic config screen

2016-11-04 Thread tom.fenne...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tom FENNELLY resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39338  
 
 
  Pipeline config "cog" to link to classic config screen   
 

  
 
 
 
 

 
Change By: 
 Tom FENNELLY  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-39511) Error with TFS Plugin with Jenkins

2016-11-04 Thread ty...@monkeypox.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 R. Tyler Croy assigned an issue to R. Tyler Croy  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39511  
 
 
  Error with TFS Plugin with Jenkins   
 

  
 
 
 
 

 
Change By: 
 R. Tyler Croy  
 
 
Assignee: 
 R. Tyler Croy  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-39232) unable to start slave after installing version 2.27 on master + new 3.0 slave.jar on slave

2016-11-04 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-39232  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: unable to start slave after installing version 2.27 on master + new 3.0 slave.jar on slave   
 

  
 
 
 
 

 
 Alexander Fischer There is a changelog in 2.28: "implementing other proxying and filtering Launcher implementations. Particular plugins may require setting up the jenkins.slaves.DefaultJnlpSlaveReceiver.disableStrictVerification system property in the master JVM to allow connecting agents." Are you looking for this fix? Or are you aware about the certificate?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-39476) Gatling report trends: add total duration

2016-11-04 Thread n.toubl...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nicolas Toublanc commented on  JENKINS-39476  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Gatling report trends: add total duration   
 

  
 
 
 
 

 
 Thanks, I created a discussion thread here: https://groups.google.com/forum/#!topic/gatling/E5BU8H2weTw  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-39511) Error with TFS Plugin with Jenkins

2016-11-04 Thread ty...@monkeypox.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 R. Tyler Croy moved an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39511  
 
 
  Error with TFS Plugin with Jenkins   
 

  
 
 
 
 

 
Change By: 
 R. Tyler Croy  
 
 
Project: 
 Infrastructure Jenkins  
 
 
Key: 
 INFRA JENKINS - 971 39511  
 
 
Workflow: 
 classic default workflow JNJira + In-Review  
 
 
Component/s: 
 tfs-plugin  
 
 
Component/s: 
 ci  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are 

[JIRA] (JENKINS-39511) Error with TFS Plugin with Jenkins

2016-11-04 Thread ty...@monkeypox.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 R. Tyler Croy assigned an issue to redsolo  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39511  
 
 
  Error with TFS Plugin with Jenkins   
 

  
 
 
 
 

 
Change By: 
 R. Tyler Croy  
 
 
Assignee: 
 R. Tyler Croy redsolo  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-39510) Need way to specify Git Tool when using Github Org Folder plugin

2016-11-04 Thread docw...@gerf.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Christian Höltje created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39510  
 
 
  Need way to specify Git Tool when using Github Org Folder plugin   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Kohsuke Kawaguchi  
 
 
Components: 
 github-organization-folder-plugin  
 
 
Created: 
 2016/Nov/04 2:36 PM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Christian Höltje  
 

  
 
 
 
 

 
 In order to work around the issue(s) in JENKINS-38179 I need to be able to use the JGit-with-apachehttps "Git Tool". But I cannot do this with checkout scm in a Jenkinsfile when using the GitHub Organization Folder plugin. Ideally, I could: 
 
Set a default in the Org Folder configuration itself. 
Override this via the checkout scm command. e.g. checkout scm, git_tool: "JGit with apachehttps" 
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

 

[JIRA] (JENKINS-39232) unable to start slave after installing version 2.27 on master + new 3.0 slave.jar on slave

2016-11-04 Thread afisc...@pcsoft.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alexander Fischer commented on  JENKINS-39232  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: unable to start slave after installing version 2.27 on master + new 3.0 slave.jar on slave   
 

  
 
 
 
 

 
 Oleg Nenashev: Will the bugfix be in the next regular version 2.29 (may be next week)? In the changelog for Release2.28 and the list of upcoming changes there is nothing said about this bug or bugfix.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-39505) JClouds plugin fails on Jenkins v2.28

2016-11-04 Thread bernd.fa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bernd Farka commented on  JENKINS-39505  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: JClouds plugin fails on Jenkins v2.28   
 

  
 
 
 
 

 
 The Version Form the Plugin page  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-39505) JClouds plugin fails on Jenkins v2.28

2016-11-04 Thread fr...@fritz-elfert.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Fritz Elfert commented on  JENKINS-39505  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: JClouds plugin fails on Jenkins v2.28   
 

  
 
 
 
 

 
 Which version of the jclouds plugin are you using? (From the plugins page or built from git).  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-26100) SCM steps should return revision state

2016-11-04 Thread jenkinsj...@marcuscobden.co.uk (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Marcus Cobden commented on  JENKINS-26100  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: SCM steps should return revision state   
 

  
 
 
 
 

 
 I'm seeing the issue where `checkout scm` results in different commits between the start/end of a build; I've made a separate bug with a reproduction example: https://issues.jenkins-ci.org/browse/JENKINS-39508  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-39509) TAP Plugin 2.0.1 fails to parse TAP stream

2016-11-04 Thread daniel.mic.spen...@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Spencer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39509  
 
 
  TAP Plugin 2.0.1 fails to parse TAP stream   
 

  
 
 
 
 

 
Change By: 
 Daniel Spencer  
 

  
 
 
 
 

 
 After upgrading the TAP plugin from version 1.24 to version 2.0.1, the plugin fails to parse some TAP streams with the error:org.tap4j.parser.ParserException: Error parsing TAP Stream: Missing TAP Plan. at org.tap4j.parser.Tap13Parser.parseTapStream(Tap13Parser.java:230) at org.tap4j.parser.Tap13Parser.parseFile(Tap13Parser.java:193) at org.tap4j.plugin.TapParser.parse(TapParser.java:167) at org.tap4j.plugin.TapPublisher.loadResults(TapPublisher.java:540) at org.tap4j.plugin.TapPublisher.performImpl(TapPublisher.java:412) at org.tap4j.plugin.TapPublisher.perform(TapPublisher.java:371) at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:78) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:720) at hudson.model.Build$BuildExecution.post2(Build.java:185) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:665) at hudson.model.Run.execute(Run.java:1766) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410)Caused by: org.tap4j.parser.ParserException: Missing TAP Plan. at org.tap4j.parser.Tap13Parser.onFinish(Tap13Parser.java:393) at org.tap4j.parser.Tap13Parser.parseTapStream(Tap13Parser.java:227) ... 15 moreI have since downgraded the plugin back to 1.24, and these same streams are now parsed correctly.The streams that were not parsed all contained special characters. An example of a stream that could not be parsed by the plugin is attached. I tested this stream in InstantTap, where it was parsed successfully.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 


[JIRA] (JENKINS-39508) Revision checked out by "checkout scm" can change if new commits happen during build

2016-11-04 Thread jenkinsj...@marcuscobden.co.uk (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Marcus Cobden created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39508  
 
 
  Revision checked out by "checkout scm" can change if new commits happen during build   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 workflow-scm-step-plugin  
 
 
Created: 
 2016/Nov/04 2:09 PM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Marcus Cobden  
 

  
 
 
 
 

 
 If new commits go into a repo after a build has started we find later stages running against a different commit to the earlier stages. We've been using checkout scm + stash/unstash to work around this I've made a test repo to demonstrate the issue: https://github.com/leth/jenkins-pipeline-scm-test  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
  

[JIRA] (JENKINS-39509) TAP Plugin 2.0.1 fails to parse TAP stream

2016-11-04 Thread daniel.mic.spen...@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Spencer created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39509  
 
 
  TAP Plugin 2.0.1 fails to parse TAP stream   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Bruno P. Kinoshita  
 
 
Attachments: 
 consistency.attributes.pl.tap  
 
 
Components: 
 tap-plugin  
 
 
Created: 
 2016/Nov/04 2:09 PM  
 
 
Environment: 
 Jenkins version: 2.7.3; TAP Plugin version 2.0.1  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Daniel Spencer  
 

  
 
 
 
 

 
 After upgrading the TAP plugin from version 1.24 to version 2.0.1, the plugin fails to parse some TAP streams with the error: org.tap4j.parser.ParserException: Error parsing TAP Stream: Missing TAP Plan. at org.tap4j.parser.Tap13Parser.parseTapStream(Tap13Parser.java:230) at org.tap4j.parser.Tap13Parser.parseFile(Tap13Parser.java:193) at org.tap4j.plugin.TapParser.parse(TapParser.java:167) at org.tap4j.plugin.TapPublisher.loadResults(TapPublisher.java:540) at org.tap4j.plugin.TapPublisher.performImpl(TapPublisher.java:412) at org.tap4j.plugin.TapPublisher.perform(TapPublisher.java:371) at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:78) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:720) at hudson.model.Build$BuildExecution.post2(Build.java:185) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:665) at hudson.model.Run.execute(Run.java:1766) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at 

[JIRA] (JENKINS-39476) Gatling report trends: add total duration

2016-11-04 Thread ccousse...@gatling.io (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Cédric Cousseran commented on  JENKINS-39476  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Gatling report trends: add total duration   
 

  
 
 
 
 

 
 Hello, If you want to discuss about the Gatling plugin, please use our mailing list, where we are more active: https://groups.google.com/forum/#!forum/gatling The plugin is open source, contributions are welcomed. In the meantime, there certainly exists a plugin which can display the duration of a build step.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-39492) slow configure page load

2016-11-04 Thread fabrice.ro...@neticoa.fr (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Fabrice Robin commented on  JENKINS-39492  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: slow configure page load   
 

  
 
 
 
 

 
 Very same problem here with Jenkins >2.19 Firefox and Chrome hang for 10/20 seconds when configuring a job with this plugin activated.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-39504) PmdPluginTest might fail due to plugins installation order

2016-11-04 Thread egutier...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Evaristo Gutierrez updated  JENKINS-39504  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39504  
 
 
  PmdPluginTest might fail due to plugins installation order   
 

  
 
 
 
 

 
Change By: 
 Evaristo Gutierrez  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-39504) PmdPluginTest might fail due to plugins installation order

2016-11-04 Thread egutier...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Evaristo Gutierrez updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39504  
 
 
  PmdPluginTest might fail due to plugins installation order   
 

  
 
 
 
 

 
Change By: 
 Evaristo Gutierrez  
 

  
 
 
 
 

 
 {{ should_set_warnings_count_in_dashboard_portlet }}  method might fail.dashboard-view plugin is needed to execute the test suite but it might happen that it is installed after pmd plugin is installed.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-39504) PmdPluginTest might fail due to plugins installation order

2016-11-04 Thread egutier...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Evaristo Gutierrez assigned an issue to Evaristo Gutierrez  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39504  
 
 
  PmdPluginTest might fail due to plugins installation order   
 

  
 
 
 
 

 
Change By: 
 Evaristo Gutierrez  
 
 
Assignee: 
 Oliver Gondža Evaristo Gutierrez  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-39504) PmdPluginTest might fail due to plugins installation order

2016-11-04 Thread egutier...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Evaristo Gutierrez started work on  JENKINS-39504  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Evaristo Gutierrez  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-39478) Select box / Dropdown component

2016-11-04 Thread cmey...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Cliff Meyers updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39478  
 
 
  Select box / Dropdown component   
 

  
 
 
 
 

 
Change By: 
 Cliff Meyers  
 

  
 
 
 
 

 
 *User Interactions*- Clicking toggles the open/closed state of the menu- Menu sizes to reasonable default height, scroll to handle large numbers of items- Menu must position itself to bottom-left corner of dropdown when open- Support keyboard accessibility (space-bar to open ; arrow up/down ,  page  up/down  arrow , home/end  keys to navigate through options, spacebar or enter to select, esc to dismiss , mousewheel )*Developer Options** Supply array of items for display* Allow for a default selection* Customize display of items with any text desired** Stretch goal: allow for custom React component to be used* Handlers for onChange  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an 

[JIRA] (JENKINS-39481) Possible race condition in {{ForemanSharedNodeCloud.provision(Label)}} during reservation

2016-11-04 Thread sco...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Scott Hebert commented on  JENKINS-39481  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Possible race condition in {{ForemanSharedNodeCloud.provision(Label)}} during reservation   
 

  
 
 
 
 

 
 In looking at https://github.com/david-caro/foreman_reserve/blob/master/app/controllers/api/v2/reserves_controller.rb#L29, it seems that a file lock is used to ensure that only 1 host can be reserved at a time. In addition, looking at https://github.com/david-caro/foreman_reserve/blob/master/app/controllers/api/v2/reserves_controller.rb#L30, another check is made to ensure that the host is free before reserving it. Hope that helps!  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-39333) Fix ATH triggered by PRs

2016-11-04 Thread tom.fenne...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tom FENNELLY resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39333  
 
 
  Fix ATH triggered by PRs   
 

  
 
 
 
 

 
Change By: 
 Tom FENNELLY  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-39333) Fix ATH triggered by PRs

2016-11-04 Thread tom.fenne...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tom FENNELLY commented on  JENKINS-39333  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Fix ATH triggered by PRs   
 

  
 
 
 
 

 
 Ok, I think I plugged some holes in the script to at least make this fail happen less frequently.One of the issues was the use of "/" in some of the branch names. That needs to be encoded or the copyartifacts fails. Encoding though is a bit of an issue because I can't seem to use the URLEncode class in the script (fails with script approval issues BUT the approval request is never added to /scriptApproval, so not able to enable it).  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-39333) Fix ATH triggered by PRs

2016-11-04 Thread tom.fenne...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tom FENNELLY stopped work on  JENKINS-39333  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Tom FENNELLY  
 
 
Status: 
 In Progress Open  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-39333) Fix ATH triggered by PRs

2016-11-04 Thread tom.fenne...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tom FENNELLY updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39333  
 
 
  Fix ATH triggered by PRs   
 

  
 
 
 
 

 
Change By: 
 Tom FENNELLY  
 
 
Attachment: 
 Screenshot 2016-11-04 13.33.29.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-37771) "Run the build in a RVM-managed environment" field gets unchecked after restarting the Jenkins server.

2016-11-04 Thread duffy...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 JP Duffy commented on  JENKINS-37771  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: "Run the build in a RVM-managed environment" field gets unchecked after restarting the Jenkins server.   
 

  
 
 
 
 

 
For me nothing in Build Environment sticks. I use Color ANSI, RVM, and SSH Agent and have to reset these at least once a day. On all my jobs... The Reload Configuration trick mentioned above doesn't work for me. Jenkins 2.19.2 ruby-runtime 0.13 rvm 0.6 AnsiColor 0.4.2 SSH Agent 1.13 Ubuntu 14.04LTS  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-39333) Fix ATH triggered by PRs

2016-11-04 Thread tom.fenne...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tom FENNELLY started work on  JENKINS-39333  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Tom FENNELLY  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-39507) Add a way to use a docker agent that creates the image like with the `docker.create()` function.

2016-11-04 Thread leandro.lucare...@sociomantic.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Leandro Lucarella created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39507  
 
 
  Add a way to use a docker agent that creates the image like with the `docker.create()` function.   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Andrew Bayer  
 
 
Components: 
 pipeline-model-definition-plugin  
 
 
Created: 
 2016/Nov/04 1:27 PM  
 
 
Priority: 
  Blocker  
 
 
Reporter: 
 Leandro Lucarella  
 

  
 
 
 
 

 
 Currently there is no way to create a docker container from an image that is specified by a Dockerfile in the repository. I guess there should be a syntax like: 

 
agent docker:create dockerFile:'Dockerfile' dockerDir:'.'
 

 Where dockerFile and dockerDir are optional and it defaults to just use the Dockerfile and usual.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 
 

[JIRA] (JENKINS-37771) "Run the build in a RVM-managed environment" field gets unchecked after restarting the Jenkins server.

2016-11-04 Thread duffy...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 JP Duffy updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37771  
 
 
  "Run the build in a RVM-managed environment" field gets unchecked after restarting the Jenkins server.   
 

  
 
 
 
 

 
Change By: 
 JP Duffy  
 
 
Attachment: 
 Screen Shot 2016-11-04 at 8.20.04 AM.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-38736) update guice to release version

2016-11-04 Thread gentoo.inte...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kanstantsin Shautsou updated  JENKINS-38736  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38736  
 
 
  update guice to release version   
 

  
 
 
 
 

 
Change By: 
 Kanstantsin Shautsou  
 
 
Status: 
 In Review Resolved  
 
 
Resolution: 
 Done  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-26940) No feedback why no installer was found for a given node

2016-11-04 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-26940  
 
 
  No feedback why no installer was found for a given node   
 

  
 
 
 
 

 
Change By: 
 Daniel Beck  
 
 
Summary: 
 JAVA_HOME is empty when No feedback why  no installer  is available  was found  for a  JDK  given node  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-26940) JAVA_HOME is empty when no installer is available for a JDK

2016-11-04 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-26940  
 
 
  JAVA_HOME is empty when no installer is available for a JDK   
 

  
 
 
 
 

 
Change By: 
 Daniel Beck  
 
 
Labels: 
 lts-candidate  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-26940) JAVA_HOME is empty when no installer is available for a JDK

2016-11-04 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck updated  JENKINS-26940  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 The main problem here is installers, and that got diagnostic messages, so considering this resolved.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-26940  
 
 
  JAVA_HOME is empty when no installer is available for a JDK   
 

  
 
 
 
 

 
Change By: 
 Daniel Beck  
 
 
Status: 
 In Review Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to 

[JIRA] (JENKINS-26940) JAVA_HOME is empty when no installer is available for a JDK

2016-11-04 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-26940  
 
 
  JAVA_HOME is empty when no installer is available for a JDK   
 

  
 
 
 
 

 
Change By: 
 Daniel Beck  
 
 
Issue Type: 
 Improvement Bug  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-38736) update guice to release version

2016-11-04 Thread bernd.fa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bernd Farka commented on  JENKINS-38736  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: update guice to release version   
 

  
 
 
 
 

 
 this update seems to broke the JClouds Plugin https://issues.jenkins-ci.org/browse/JENKINS-39505  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-39506) Freestyle multi-branch project has to long pathname

2016-11-04 Thread ris...@dsb.dk (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rik Svendsen Rose created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39506  
 
 
  Freestyle multi-branch project has to long pathname   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Max Spring  
 
 
Components: 
 jenkow-plugin  
 
 
Created: 
 2016/Nov/04 12:46 PM  
 
 
Environment: 
 Win7 - Client  
 
 
Priority: 
  Blocker  
 
 
Reporter: 
 Rik Svendsen Rose  
 

  
 
 
 
 

 
 The freestyle multi-branch project appears to have a serious issue. Or i am doing something wrong. For each branch, when building, It adds a huge ID to the folder it builds to. Why? E.g.: NUnit_AM_Develop-E6QXPCKKZO7VWBORRTTWLSEHXX47QH6G5QVMNRI7IGDH4AB2CMZQ. My branch name i AM_Develop and the config NUnit. Hence the MS Build gives me a: _The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters _ If the project name is longer then "NUnit" i get the error just in the GIT pull. How can i switch so the E6QXPCKKZO7VWBORRTTWLSEHXX47QH6G5QVMNRI7IGDH4AB2CMZQ is not present. And is it even needed?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
  

[JIRA] (JENKINS-39444) Spurious "You have no permission to build" errors with inconsistent effects.

2016-11-04 Thread scott.justa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Scott Justason commented on  JENKINS-39444  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Spurious "You have no permission to build" errors with inconsistent effects.   
 

  
 
 
 
 

 
 Yes, I forgot to mention this problem only manifested after we upgraded to 2.28 from an earlier version (I don't remember which but it's been at least 6 months since we've upgraded   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-39505) JClouds plugin fails on Jenkins v2.28

2016-11-04 Thread georg.brunm...@dynatrace.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Georg Brunmayr created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39505  
 
 
  JClouds plugin fails on Jenkins v2.28   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Fritz Elfert  
 
 
Components: 
 jclouds-plugin  
 
 
Created: 
 2016/Nov/04 12:41 PM  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Georg Brunmayr  
 

  
 
 
 
 

 
 We use the JClouds plugin to provision OpenNebula instances via aws-ec2 api Since update to 2.28 the connection fails. From the stack trace i guess this is related to JENKINS-38736 Cannot connect to specified cloud, please check the identity and credentials: Unable to create injector, see the following errors: 1) Overriding @Provides methods is not allowed. @Provides method: org.jclouds.logging.config.LoggingModule.createLoggerFactory() overridden by: jenkins.plugins.jclouds.compute.JCloudsCloud$1.createLoggerFactory() at com.google.inject.internal.ProviderMethodsModule.getProviderMethods(ProviderMethodsModule.java:163) 2) Overriding @Provides methods is not allowed. @Provides method: org.jclouds.compute.config.BaseComputeServiceContextModule.provideTemplateOptions() overridden by: org.jclouds.aws.ec2.compute.config.AWSEC2ComputeServiceContextModule.provideTemplateOptions() at com.google.inject.internal.ProviderMethodsModule.getProviderMethods(ProviderMethodsModule.java:163) 3) Overriding @Provides methods is not allowed. @Provides method: org.jclouds.compute.config.BaseComputeServiceContextModule.provideImageExtension() overridden by: org.jclouds.aws.ec2.compute.config.AWSEC2ComputeServiceContextModule.provideImageExtension() at com.google.inject.internal.ProviderMethodsModule.getProviderMethods(ProviderMethodsModule.java:163) 4) Overriding @Provides methods is not allowed. @Provides method: org.jclouds.compute.config.BaseComputeServiceContextModule.provideSecurityGroupExtension() overridden by: org.jclouds.aws.ec2.compute.config.AWSEC2ComputeServiceContextModule.provideSecurityGroupExtension() at com.google.inject.internal.ProviderMethodsModule.getProviderMethods(ProviderMethodsModule.java:163)  
 

[JIRA] (JENKINS-39504) PmdPluginTest might fail due to plugins installation order

2016-11-04 Thread egutier...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Evaristo Gutierrez created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39504  
 
 
  PmdPluginTest might fail due to plugins installation order   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Oliver Gondža  
 
 
Components: 
 acceptance-test-harness  
 
 
Created: 
 2016/Nov/04 12:31 PM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Evaristo Gutierrez  
 

  
 
 
 
 

 
 should_set_warnings_count_in_dashboard_portlet method might fail. dashboard-view plugin is needed to execute the test suite but it might happen that it is installed after pmd plugin is installed.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 

[JIRA] (JENKINS-37778) Pipeline Config: Getting env vars from Credentials

2016-11-04 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-37778  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipeline Config: Getting env vars from Credentials   
 

  
 
 
 
 

 
 Code changed in jenkins User: Robert Sandell Path: pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/steps/CredentialWrapperStepTest.java pipeline-model-definition/src/test/resources/credentials/mixedEnv.groovy http://jenkins-ci.org/commit/pipeline-model-definition-plugin/8b4885875aca43509f183a5e5972608b7387c119 Log: JENKINS-37778 more happy path testing  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-39502) ghprb couldn't pass the variable for triggerPhrase

2016-11-04 Thread m...@daniel-spilker.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Spilker resolved as Duplicate  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39502  
 
 
  ghprb couldn't pass the variable for triggerPhrase   
 

  
 
 
 
 

 
Change By: 
 Daniel Spilker  
 
 
Status: 
 Open Resolved  
 
 
Assignee: 
 ben patterson Daniel Spilker  
 
 
Resolution: 
 Duplicate  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-39482) GitHub commit status not working with GitHubCommitStatusSetter on first build of branch in multi-branch pipeline

2016-11-04 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev closed an issue as Won't Fix  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Please read docs for pipeline plugin. On first run there is no information about git (pipeline doesn't provide it)  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-39482  
 
 
  GitHub commit status not working with GitHubCommitStatusSetter on first build of branch in multi-branch pipeline   
 

  
 
 
 
 

 
Change By: 
 Kirill Merkushev  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Won't Fix  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 

[JIRA] (JENKINS-39477) Github Plugin with Two Factor Authentication (2FA)

2016-11-04 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev closed an issue as Won't Fix  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 2FA auth requires pin which can't be retrieved automatically. Nobody use 2FA and store all creds in jenkins, where u can fetch any creds with help of groovy console  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-39477  
 
 
  Github Plugin with Two Factor Authentication (2FA)   
 

  
 
 
 
 

 
Change By: 
 Kirill Merkushev  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Won't Fix  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving 

[JIRA] (JENKINS-39332) ApiSlRuntimeErrors.UnsafeCode error during analysis

2016-11-04 Thread ka...@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Yafim Kazak edited a comment on  JENKINS-39332  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: ApiSlRuntimeErrors.UnsafeCode error during analysis   
 

  
 
 
 
 

 
 Yes they seem fine.It seems that for some reason that analysis can't create a session from you LRR - did you succeed doing that manually with that LRR? Which windows version does the node use?What's the user Jenkins has been using? Can you please follow this instruction on our plugin page and change the setting of your jenkins user - it shouldn't be set on local system account - [https://wiki.jenkins-ci.org/display/JENKINS/HP+Application+Automation+Tools#HPApplicationAutomationTools-SlavesandTestingToolsInstallation]  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-39332) ApiSlRuntimeErrors.UnsafeCode error during analysis

2016-11-04 Thread ka...@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Yafim Kazak commented on  JENKINS-39332  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: ApiSlRuntimeErrors.UnsafeCode error during analysis   
 

  
 
 
 
 

 
 Yes they seem fine. It seems that for some reason that analysis can't create a session from you LRR - did you succeed doing that manually with that LRR?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-39413) Errors in LR Scenario set build status to UNSTABLE

2016-11-04 Thread ka...@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Yafim Kazak started work on  JENKINS-39413  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Yafim Kazak  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-28367) perforce plugin don't support P4 ticket authentication

2016-11-04 Thread ant....@tin.it (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 antonio bur edited a comment on  JENKINS-28367  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: perforce plugin don't support P4 ticket authentication   
 

  
 
 
 
 

 
 Hi,I have installed the Jenkins server  (2.28 ver)  using the perforce plug in 1.3.36, but I 'm  still get the following error. Note I sure that the password is right. Can you help  me  on this?[workspace] $ p4 -p ssl:myperforce:1666 trust -y[workspace] $ p4 login -a -p[workspace] $ p4 -P xx workspace -o -S //depot/abcd jenkins_workspaceCaught exception communicating with perforce. Perforce password (P4PASSWD) invalid or unset.com.tek42.perforce.PerforceException: Perforce password (P4PASSWD) invalid or unset.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-39503) Bitbucket pull request not approved when "Reset approvals" option is set

2016-11-04 Thread kar...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Karol Tyl created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39503  
 
 
  Bitbucket pull request not approved when "Reset approvals" option is set   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 bitbucket-pullrequest-builder-plugin  
 
 
Created: 
 2016/Nov/04 11:01 AM  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Karol Tyl  
 

  
 
 
 
 

 
 When the branch has set the option "Reset approvals when source branch is modified", the Jenkins approval is visible in Activity tab, but the pull request does not get approved. This is probably due to the fact, that in such case the approval must contain commit id of the source branch at the moment of approving, which probably is missing in Bitbucket Pull Request Builder Plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

   

[JIRA] (JENKINS-38533) Pull Requests checkout the wrong commit

2016-11-04 Thread alexander.ger...@bosch-si.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alexander Gerock commented on  JENKINS-38533  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pull Requests checkout the wrong commit   
 

  
 
 
 
 

 
 Stash Pull Request Builder Plugin uses Stash REST API to check for changes on pull requests: 
 
https:///stash/rest/api/1.0/projects//repos//pull-requests/ 
 If a new commit is present build job is started 
 
last revision is retrieved by 
 
git fetch --tags --progress  +refs/pull-requests/:refs/remotes/origin/pr/ 
git rev-parse refs/remotes/origin/pr//from^ {commit} 
  
 The problem is that after pushing a commit on a branch for wich a pull request exists these changes are retrieved immediately by REST API but refs are not updated so that build job checks out not the latest commit. The pull request (refs) is only updated if the following call is made: 
 
https:///stash/rest/api/latest/projects//repos//pull-requests//merge 
 This call is made if you open a pull request in stash web page. This is the official solution: 
 
https://answers.atlassian.com/questions/239988/change-pull-request-refs-after-commit-instead-of-after-approval-or-workaround 
 Workaround for Stash Pull Request Builder Plugin: 
 
Activate "Build only if PR is mergeable" of Stash Pull Requests Builder on Jenkins to enforce REST API call to .../merge 
 Possible solution: 
 
Always call https:///stash/rest/api/latest/projects//repos//pull-requests//merge if there are changes on https:///stash/rest/api/1.0/projects//repos//pull-requests/ 
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

   

[JIRA] (JENKINS-35219) Jenkins checks out previous commit when new commit added to Pull Request

2016-11-04 Thread alexander.ger...@bosch-si.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alexander Gerock commented on  JENKINS-35219  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins checks out previous commit when new commit added to Pull Request   
 

  
 
 
 
 

 
 Stash Pull Request Builder Plugin uses Stash REST API to check for changes on pull requests: 
 
https:///stash/rest/api/1.0/projects//repos//pull-requests/ 
 If a new commit is present build job is started 
 
last revision is retrieved by 
 
git fetch --tags --progress  +refs/pull-requests/:refs/remotes/origin/pr/ 
git rev-parse refs/remotes/origin/pr//from^ {commit} 
  
 The problem is that after pushing a commit on a branch for wich a pull request exists these changes are retrieved immediately by REST API but refs are not updated so that build job checks out not the latest commit. The pull request (refs) is only updated if the following call is made: 
 
https:///stash/rest/api/latest/projects//repos//pull-requests//merge 
 This call is made if you open a pull request in stash web page. This is the official solution: 
 
https://answers.atlassian.com/questions/239988/change-pull-request-refs-after-commit-instead-of-after-approval-or-workaround 
 Workaround for Stash Pull Request Builder Plugin: 
 
Activate "Build only if PR is mergeable" of Stash Pull Requests Builder on Jenkins to enforce REST API call to .../merge 
 Possible solution: 
 
Always call https:///stash/rest/api/latest/projects//repos//pull-requests//merge if there are changes on https:///stash/rest/api/1.0/projects//repos//pull-requests/ 
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  

[JIRA] (JENKINS-39400) Stacktrace on Jenkins Global Configuration page

2016-11-04 Thread stefan.thurnh...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stefan Thurnherr commented on  JENKINS-39400  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Stacktrace on Jenkins Global Configuration page   
 

  
 
 
 
 

 
 yes same here: ruby-runtime 0.13  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-19946) NullPointerException when authentication fails using LDAP with Jenkins as a Jetty webapp

2016-11-04 Thread sorin.sbar...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sorin Sbarnea updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-19946  
 
 
  NullPointerException when authentication fails using LDAP with Jenkins as a Jetty webapp   
 

  
 
 
 
 

 
Change By: 
 Sorin Sbarnea  
 

  
 
 
 
 

 
 A NullPointerException occurs if the authentication fails. I use LDAP authentication but it's likely unrelated to the authentication method. Probably just a configuration error.Here the stack trace: {code} java.lang.NullPointerException at org.eclipse.jetty.util.QuotedStringTokenizer.quoteOnly(QuotedStringTokenizer.java:346) at org.eclipse.jetty.http.HttpFields.quoteOnlyOrAppend(HttpFields.java:1183) at org.eclipse.jetty.http.HttpFields.addSetCookie(HttpFields.java:835) at org.eclipse.jetty.server.Response.addCookie(Response.java:201) at javax.servlet.http.HttpServletResponseWrapper.addCookie(HttpServletResponseWrapper.java:98) at javax.servlet.http.HttpServletResponseWrapper.addCookie(HttpServletResponseWrapper.java:98) at org.acegisecurity.ui.rememberme.TokenBasedRememberMeServices.cancelCookie(TokenBasedRememberMeServices.java:332) at org.acegisecurity.ui.rememberme.TokenBasedRememberMeServices.autoLogin(TokenBasedRememberMeServices.java:261) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:104) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1486) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:503) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:138) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:540) at 

[JIRA] (JENKINS-39502) ghprb couldn't pass the variable for triggerPhrase

2016-11-04 Thread hanbingxi...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 jubel han created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39502  
 
 
  ghprb couldn't pass the variable for triggerPhrase   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 ben patterson  
 
 
Components: 
 ghprb-plugin, job-dsl-plugin  
 
 
Created: 
 2016/Nov/04 10:45 AM  
 
 
Environment: 
 jenkins v2.28  ghprb-plugin v1.32.2  job-dsl-plugin v1.5.2  
 
 
Labels: 
 jenkins dsl ghprb triggerPhrase  
 
 
Priority: 
  Major  
 
 
Reporter: 
 jubel han  
 

  
 
 
 
 

 
 This is DSL script code: 

 

def phrase = 'testphrase'
job("test_job") {
displayName('test_job')
scm {
git {
remote {
github('xxx/xxx')
refspec('+refs/pull/*:refs/remotes/origin/pr/*')
}
branch('${sha1}')
}
}
triggers {
ghprbTrigger {
adminlist("")
whitelist("")
cron("")
orgslist('xxx')
triggerPhrase("${phrase}")
onlyTriggerPhrase(true)
useGitHubHooks(true)
permitAll(false)
autoCloseFailedPullRequests(false)
displayBuildErrorsOnDownstreamBuilds(false)
commentFilePath("")
skipBuildPhrase("")
allowMembersOfWhitelistedOrgsAsAdmin(true)
msgSuccess("")
msgFailure("")
commitStatusContext("")
gitHubAuthId("")
buildDescTemplate("")
}
}
}
 
  

[JIRA] (JENKINS-39444) Spurious "You have no permission to build" errors with inconsistent effects.

2016-11-04 Thread imking...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mike Kinghan edited a comment on  JENKINS-39444  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Spurious "You have no permission to build" errors with inconsistent effects.   
 

  
 
 
 
 

 
 As with @ScottJustason, this is a *regression* in my case. It started happening with my first upgrade to Jenkins > =  2.0. The problem was innocuous at first because the jobs that I "had no permission to build" where triggered as build-steps of parent jobs, and in fact they ran as they had always done. The problem bites now that I want to trigger a downstream job as a post-build action, and in this case "you have no permission to build" turns out true.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-33655) blank page after login, log says: java.lang.RuntimeException: Header>6144

2016-11-04 Thread sorin.sbar...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sorin Sbarnea edited a comment on  JENKINS-33655  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: blank page after login, log says: java.lang.RuntimeException: Header>6144   
 

  
 
 
 
 

 
 To be clear: this error is caused by Jenkins sending a too big header as part of the response, not the client. In fact the client is sending a header < 500 bites. We observed this behaviour on an instance with LDAP login enabled and especially on the /console page. It did not happen while requesting the /textConsole page. My impression is that http://stackoverflow.com/questions/20083651/jersey-client-post-results-in-header-full-java-lang-runtimeexception-header could be used to increase the limit of the header size.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-39444) Spurious "You have no permission to build" errors with inconsistent effects.

2016-11-04 Thread imking...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mike Kinghan commented on  JENKINS-39444  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Spurious "You have no permission to build" errors with inconsistent effects.   
 

  
 
 
 
 

 
 As with @ScottJustason, this is a regression in my case. It started happening with my first upgrade to Jenkins > 2.0. The problem was innocuous at first because the jobs that I "had no permission to build" where triggered as build-steps of parent jobs, and in fact they ran as they had always done. The problem bites now that I want to trigger a downstream job as a post-build action, and in this case "you have no permission to build" turns out true.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-33655) blank page after login, log says: java.lang.RuntimeException: Header>6144

2016-11-04 Thread sorin.sbar...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sorin Sbarnea commented on  JENKINS-33655  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: blank page after login, log says: java.lang.RuntimeException: Header>6144   
 

  
 
 
 
 

 
 To be clear: this error is caused by Jenkins sending a too big header as part of the response, not the client. In fact the client is sending a header < 500 bites. We observed this behaviour on an instance with LDAP login enabled and especially on the /console page. It did not happen while requesting the /textConsole page.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-39501) Docker image 2.19.2 is missing for the newest LTS version

2016-11-04 Thread em...@daniel-zwicker.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Zwicker created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39501  
 
 
  Docker image 2.19.2 is missing for the newest LTS version   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Nicolas De Loof  
 
 
Components: 
 docker  
 
 
Created: 
 2016/Nov/04 10:25 AM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Daniel Zwicker  
 

  
 
 
 
 

 
 The current LTS version present on the jenkinsci.org page ist 2.19.2. At dockerhub there is no tagged version for this release.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
  

[JIRA] (JENKINS-39500) ExternalWorkspaceManagerPluginTest might fail due to plugins installation order

2016-11-04 Thread egutier...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Evaristo Gutierrez created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39500  
 
 
  ExternalWorkspaceManagerPluginTest might fail due to plugins installation order   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Oliver Gondža  
 
 
Components: 
 acceptance-test-harness  
 
 
Created: 
 2016/Nov/04 9:35 AM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Evaristo Gutierrez  
 

  
 
 
 
 

 
 workflow-job plugin is needed to execute the test suite but it might happen that it is installed after external-workspace-manager plugin is installed, and therefore this last one is not usable.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
   

[JIRA] (JENKINS-39500) ExternalWorkspaceManagerPluginTest might fail due to plugins installation order

2016-11-04 Thread egutier...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Evaristo Gutierrez updated  JENKINS-39500  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39500  
 
 
  ExternalWorkspaceManagerPluginTest might fail due to plugins installation order   
 

  
 
 
 
 

 
Change By: 
 Evaristo Gutierrez  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-39500) ExternalWorkspaceManagerPluginTest might fail due to plugins installation order

2016-11-04 Thread egutier...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Evaristo Gutierrez assigned an issue to Evaristo Gutierrez  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39500  
 
 
  ExternalWorkspaceManagerPluginTest might fail due to plugins installation order   
 

  
 
 
 
 

 
Change By: 
 Evaristo Gutierrez  
 
 
Assignee: 
 Oliver Gondža Evaristo Gutierrez  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-39500) ExternalWorkspaceManagerPluginTest might fail due to plugins installation order

2016-11-04 Thread egutier...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Evaristo Gutierrez started work on  JENKINS-39500  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Evaristo Gutierrez  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-38928) When save a job you lose the changes if someone is reading the job

2016-11-04 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-38928  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: When save a job you lose the changes if someone is reading the job   
 

  
 
 
 
 

 
 Code changed in jenkins User: Vincent Latombe Path: src/main/java/org/jenkinsci/test/acceptance/po/ConfigurablePageObject.java src/test/java/core/FreestyleJobTest.java http://jenkins-ci.org/commit/acceptance-test-harness/4721f1d188c6315b60c5ca9fac6e7495abe54fef Log: JENKINS-38928 Add a test doing apply then save in a job  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-38928) When save a job you lose the changes if someone is reading the job

2016-11-04 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-38928  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: When save a job you lose the changes if someone is reading the job   
 

  
 
 
 
 

 
 Code changed in jenkins User: Vincent Latombe Path: pom.xml src/main/java/org/jenkinsci/test/acceptance/FallbackConfig.java src/main/java/org/jenkinsci/test/acceptance/po/ConfigurablePageObject.java src/test/java/core/FreestyleJobTest.java http://jenkins-ci.org/commit/acceptance-test-harness/5f4c2b81cea283b5397b0b3bc40120609a0921a1 Log: Merge pull request #210 from Vlatombe/JENKINS-38928 JENKINS-38928 Add a test doing apply then save in a job Compare: https://github.com/jenkinsci/acceptance-test-harness/compare/fdd33e12599c...5f4c2b81cea2  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-38928) When save a job you lose the changes if someone is reading the job

2016-11-04 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-38928  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: When save a job you lose the changes if someone is reading the job   
 

  
 
 
 
 

 
 Code changed in jenkins User: Vincent Latombe Path: src/main/java/org/jenkinsci/test/acceptance/po/ConfigurablePageObject.java http://jenkins-ci.org/commit/acceptance-test-harness/0e6815addd8e22b904f18578d64fb0db003ca505 Log: JENKINS-38928 Wait for splash to appear  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-38928) When save a job you lose the changes if someone is reading the job

2016-11-04 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-38928  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: When save a job you lose the changes if someone is reading the job   
 

  
 
 
 
 

 
 Code changed in jenkins User: Vincent Latombe Path: src/main/java/org/jenkinsci/test/acceptance/FallbackConfig.java http://jenkins-ci.org/commit/acceptance-test-harness/057ae2fcd8e9cf46ddda357f8068addecda10e3e Log: JENKINS-38928 Pull form-element-path 1.8  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-38928) When save a job you lose the changes if someone is reading the job

2016-11-04 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-38928  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: When save a job you lose the changes if someone is reading the job   
 

  
 
 
 
 

 
 Code changed in jenkins User: Vincent Latombe Path: src/main/java/org/jenkinsci/test/acceptance/po/ConfigurablePageObject.java http://jenkins-ci.org/commit/acceptance-test-harness/d20f235ad5f18831ac6333155e7b7c48cb718ad2 Log: JENKINS-38928 Simplify assertion  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-38913) DSL for choiceParam not working

2016-11-04 Thread m...@okiizo.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 ma pi edited a comment on  JENKINS-38913  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: DSL for choiceParam not working   
 

  
 
 
 
 

 
 I have same problem too.Add some information about this problem.Jenkins 2.19.1Job DSL Plugin 1.52Promoted Builds Plugin 2.27This is a small Job-DSL script reproduce this issue.{code:java}job('JENKINS_38913') {  description('reproduce JENKINS-38913')  properties {promotions {  promotion {name('promote-me')icon('star-red')conditions {  manual('') {parameters {  choiceParam('choice', ['a', 'b', 'c'], 'FIXME')}  }}  }}  }}{code}After generate Job. Jenkins report warning.!1.png|thumbnail!!2.png|thumbnail!Generated config.xml is here.  ( {noformat} ${JENKINS_HOME}/jobs/JENKINS_38913/promotions/promote-me/config.xml ) {noformat} {code:xml}  promote-me  star-red  a  b  cchoice  FIXME  {code}Then, go back to the warning page and click "Discard Unreadable Data"Check config.xml again{code:xml}  false  false  false  false  falsefalsechoice  FIXMEstar-red  {code}{noformat} ... {noformat} section removed.finally, edit this job manually.Correct config.xml is here.{code:xml}  false  false  false  false  falsefalsechoice  FIXMEa  b  cstar-red{code}I guess Job-DSL plugin lost choiceParam type(type hint?).I hope this information to help.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  

[JIRA] (JENKINS-39496) Make PullRequestSCMRevision public

2016-11-04 Thread rarabaol...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Raul Arabaolaza updated  JENKINS-39496  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39496  
 
 
  Make PullRequestSCMRevision public   
 

  
 
 
 
 

 
Change By: 
 Raul Arabaolaza  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-38913) DSL for choiceParam not working

2016-11-04 Thread m...@okiizo.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 ma pi edited a comment on  JENKINS-38913  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: DSL for choiceParam not working   
 

  
 
 
 
 

 
 I have same problem too.Add some information about this problem.Jenkins 2.19.1Job DSL Plugin 1.52Promoted Builds Plugin 2.27This is a small Job-DSL script reproduce this issue.{code:java}job('JENKINS_38913') {  description('reproduce JENKINS-38913')  properties {promotions {  promotion {name('promote-me')icon('star-red')conditions {  manual('') {parameters {  choiceParam('choice', ['a', 'b', 'c'], 'FIXME')}  }}  }}  }}{code}After generate Job. Jenkins report warning.!1.png|thumbnail!!2.png|thumbnail!Generated config.xml is here. (${JENKINS_HOME}/jobs/JENKINS_38913/promotions/promote-me/config.xml){code:xml}  promote-me  star-red  a  b  cchoice   description FIXME   {code}Then, go back to the warning page and click "Discard Unreadable Data"Check config.xml again{code:xml}  false  false  false  false  falsefalsechoice   description FIXME star-red  {code}{noformat} ... {noformat} section removed.finally, edit this job manually.Correct config.xml is here.{code:xml}  false  false  false  false  falsefalsechoice   description FIXME a  b  cstar-red{code}I guess Job-DSL plugin lost choiceParam type(type hint?).I hope this information to help.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

   

[JIRA] (JENKINS-38913) DSL for choiceParam not working

2016-11-04 Thread m...@okiizo.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 ma pi commented on  JENKINS-38913  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: DSL for choiceParam not working   
 

  
 
 
 
 

 
 I have same problem too. Add some information about this problem. Jenkins 2.19.1 Job DSL Plugin 1.52 Promoted Builds Plugin 2.27 This is a small Job-DSL script reproduce this issue. 

 

job('JENKINS_38913') {
  description('reproduce JENKINS-38913')
  properties {
promotions {
  promotion {
name('promote-me')
icon('star-red')
conditions {
  manual('') {
parameters {
  choiceParam('choice', ['a', 'b', 'c'], 'FIXME')
}
  }
}
  }
}
  }
}
 

 After generate Job. Jenkins report warning.   Generated config.xml is here.  ($ {JENKINS_HOME} /jobs/JENKINS_38913/promotions/promote-me/config.xml) 

 

"promoted-builds@2.27">
  promote-me
  star-red
  

  
  

  

  a
  b
  c

  
  choice
  description

  

  
  

 

 Then, go back to the warning page and click "Discard Unreadable Data" Check config.xml again 

 


"promoted-builds@2.27">
  false
  
  "hudson.scm.NullSCM"/>
  false
  false
  false
  false
  
  false
  

  
  

  choice
  description
  

  

  
  star-red
  

 

 

 
 ...  

  section removed. finally, edit this job manually. Correct config.xml is here. 

 


"promoted-builds@2.27">
  false
  
  "hudson.scm.NullSCM"/>
  false
  false
  false
  false
  
  false
  

  
  

  choice
  description
  "java.util.Arrays$ArrayList">
"string-array">
  a
  b
  c

  

  

  
  star-red
  
  

 

 I guess Job-DSL plugin lost choiceParam type(type hint?). I hope this information to help.  
 

  
 
 
 
 
   

[JIRA] (JENKINS-38928) When save a job you lose the changes if someone is reading the job

2016-11-04 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-38928  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: When save a job you lose the changes if someone is reading the job   
 

  
 
 
 
 

 
 Code changed in jenkins User: Vincent Latombe Path: Jenkinsfile src/main/resources/org/jenkinsci/plugins/form-element-path.js http://jenkins-ci.org/commit/form-element-path-plugin/4a72ea5cf83380cd44ac1c348452f165d8bf3f1f Log: Merge pull request #6 from Vlatombe/JENKINS-38928 JENKINS-38928 Fix apply behaviour when form contains radio group Compare: https://github.com/jenkinsci/form-element-path-plugin/compare/a4518681c91a...4a72ea5cf833  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-38928) When save a job you lose the changes if someone is reading the job

2016-11-04 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-38928  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: When save a job you lose the changes if someone is reading the job   
 

  
 
 
 
 

 
 Code changed in jenkins User: Vincent Latombe Path: Jenkinsfile src/main/resources/org/jenkinsci/plugins/form-element-path.js http://jenkins-ci.org/commit/form-element-path-plugin/e1b232636c6a45715d1f33150ff5953861ecddd0 Log: JENKINS-38928 Handle radio groups This fixes the form handling issue after 'Apply' is clicked.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-39496) Make PullRequestSCMRevision public

2016-11-04 Thread rarabaol...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Raul Arabaolaza updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39496  
 
 
  Make PullRequestSCMRevision public   
 

  
 
 
 
 

 
Change By: 
 Raul Arabaolaza  
 
 
Issue Type: 
 New Feature Task  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-39496) Make PullRequestSCMRevision public

2016-11-04 Thread rarabaol...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Raul Arabaolaza updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39496  
 
 
  Make PullRequestSCMRevision public   
 

  
 
 
 
 

 
Change By: 
 Raul Arabaolaza  
 

  
 
 
 
 

 
 In a multibranch pipeline project there is the option to build PR merged with a base branch (typically master or integration branches) to ensure that changes in the final status (merged) are valid.In this cases the revision given by the build data refers to the merge commit, not the last PR commit in the remote ` {{ PullRequestSCMRevision ` }}  contains info about the pull hash and the base hash that is internally used to notify GitHub. This info could be very interesting to third parties like pipeline steps, but the class visibility is default so  is not possible to access it.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to 

[JIRA] (JENKINS-38913) DSL for choiceParam not working

2016-11-04 Thread m...@okiizo.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 ma pi updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38913  
 
 
  DSL for choiceParam not working   
 

  
 
 
 
 

 
Change By: 
 ma pi  
 
 
Attachment: 
 2.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


<    1   2   3   >