[JIRA] [scm-sync-configuration-plugin] (JENKINS-25786) Renaming Job Causes a poisoned commitQueue

2015-10-06 Thread stefan.schaefer...@web.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Stefan Schäfer commented on  JENKINS-25786 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Renaming Job Causes a poisoned commitQueue  
 
 
 
 
 
 
 
 
 
 
lol 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [websphere-deployer-plugin] (JENKINS-29725) Application starting issue websphere application server 8.5 after deployment Jenkins

2015-10-06 Thread gregpeter...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Greg Peters updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-29725 
 
 
 
  Application starting issue websphere application server 8.5 after deployment Jenkins  
 
 
 
 
 
 
 
 
 
 
Ansuman Swain, manually install the attached version and shoot me the verbose output so I can see exactly what's going on. 
 
 
 
 
 
 
 
 
 

Change By:
 
 Greg Peters 
 
 
 

Attachment:
 
 websphere-deployer.hpi 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [websphere-deployer-plugin] (JENKINS-29725) Application starting issue websphere application server 8.5 after deployment Jenkins

2015-10-06 Thread gregpeter...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Greg Peters reopened an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-29725 
 
 
 
  Application starting issue websphere application server 8.5 after deployment Jenkins  
 
 
 
 
 
 
 
 
 

Change By:
 
 Greg Peters 
 
 
 

Resolution:
 
 Fixed 
 
 
 

Status:
 
 Closed Reopened 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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.


brenda Folake shared "FROM MISS BRENDA FOLAKE.txt" with you

2015-10-06 Thread 'Brenda via Dropbox' via Jenkins Issues
>From Brenda:

"Open the confidential attachment file to see the email i sent to you and get 
back to me for more details."

Click here to view[1]

(Brenda shared these files using Dropbox. Enjoy!)

[1]: https://www.dropbox.com/l/s/PN2iIlfdRCpjHT4LOYqJ2h?text=1

-- 
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] [view-job-filters-plugin] (JENKINS-24579) Filter based on Job Labels

2015-10-06 Thread p...@paulb.org (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Paul Brinkmann commented on  JENKINS-24579 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Filter based on Job Labels  
 
 
 
 
 
 
 
 
 
 
We use node labels for our Multi-configuration project builds to build a project across several platforms. It would be awesome to filter jobs based on which one had builds on a specific platform. 
For an example job config with labels: 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [view-job-filters-plugin] (JENKINS-24579) Filter based on Job Labels

2015-10-06 Thread p...@paulb.org (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Paul Brinkmann updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-24579 
 
 
 
  Filter based on Job Labels  
 
 
 
 
 
 
 
 
 

Change By:
 
 Paul Brinkmann 
 
 
 

Attachment:
 
 screenshot-1.png 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [libvirt-slave-plugin] (JENKINS-30691) Unable to connect to remote server

2015-10-06 Thread g...@gkr.i24.cc (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 G. Kr. resolved as Not A Defect 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
marking resolved 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-30691 
 
 
 
  Unable to connect to remote server  
 
 
 
 
 
 
 
 
 

Change By:
 
 G. Kr. 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Not A Defect 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [libvirt-slave-plugin] (JENKINS-30691) Unable to connect to remote server

2015-10-06 Thread g...@gkr.i24.cc (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 G. Kr. commented on  JENKINS-30691 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Unable to connect to remote server  
 
 
 
 
 
 
 
 
 
 
can you make a suggestion were should what exactly be documented ?  when you configure the cloud you also need to configure credentials, is that too hidden away in the UI? also what do you mean with accepting external passwords ? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [ownership-plugin] (JENKINS-30818) Ownership plugin: NPE in the job property summary

2015-10-06 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oleg Nenashev created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30818 
 
 
 
  Ownership plugin: NPE in the job property summary  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Oleg Nenashev 
 
 
 

Components:
 

 ownership-plugin 
 
 
 

Created:
 

 06/Oct/15 9:10 PM 
 
 
 

Environment:
 

 Jenkins 1.609.1  Ownership 0.7 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Oleg Nenashev 
 
 
 
 
 
 
 
 
 
 
The issue has been reported in the external bugtracker: 

 
Caused by: org.apache.commons.jelly.JellyTagException: jar:file:/X/jenkins-core-1.609.1.jar!/hudson/model/Job/jobpropertysummaries.jelly:30:78:  Error setting property 'from', exception - java.lang.NullPointerException
	at org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:726)
	at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:281)
	at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
	at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150)
	at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
	at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
	at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:95)
	at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:147)
	at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
	at org.apac

[JIRA] [subversion-plugin] (JENKINS-30774) Subversion parameterized build throws error in job configuration

2015-10-06 Thread schristo...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Steven Christou commented on  JENKINS-30774 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Subversion parameterized build throws error in job configuration  
 
 
 
 
 
 
 
 
 
 
Manuel Jesús Recena Soto that sounds good. The current error message (and huge stack trace generated) can be a little misleading. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [subversion-plugin] (JENKINS-30774) Subversion parameterized build throws error in job configuration

2015-10-06 Thread schristo...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Steven Christou edited a comment on  JENKINS-30774 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Subversion parameterized build throws error in job configuration  
 
 
 
 
 
 
 
 
 
 [~recena] that sounds good. The current error message (and huge stack trace generated) can be a little  misleading  confusing . 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [core] (JENKINS-26657) File context menu missing when installing Slave under windows with jnlp

2015-10-06 Thread vladg...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 vlad guan commented on  JENKINS-26657 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: File context menu missing when installing Slave under windows with jnlp  
 
 
 
 
 
 
 
 
 
 
No worries Sebastien. I did not know about that article. Good to know my method is somewhat official. Will be adding that article to my docs Gor future reference. Vlad 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [downstream-ext-plugin] (JENKINS-30789) New condition: Downstream build result

2015-10-06 Thread ku...@gmx.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 kutzi commented on  JENKINS-30789 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: New condition: Downstream build result  
 
 
 
 
 
 
 
 
 
 
Can you elaborate on how this should exactly work (e.g.: should it be base own the result of the previous downstream build?) and what is the usecase for this? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [downstream-ext-plugin] (JENKINS-30789) New condition: Downstream build result

2015-10-06 Thread ku...@gmx.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 kutzi edited a comment on  JENKINS-30789 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: New condition: Downstream build result  
 
 
 
 
 
 
 
 
 
 Can you elaborate on how this should exactly work (e.g.: should it be  base own  based on  the result of the *previous* downstream build?) and what is the usecase for this? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [subversion-plugin] (JENKINS-27084) SVN authentication fails using subversion plugin v.2.5

2015-10-06 Thread rec...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Jesús Recena Soto commented on  JENKINS-27084 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: SVN authentication fails using subversion plugin v.2.5  
 
 
 
 
 
 
 
 
 
 
M L, Please review these comments because there are users with the problem solved. 
If you prefer, you can file a new ticket in which provide a step by step to reproduce the bug. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [envinject-plugin] (JENKINS-18714) SVN_URL and SVN_REVISION environment variables are missing when repository url contains a variable

2015-10-06 Thread rec...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Jesús Recena Soto commented on  JENKINS-18714 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: SVN_URL and SVN_REVISION environment variables are missing when repository url contains a variable  
 
 
 
 
 
 
 
 
 
 
Slawek Wieczorkowski, I tried to reproduce the bug unsuccessful. 
I really want to help here but I need a step by step so that can reproduce the bug and find a solution. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [email-ext-plugin] (JENKINS-30817) Add option to disable In-Reply-To header

2015-10-06 Thread pub...@scott-weldon.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Scott Weldon created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30817 
 
 
 
  Add option to disable In-Reply-To header  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Alex Earl 
 
 
 

Components:
 

 email-ext-plugin 
 
 
 

Created:
 

 06/Oct/15 7:27 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Scott Weldon 
 
 
 
 
 
 
 
 
 
 
I would like to request that an option be added to disable the In-Reply-To header. I see that this headers was added in response to issue 3089, and the relevant section of code can be found here. 
My use case: my company uses ZenDesk to track issues, and we have Jenkins set up to send email notifications after every build. Since we generally already have a ticket open for that task, we merge the newly-created ticket into the original ticket. If that original ticket was requested by a client, and not an internal user, then any updates that Jenkins sends ("Still Failing", "Fixed", etc.) will also be sent to the client, which we would prefer to avoid. If there was an option to disable the In-Reply-To header, that would fix this issue. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 

[JIRA] [support-core-plugin] (JENKINS-30816) Allow for customizing JENKINS_HOME/logs/custom size

2015-10-06 Thread schristo...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Steven Christou created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30816 
 
 
 
  Allow for customizing JENKINS_HOME/logs/custom size  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Steven Christou 
 
 
 

Components:
 

 support-core-plugin 
 
 
 

Created:
 

 06/Oct/15 7:18 PM 
 
 
 

Priority:
 
  Trivial 
 
 
 

Reporter:
 
 Steven Christou 
 
 
 
 
 
 
 
 
 
 
Currently the support core plugin records custom loggers to the file system, however it would be nice to allow users to customize the size (via JVM argument). https://github.com/jenkinsci/support-core-plugin/blob/5edc573e45457dd79b8e07594bc24f5921606ef2/src/main/java/com/cloudbees/jenkins/support/impl/JenkinsLogs.java#L70 would need to be fixed to use FileListCapComponent.MAX_FILE_SIZE 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 

[JIRA] [support-core-plugin] (JENKINS-24814) Bundle rotated slave launch logs

2015-10-06 Thread schristo...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Steven Christou updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-24814 
 
 
 
  Bundle rotated slave launch logs  
 
 
 
 
 
 
 
 
 

Change By:
 
 Steven Christou 
 
 
 

Summary:
 
 Bundle  rorated  rotated  slave launch logs 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [hp-application-automation-tools-plugin] (JENKINS-30743) How to update the HP LoadRunner Jenkins plugin to see Controller

2015-10-06 Thread byron.magru...@uspto.gov (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Byron Magruder commented on  JENKINS-30743 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: How to update the HP LoadRunner Jenkins plugin to see Controller  
 
 
 
 
 
 
 
 
 
 
Problem: Currently the HP-application-automation-tools-plugin does not allow the HP LoadRunner Controller to be visible during execution. We understand that there is a way to configure the Jenkins server to allow this. Could you please provide that info (i.e. what file needs to be changed and what fields to change). 
I understand that HpToolsLauncher/TestRunners/PerformanceTestRunner.cs::320 is the file that needs to be changed but what does it need to changed to in order for the Controller GUI to be displayed during Jenkins builds. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [hp-application-automation-tools-plugin] (JENKINS-30743) How to update the HP LoadRunner Jenkins plugin to see Controller

2015-10-06 Thread byron.magru...@uspto.gov (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Byron Magruder started work on  JENKINS-30743 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

Change By:
 
 Byron Magruder 
 
 
 

Status:
 
 Open In Progress 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [ldap-plugin] (JENKINS-24859) LDAP cresentials with sAMAccountName including uppercase letter does not work with Global Security

2015-10-06 Thread levi.dano...@us.bosch.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Levi Danoski commented on  JENKINS-24859 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: LDAP cresentials with sAMAccountName including uppercase letter does not work with Global Security  
 
 
 
 
 
 
 
 
 
 
Since the core issue appears to be fixed, are there any plans to update this plugin to make use of the new API? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [git-plugin] (JENKINS-30291) Side effect of Email-ext plugin to Git

2015-10-06 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mark Waite resolved as Not A Defect 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
As far as I can tell from the Era Tolekov's description, this is not a bug in the git plugin, and may not even be a Jenkins bug. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-30291 
 
 
 
  Side effect of Email-ext plugin to Git  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mark Waite 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Not A Defect 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [job-dsl-plugin] (JENKINS-28744) Support for confguring publish over CIFS Plugin

2015-10-06 Thread m...@daniel-spilker.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Spilker updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-28744 
 
 
 
  Support for confguring publish over CIFS Plugin  
 
 
 
 
 
 
 
 
 
 
Added a label for publish-over-cifs-plugin because the DSL can also be added to that plugin through the Job DSL extension point. 
 
 
 
 
 
 
 
 
 

Change By:
 
 Daniel Spilker 
 
 
 

Component/s:
 
 publish-over-cifs-plugin 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [cucumber-plugin] (JENKINS-28431) Add support for Cucumber plugin

2015-10-06 Thread m...@daniel-spilker.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Spilker assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
The DSL can also be added to the Cucumber plugin through the Job DSL extension point. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-28431 
 
 
 
  Add support for Cucumber plugin  
 
 
 
 
 
 
 
 
 

Change By:
 
 Daniel Spilker 
 
 
 

Assignee:
 
 Daniel Spilker 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [bitbucket-pullrequest-builder-plugin] (JENKINS-26488) Add support for Bitbucket Pull Request Builder plugin

2015-10-06 Thread m...@daniel-spilker.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Spilker assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Added a label for bitbucket-pullrequest-builder-plugin because the DSL can also be added to that plugin through the Job DSL extension point. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-26488 
 
 
 
  Add support for Bitbucket Pull Request Builder plugin  
 
 
 
 
 
 
 
 
 

Change By:
 
 Daniel Spilker 
 
 
 

Component/s:
 
 bitbucket-pullrequest-builder-plugin 
 
 
 

Assignee:
 
 Daniel Spilker 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [accurev-plugin] (JENKINS-22138) Add support for Accurev SCM

2015-10-06 Thread m...@daniel-spilker.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Spilker assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Added a label for accurev-plugin because the DSL can also be added to that plugin through the Job DSL extension point. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-22138 
 
 
 
  Add support for Accurev SCM  
 
 
 
 
 
 
 
 
 

Change By:
 
 Daniel Spilker 
 
 
 

Component/s:
 
 accurev-plugin 
 
 
 

Assignee:
 
 Justin Ryan 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [git-client-plugin] (JENKINS-30073) git-client changelog timestamp is wrong

2015-10-06 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mark Waite edited a comment on  JENKINS-30073 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: git-client changelog timestamp is wrong  
 
 
 
 
 
 
 
 
 
 [~vkopchenin] thanks for the output. Unfortunately, as noted in the  [  earlier comment |https://issues.jenkins-ci.org/browse/JENKINS-30073?focusedCommentId=235998&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-235998] , the {code}%cI{code} argument is not workable in the git client plugin because the plugin must support git versions prior to git 2.  We can't abandon support for Red Hat 5, Red Hat 6, Debian 6, and several other working environments which provide git versions prior to git 2.Your output is a good source to use to write a test to show the failure and then you could submit a pull request with the test and with code changes to resolve the failure.  Even if all you do is write a test to show the failure and submit that as a pull request, that will help move towards an eventual fix for the bug. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [git-client-plugin] (JENKINS-30073) git-client changelog timestamp is wrong

2015-10-06 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mark Waite commented on  JENKINS-30073 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: git-client changelog timestamp is wrong  
 
 
 
 
 
 
 
 
 
 
Slava Kopchenin thanks for the output. Unfortunately, as noted in the earlier comment, the  

 
%cI 

 
 argument is not workable in the git client plugin because the plugin must support git versions prior to git 2.  
We can't abandon support for Red Hat 5, Red Hat 6, Debian 6, and several other working environments which provide git versions prior to git 2. 
Your output is a good source to use to write a test to show the failure and then you could submit a pull request with the test and with code changes to resolve the failure. Even if all you do is write a test to show the failure and submit that as a pull request, that will help move towards an eventual fix for the bug. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [git-client-plugin] (JENKINS-30073) git-client changelog timestamp is wrong

2015-10-06 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mark Waite edited a comment on  JENKINS-30073 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: git-client changelog timestamp is wrong  
 
 
 
 
 
 
 
 
 
 Thanks [~vkopchenin] thanks  for the picture. It showed that the API call is a public API that is easily accessible. That makes it easier to write a test for this bug.For example, I see a problem timestamp in the json response when I request http://localhost:8085/view/git-client/job/git-client-multi-master/242/api/json but not when I request http://localhost:8085/view/git-client/job/git-client-multi-master/244/api/json.  In my use case, it doesn't seem to be an "every build" occurrence, but it happens on at least some of my cases. Is your Jenkins server running with Java 6, or with a later version of Java? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [git-client-plugin] (JENKINS-30073) git-client changelog timestamp is wrong

2015-10-06 Thread v.kopche...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Slava Kopchenin edited a comment on  JENKINS-30073 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: git-client changelog timestamp is wrong  
 
 
 
 
 
 
 
 
 
 *"for all builds"* I mean in my case...I logged the *hudson.plugins.git.GitChangeSet#parseCommit* and the *jenkins.log* has the following output:{code:java}commit 302548f75c3eb6fa1db83634e4061d0ded416e5atree e1bd430d3f45b7aae54a3061b7895ee1858ec1f8parent c74f084d8f9bc9e52f0b3fe9175ad27c39947a73author Viacheslav Kopchenin  2015-10-06 19:29:47 +0300committer Viacheslav Kopchenin  2015-10-06 19:29:47 +0300pom.xml:100644 100644 bb32d78c69a7bf79849217bc02b1ba2c870a5a66 343a844ad90466d8e829896c1827ca7511d0d1ef M modules/platform/pom.xml{code}*But*, when I changed (*ai->aI, ci->cI*) :{code:java}-public static final String RAW = "commit %H%ntree %T%nparent %P%nauthor %aN <%aE> %ai%ncommitter %cN <%cE> %ci%n%n%w(76,4,4)%s%n%n%b";+public static final String RAW = "commit %H%ntree %T%nparent %P%nauthor %aN <%aE> %aI%ncommitter %cN <%cE> %cI%n%n%w(76,4,4)%s%n%n%b";{code}The output is:{code:java}commit 841fd27f1a0ef11a1696e3a5cb6eced316761ee3tree 369d49618e2752d809ee8807149c402485b8e15bparent b5ad39f1d9c338cb76b2851d8b2ebcef7d59484eauthor Viacheslav Kopchenin  2015-10-06T20:09:18+03:00committer Viacheslav Kopchenin  2015-10-06T20:09:18+03:00pom.xml:100644 100644 5868c1b334fdea0d25b21705604e9e1d6f3243b8 56f50739924afe9d151a3c89aa7ace332e55b044 M modules/platform/pom.xml{code} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [git-client-plugin] (JENKINS-30073) git-client changelog timestamp is wrong

2015-10-06 Thread v.kopche...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Slava Kopchenin edited a comment on  JENKINS-30073 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: git-client changelog timestamp is wrong  
 
 
 
 
 
 
 
 
 
 *"for all builds"* I mean in my case...I logged the *hudson.plugins.git.GitChangeSet#parseCommit* and the *jenkins.log* has the following output:{code:java}commit 302548f75c3eb6fa1db83634e4061d0ded416e5atree e1bd430d3f45b7aae54a3061b7895ee1858ec1f8parent c74f084d8f9bc9e52f0b3fe9175ad27c39947a73author Viacheslav Kopchenin  2015-10-06 19:29:47 +0300committer Viacheslav Kopchenin  2015-10-06 19:29:47 +0300pom.xml:100644 100644 bb32d78c69a7bf79849217bc02b1ba2c870a5a66 343a844ad90466d8e829896c1827ca7511d0d1ef M modules/platform/pom.xml{code}*But*, when I changed:{code:java}-public static final String RAW = "commit %H%ntree %T%nparent %P%nauthor %aN <%aE> %ai%ncommitter %cN <%cE> %ci%n%n%w(76,4,4)%s%n%n%b";+public static final String RAW = "commit %H%ntree %T%nparent %P%nauthor %aN <%aE> %aI%ncommitter %cN <%cE> %cI%n%n%w(76,4,4)%s%n%n%b";{code}The output is:{code:java} :100644 100644 5868c1b334fdea0d25b21705604e9e1d6f3243b8 56f50739924afe9d151a3c89aa7ace332e55b044 M modules/platform/pom.xml commit 841fd27f1a0ef11a1696e3a5cb6eced316761ee3tree 369d49618e2752d809ee8807149c402485b8e15bparent b5ad39f1d9c338cb76b2851d8b2ebcef7d59484eauthor Viacheslav Kopchenin  2015-10-06T20:09:18+03:00committer Viacheslav Kopchenin  2015-10-06T20:09:18+03:00pom.xml:100644 100644 5868c1b334fdea0d25b21705604e9e1d6f3243b8 56f50739924afe9d151a3c89aa7ace332e55b044 M modules/platform/pom.xml{code} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [git-client-plugin] (JENKINS-30073) git-client changelog timestamp is wrong

2015-10-06 Thread v.kopche...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Slava Kopchenin edited a comment on  JENKINS-30073 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: git-client changelog timestamp is wrong  
 
 
 
 
 
 
 
 
 
 *"for all builds"* I mean in my case...I logged the *hudson.plugins.git.GitChangeSet#parseCommit* and the *jenkins.log* has the following output:{code:java}commit 302548f75c3eb6fa1db83634e4061d0ded416e5atree e1bd430d3f45b7aae54a3061b7895ee1858ec1f8parent c74f084d8f9bc9e52f0b3fe9175ad27c39947a73author Viacheslav Kopchenin  2015-10-06 19:29:47 +0300committer Viacheslav Kopchenin  2015-10-06 19:29:47 +0300pom.xml:100644 100644 bb32d78c69a7bf79849217bc02b1ba2c870a5a66 343a844ad90466d8e829896c1827ca7511d0d1ef M modules/platform/pom.xml{code}*But*, when  I  changed: {code:java} -public static final String RAW = "commit %H%ntree %T%nparent %P%nauthor %aN <%aE> %ai%ncommitter %cN <%cE> %ci%n%n%w(76,4,4)%s%n%n%b";+public static final String RAW = "commit %H%ntree %T%nparent %P%nauthor %aN <%aE> %aI%ncommitter %cN <%cE> %cI%n%n%w(76,4,4)%s%n%n%b"; {code}   The output is:{code:java}:100644 100644 5868c1b334fdea0d25b21705604e9e1d6f3243b8 56f50739924afe9d151a3c89aa7ace332e55b044 M modules/platform/pom.xmlcommit 841fd27f1a0ef11a1696e3a5cb6eced316761ee3tree 369d49618e2752d809ee8807149c402485b8e15bparent b5ad39f1d9c338cb76b2851d8b2ebcef7d59484eauthor Viacheslav Kopchenin  2015-10-06T20:09:18+03:00committer Viacheslav Kopchenin  2015-10-06T20:09:18+03:00pom.xml:100644 100644 5868c1b334fdea0d25b21705604e9e1d6f3243b8 56f50739924afe9d151a3c89aa7ace332e55b044 M modules/platform/pom.xml{code} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [git-client-plugin] (JENKINS-30073) git-client changelog timestamp is wrong

2015-10-06 Thread v.kopche...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Slava Kopchenin edited a comment on  JENKINS-30073 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: git-client changelog timestamp is wrong  
 
 
 
 
 
 
 
 
 
 *"for all builds"* I mean in my case...I logged the *hudson.plugins.git.GitChangeSet#parseCommit* and the *jenkins.log* has the following output:{code:java}commit 302548f75c3eb6fa1db83634e4061d0ded416e5atree e1bd430d3f45b7aae54a3061b7895ee1858ec1f8parent c74f084d8f9bc9e52f0b3fe9175ad27c39947a73author Viacheslav Kopchenin  2015-10-06 19:29:47 +0300committer Viacheslav Kopchenin  2015-10-06 19:29:47 +0300pom.xml:100644 100644 bb32d78c69a7bf79849217bc02b1ba2c870a5a66 343a844ad90466d8e829896c1827ca7511d0d1ef M modules/platform/pom.xml{code}*But*, when changed:-public static final String RAW = "commit %H%ntree %T%nparent %P%nauthor %aN <%aE> %ai%ncommitter %cN <%cE> %ci%n%n%w(76,4,4)%s%n%n%b";+public static final String RAW = "commit %H%ntree %T%nparent %P%nauthor %aN <%aE> %aI%ncommitter %cN <%cE> %cI%n%n%w(76,4,4)%s%n%n%b";The output is: {code : java}: 100644 100644 5868c1b334fdea0d25b21705604e9e1d6f3243b8 56f50739924afe9d151a3c89aa7ace332e55b044 M modules/platform/pom.xmlcommit 841fd27f1a0ef11a1696e3a5cb6eced316761ee3tree 369d49618e2752d809ee8807149c402485b8e15bparent b5ad39f1d9c338cb76b2851d8b2ebcef7d59484eauthor Viacheslav Kopchenin  2015-10-06T20:09:18+03:00committer Viacheslav Kopchenin  2015-10-06T20:09:18+03:00pom.xml:100644 100644 5868c1b334fdea0d25b21705604e9e1d6f3243b8 56f50739924afe9d151a3c89aa7ace332e55b044 M modules/platform/pom.xml {code} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [git-client-plugin] (JENKINS-30073) git-client changelog timestamp is wrong

2015-10-06 Thread v.kopche...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Slava Kopchenin commented on  JENKINS-30073 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: git-client changelog timestamp is wrong  
 
 
 
 
 
 
 
 
 
 
"for all builds" I mean in my case... 
I logged the hudson.plugins.git.GitChangeSet#parseCommit and the jenkins.log has the following output: 

 

commit 302548f75c3eb6fa1db83634e4061d0ded416e5a
tree e1bd430d3f45b7aae54a3061b7895ee1858ec1f8
parent c74f084d8f9bc9e52f0b3fe9175ad27c39947a73
author Viacheslav Kopchenin  2015-10-06 19:29:47 +0300
committer Viacheslav Kopchenin  2015-10-06 19:29:47 +0300

pom.xml

:100644 100644 bb32d78c69a7bf79849217bc02b1ba2c870a5a66 343a844ad90466d8e829896c1827ca7511d0d1ef M	modules/platform/pom.xml
 

 
But, when changed: 
 

public static final String RAW = "commit %H%ntree %T%nparent %P%nauthor %aN <%aE> %ai%ncommitter %cN <%cE> %ci%n%n%w(76,4,4)%s%n%n%b"; + public static final String RAW = "commit %H%ntree %T%nparent %P%nauthor %aN <%aE> %aI%ncommitter %cN <%cE> %cI%n%n%w(76,4,4)%s%n%n%b";
 
 
The output is: 
:100644 100644 5868c1b334fdea0d25b21705604e9e1d6f3243b8 56f50739924afe9d151a3c89aa7ace332e55b044 M modules/platform/pom.xml commit 841fd27f1a0ef11a1696e3a5cb6eced316761ee3 tree 369d49618e2752d809ee8807149c402485b8e15b parent b5ad39f1d9c338cb76b2851d8b2ebcef7d59484e author Viacheslav Kopchenin  2015-10-06T20:09:18+03:00 committer Viacheslav Kopchenin  2015-10-06T20:09:18+03:00 
 pom.xml 
:100644 100644 5868c1b334fdea0d25b21705604e9e1d6f3243b8 56f50739924afe9d151a3c89aa7ace332e55b044 M modules/platform/pom.xml 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
   

[JIRA] [git-client-plugin] (JENKINS-30073) git-client changelog timestamp is wrong

2015-10-06 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mark Waite commented on  JENKINS-30073 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: git-client changelog timestamp is wrong  
 
 
 
 
 
 
 
 
 
 
Thanks for the picture. It showed that the API call is a public API that is easily accessible. That makes it easier to write a test for this bug. 
For example, I see a problem timestamp in the json response when I request http://localhost:8085/view/git-client/job/git-client-multi-master/242/api/json but not when I request http://localhost:8085/view/git-client/job/git-client-multi-master/244/api/json. In my use case, it doesn't seem to be an "every build" occurrence, but it happens on at least some of my cases. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [promoted-builds-plugin] (JENKINS-30814) Send An Email Notification Upon A Failed Promotion Job

2015-10-06 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oleg Nenashev commented on  JENKINS-30814 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Send An Email Notification Upon A Failed Promotion Job  
 
 
 
 
 
 
 
 
 
 
The issue description is incomplete. No logs, etc.. Please follow https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue and provide the job's configuration, plugin version, etc. 
According to the common rules of Jenkins build steps, the process should be interrupted when an issue happens. "-1" return value in she shell script is considered as a "promotion failure", so further steps should not happen. In such case the behavior seems to be valid, although it's not what you would expect from the notification. 
Do you consider handling return statuses in scripts. If you want to setup an intelligent notification, you will need to provide conditions for e-mail triggers in any case. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [git-client-plugin] (JENKINS-30073) git-client changelog timestamp is wrong

2015-10-06 Thread v.kopche...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Slava Kopchenin updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30073 
 
 
 
  git-client changelog timestamp is wrong  
 
 
 
 
 
 
 
 
 

Change By:
 
 Slava Kopchenin 
 
 
 

Priority:
 
 Major Critical 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [git-client-plugin] (JENKINS-30073) git-client changelog timestamp is wrong

2015-10-06 Thread v.kopche...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Slava Kopchenin updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30073 
 
 
 
  git-client changelog timestamp is wrong  
 
 
 
 
 
 
 
 
 

Change By:
 
 Slava Kopchenin 
 
 
 

Attachment:
 
 timestamp.png 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [git-client-plugin] (JENKINS-30073) git-client changelog timestamp is wrong

2015-10-06 Thread v.kopche...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Slava Kopchenin updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30073 
 
 
 
  git-client changelog timestamp is wrong  
 
 
 
 
 
 
 
 
 

Change By:
 
 Slava Kopchenin 
 
 
 

Attachment:
 
 timestamp.png 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [git-client-plugin] (JENKINS-30073) git-client changelog timestamp is wrong

2015-10-06 Thread v.kopche...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Slava Kopchenin edited a comment on  JENKINS-30073 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: git-client changelog timestamp is wrong  
 
 
 
 
 
 
 
 
 
 I have the same problem  for all builds  [^timestamp.png]. -bash-4.2# git --versiongit version 2.4.0Jenkins ver. 1.609.3GIT client pluginShared library plugin for other Git related Jenkins plugins.1.19.0 Git pluginThis plugin integrates Git with Jenkins.2.4.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [git-client-plugin] (JENKINS-30073) git-client changelog timestamp is wrong

2015-10-06 Thread v.kopche...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Slava Kopchenin updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30073 
 
 
 
  git-client changelog timestamp is wrong  
 
 
 
 
 
 
 
 
 
 
I have the same problem timestamp.png.  
-bash-4.2# git --version git version 2.4.0 
Jenkins ver. 1.609.3 
GIT client plugin Shared library plugin for other Git related Jenkins plugins. 1.19.0 
Git plugin This plugin integrates Git with Jenkins. 2.4.0 
 
 
 
 
 
 
 
 
 

Change By:
 
 Slava Kopchenin 
 
 
 

Attachment:
 
 timestamp.png 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [subversion-plugin] (JENKINS-27084) SVN authentication fails using subversion plugin v.2.5

2015-10-06 Thread ju...@spamex.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 M L commented on  JENKINS-27084 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: SVN authentication fails using subversion plugin v.2.5  
 
 
 
 
 
 
 
 
 
 
reentering the password did not work for me on Jenkins ver. 1.609.2 with plugin version 2.5.3 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [join-plugin] (JENKINS-29652) Rerunning failed Delivery Pipeline stage doesn't enable/disable a manual trigger when using the Join plugin

2015-10-06 Thread chrisen...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Chris Engel commented on  JENKINS-29652 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Rerunning failed Delivery Pipeline stage doesn't enable/disable a manual trigger when using the Join plugin  
 
 
 
 
 
 
 
 
 
 
I can confirm I'm seeing the same issue with Join plugin 1.16 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [core] (JENKINS-30721) Filesets on Windows shall be case insensitive

2015-10-06 Thread vvv...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Vasili Galka closed an issue as Duplicate 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Duplicate of JENKINS-5253 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-30721 
 
 
 
  Filesets on Windows shall be case insensitive  
 
 
 
 
 
 
 
 
 

Change By:
 
 Vasili Galka 
 
 
 

Status:
 
 Open Closed 
 
 
 

Resolution:
 
 Duplicate 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [core] (JENKINS-30721) Filesets on Windows shall be case insensitive

2015-10-06 Thread vvv...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Vasili Galka commented on  JENKINS-30721 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Filesets on Windows shall be case insensitive  
 
 
 
 
 
 
 
 
 
 
Ok, I agree. The other is older and seems a better solution, since it is configurable. Let's close this one as duplicate. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [core] (JENKINS-30815) GZip compression of master-slave transfer should be optional

2015-10-06 Thread tom...@free.fr (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas de Grenier de Latour updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30815 
 
 
 
  GZip compression of master-slave transfer should be optional  
 
 
 
 
 
 
 
 
 

Change By:
 
 Thomas de Grenier de Latour 
 
 
 

Summary:
 
 GZip compression of master-slave transfer  should be  optionnal  optional 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [core] (JENKINS-30815) GZip compression of master-slave transfer should be optionnal

2015-10-06 Thread tom...@free.fr (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas de Grenier de Latour created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30815 
 
 
 
  GZip compression of master-slave transfer should be optionnal  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Attachments:
 

 flamegraph-1.svg, flamegraph-2.svg 
 
 
 

Components:
 

 core 
 
 
 

Created:
 

 06/Oct/15 4:32 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Thomas de Grenier de Latour 
 
 
 
 
 
 
 
 
 
 
When artifacts are archived at the end of a build (hudson.tasks.ArtifactArchiver), they get transferred from the slave to the master through a stream of gzipped tar data (jenkins.model.StandardArtifactManager calling hudson.FilePath.copyRecursiveTo). While I understand the intent of the involved compression (using some CPU to reduce bandwidth usage), I think it's not always the right thing to do: 
 

in some (many?) cases, the biggest artifacts are already compressed (.jar/.deb/.rpm/...), and gzipping the stream won't really reduce its length
 

in some cases, bandwidth is much less an issue than CPU (think co-located master and slave VMs on an very loaded host)
 
 

[JIRA] [promoted-builds-plugin] (JENKINS-30814) Send An Email Notification Upon A Failed Promotion Job

2015-10-06 Thread jtsw...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 James Sweet created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30814 
 
 
 
  Send An Email Notification Upon A Failed Promotion Job  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Oleg Nenashev 
 
 
 

Components:
 

 promoted-builds-plugin 
 
 
 

Created:
 

 06/Oct/15 4:22 PM 
 
 
 

Environment:
 

 Jenkins  Promoted Builds Plugin 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 James Sweet 
 
 
 
 
 
 
 
 
 
 
Create a new freestyle job. Check "Promote builds when". Under Actions Choose "Execute Shell" and enter "exit -1" Under Actions Choose "Editable Email Notification". Save the job and run it. 
The job never reaches the "Editable Email Notification" step. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
  

[JIRA] [workflow-plugin] (JENKINS-26126) DSLD and/or GDSL

2015-10-06 Thread rsand...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 rsandell edited a comment on  JENKINS-26126 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: DSLD and/or GDSL  
 
 
 
 
 
 
 
 
 
 I made a workflow script that generates a GDSL file for you. It has some  bugs  issues  and is riddled with bugs, assumptions and guesses. But it's a start to build from maybe ;)https://gist.github.com/rsandell/ea18fa6bf07662a223f5 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [workflow-plugin] (JENKINS-26126) DSLD and/or GDSL

2015-10-06 Thread rsand...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 rsandell commented on  JENKINS-26126 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: DSLD and/or GDSL  
 
 
 
 
 
 
 
 
 
 
I made a workflow script that generates a GDSL file for you. It has some bugs and is riddled with bugs, assumptions and guesses. But it's a start to build from maybe  
https://gist.github.com/rsandell/ea18fa6bf07662a223f5 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [workflow-plugin] (JENKINS-30798) workflow multibranch failed after rebase

2015-10-06 Thread magn...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 magnayn commented on  JENKINS-30798 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: workflow multibranch failed after rebase  
 
 
 
 
 
 
 
 
 
 
Hm. Even more strange behaviour. 
I'd set the 'branches' to be "dev*, release*" - which doesn't work. So I changed it to "dev* release*" - and then when I thought a bit more to just "*". 
Now I have projects building - but I can't access their URL. E.g:  http://jenkins.blah.com/job/rd2/ 
Shows a list of branches. But clicking on one (e.g: dev-main) that's currently building goes to  http://jenkins.blah.com/job/rd2/branch/dev-main/ 
Which results in a 404 Not Found. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [core] (JENKINS-30802) enhance buildable status job operations

2015-10-06 Thread jake.bis...@netdudes.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 jake bishop edited a comment on  JENKINS-30802 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: enhance buildable status job operations  
 
 
 
 
 
 
 
 
 
 This buildable status is also somehow incosistently implemented. See JENKINS-30745. In particular the facts that{quote} After It is possible to manually start  the  build  \[ of an unbuildable  job ] . After the  job has run  \[manually]  the polling still does not work{quote}and{quote}if you restart jenkins. All those previously 'unbuildable' jobs suddenly become magically buildable and start running{quote}and {quote}\[polling copied jobs] used to work but now it does not{quote} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [core] (JENKINS-30745) First poll does not run on copied jobs which aren't yet saved or applied

2015-10-06 Thread jake.bis...@netdudes.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 jake bishop edited a comment on  JENKINS-30745 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: First poll does not run on copied jobs which aren't yet saved or applied  
 
 
 
 
 
 
 
 
 
 What about the cases i mention?{quote}After the  build  job  has run [manually] the polling still does not work{quote}and{quote}if you restart jenkins. All those previously 'unbuildable' jobs suddenly become magically buildable and start running{quote}and also the fact that it used to work but now it does not 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [core] (JENKINS-30745) First poll does not run on copied jobs which aren't yet saved or applied

2015-10-06 Thread jake.bis...@netdudes.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 jake bishop edited a comment on  JENKINS-30745 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: First poll does not run on copied jobs which aren't yet saved or applied  
 
 
 
 
 
 
 
 
 
 Ok... as long as it can still be discussed i will not reopen. (if nobody see this because it is resolved i will have to re-open.). There is definitely a bug here. And the problem is not resolved for me. I have also discovered another problem caused by this:You say the builds are marked 'unbuildable' you just dont see it in the UI. However it is possible to manually start the build. After the  build  job  has run the polling still does not work. *This is inconsistant and is causing serious problems in our workflow! The builds are not running when the git repo is updated *I would say it is not a bug if- the job does not exist until you click the 'save' button- the job is disabled- the job visually says it is 'unbuildable' (and you cannot start the build manually)However this is *not the case*. Therefore (!) BUG (!)Also... if you restart jenkins. All those previously 'unbuildable' jobs suddenly become magically buildable and start running ;) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [core] (JENKINS-30802) enhance buildable status job operations

2015-10-06 Thread jake.bis...@netdudes.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 jake bishop commented on  JENKINS-30802 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: enhance buildable status job operations  
 
 
 
 
 
 
 
 
 
 
This buildable status is also somehow incosistently implemented. See 

JENKINS-30745
. In particular the facts that 
 
After the [unbuildable] build has run [manually] the polling still does not work
 
and 
 
if you restart jenkins. All those previously 'unbuildable' jobs suddenly become magically buildable and start running
 
and  
 
[polling copied jobs] used to work but now it does not
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [core] (JENKINS-30802) enhance buildable status job operations

2015-10-06 Thread jake.bis...@netdudes.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 jake bishop edited a comment on  JENKINS-30802 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: enhance buildable status job operations  
 
 
 
 
 
 
 
 
 
 This buildable status is also somehow incosistently implemented. See JENKINS-30745. In particular the facts that{quote}After the \[unbuildable]  build  job  has run \[manually] the polling still does not work{quote}and{quote}if you restart jenkins. All those previously 'unbuildable' jobs suddenly become magically buildable and start running{quote}and {quote}\[polling copied jobs] used to work but now it does not{quote} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [core] (JENKINS-30745) First poll does not run on copied jobs which aren't yet saved or applied

2015-10-06 Thread gentoo.inte...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kanstantsin Shautsou commented on  JENKINS-30745 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: First poll does not run on copied jobs which aren't yet saved or applied  
 
 
 
 
 
 
 
 
 
 
All this logic is the same for all triggers and test cases, everybody enforce to do roundtrip (open config/save). So this is not a bug but pure designed api that was concentrated on UI (and obviously those who entered such "feature" (obvioulsy why it done) forget to raise it into UI). So this should be an enhancement that i linked to this issue. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [core] (JENKINS-30745) First poll does not run on copied jobs which aren't yet saved or applied

2015-10-06 Thread jake.bis...@netdudes.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 jake bishop commented on  JENKINS-30745 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: First poll does not run on copied jobs which aren't yet saved or applied  
 
 
 
 
 
 
 
 
 
 
Ok... as long as it can still be discussed i will not reopen. (if nobody see this because it is resolved i will have to re-open.).  
There is definitely a bug here. And the problem is not resolved for me. I have also discovered another problem caused by this: 
You say the builds are marked 'unbuildable' you just dont see it in the UI. However it is possible to manually start the build. After the build has run, but polling still does not work. *This is inconsistant and is causing serious problems in our workflow! The builds are not running when the git repo is updated * 
I would say it is not a bug if 
 

the job does not exist until you click the 'save' button
 

the job is disabled
 

the job visually says it is 'unbuildable' (and you cannot start the build manually)
 
 
However this is not the case. Therefore  BUG  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [core] (JENKINS-30745) First poll does not run on copied jobs which aren't yet saved or applied

2015-10-06 Thread jake.bis...@netdudes.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 jake bishop edited a comment on  JENKINS-30745 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: First poll does not run on copied jobs which aren't yet saved or applied  
 
 
 
 
 
 
 
 
 
 What about the cases i mention?{quote}After the build has run [manually] the polling still does not work{quote}and{quote}if you restart jenkins. All those previously 'unbuildable' jobs suddenly become magically buildable and start running{quote}and  als  also  the fact that it used to work but now it does not 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [core] (JENKINS-30745) First poll does not run on copied jobs which aren't yet saved or applied

2015-10-06 Thread jake.bis...@netdudes.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 jake bishop commented on  JENKINS-30745 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: First poll does not run on copied jobs which aren't yet saved or applied  
 
 
 
 
 
 
 
 
 
 
What about the cases i mention 
 
After the build has run [manually] the polling still does not work
 
and 
 
if you restart jenkins. All those previously 'unbuildable' jobs suddenly become magically buildable and start running
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [core] (JENKINS-30745) First poll does not run on copied jobs which aren't yet saved or applied

2015-10-06 Thread jake.bis...@netdudes.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 jake bishop edited a comment on  JENKINS-30745 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: First poll does not run on copied jobs which aren't yet saved or applied  
 
 
 
 
 
 
 
 
 
 What about the cases i mention ? {quote}After the build has run [manually] the polling still does not work{quote}and{quote}if you restart jenkins. All those previously 'unbuildable' jobs suddenly become magically buildable and start running{quote} and als the fact that it used to work but now it does not 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [core] (JENKINS-30745) First poll does not run on copied jobs which aren't yet saved or applied

2015-10-06 Thread gentoo.inte...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kanstantsin Shautsou commented on  JENKINS-30745 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: First poll does not run on copied jobs which aren't yet saved or applied  
 
 
 
 
 
 
 
 
 
 
jake bishop please add this comments to JENKINS-30802 because i fully agree that this is bad and unexpected behaviour. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [cmakebuilder-plugin] (JENKINS-30070) Automatic download and installation of cmake from cmake.org

2015-10-06 Thread geg...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Guillaume Egles reopened an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
I've just tested, the download part now works. Thank you! 
Sadly, there is now another issue with the path for the cmake binary being different on Mac then on Linux. 
For mac, the cmake CLI binary does not sit in the extracted "bin/" directory (like Unix), but in the "CMake.app/Contents/bin/" of the extracted cmake-3.3.2-Darwin-x86_64.tar.gz. 
Here is the relevant part of the log: 
Unpacking http://www.cmake.org/files/v3.3/cmake-3.3.2-Darwin-x86_64.tar.gz to /var/tmp/jenkins/tools/hudson.plugins.cmake.CmakeTool/3.3.2 on osx-10_9 Cleaning build dir... /opt/build/conduit-connect-osx/build [build] $ /var/tmp/jenkins/tools/hudson.plugins.cmake.CmakeTool/3.3.2/bin/cmake -G "Unix Makefiles" -DCMAKE_INSTALL_PREFIX=/opt/build/conduit-connect-osx/install -DOPENSSL_ROOT_DIR=/aspera/build/3rdparty/trunk/mac-intel-10.9/stable/latest/build/result/BUILD/mac-10.7-64-release/openssl-1.0.1p -DCMAKE_PREFIX_PATH=/opt/build/webrtc-osx/install -DCMAKE_BUILD_TYPE=Release /opt/build/conduit-connect-osx ERROR: Cannot run program "/var/tmp/jenkins/tools/hudson.plugins.cmake.CmakeTool/3.3.2/bin/cmake" (in directory "/opt/build/conduit-connect-osx/build"): error=2, No such file or directory Build step 'CMake Build' marked build as failure Archiving artifacts Finished: FAILURE 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-30070 
 
 
 
  Automatic download and installation of cmake from cmake.org  
 
 
 
 
 
 
 
 
 

Change By:
 
 Guillaume Egles 
 
 
 

Resolution:
 
 Fixed 
 
 
 

Status:
 
 Closed Reopened 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

  

[JIRA] [core] (JENKINS-30745) First poll does not run on copied jobs which aren't yet saved or applied

2015-10-06 Thread jake.bis...@netdudes.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 jake bishop edited a comment on  JENKINS-30745 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: First poll does not run on copied jobs which aren't yet saved or applied  
 
 
 
 
 
 
 
 
 
 Ok... as long as it can still be discussed i will not reopen. (if nobody see this because it is resolved i will have to re-open.). There is definitely a bug here. And the problem is not resolved for me. I have also discovered another problem caused by this:You say the builds are marked 'unbuildable' you just dont see it in the UI. However it is possible to manually start the build. After the build has run , but  the  polling still does not work. *This is inconsistant and is causing serious problems in our workflow! The builds are not running when the git repo is updated *I would say it is not a bug if- the job does not exist until you click the 'save' button- the job is disabled- the job visually says it is 'unbuildable' (and you cannot start the build manually)However this is *not the case*. Therefore (!) BUG (!)Also... if you restart jenkins. All those previously 'unbuildable' jobs suddenly become magically buildable and start running ;) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [core] (JENKINS-30745) First poll does not run on copied jobs which aren't yet saved or applied

2015-10-06 Thread jake.bis...@netdudes.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 jake bishop edited a comment on  JENKINS-30745 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: First poll does not run on copied jobs which aren't yet saved or applied  
 
 
 
 
 
 
 
 
 
 Ok... as long as it can still be discussed i will not reopen. (if nobody see this because it is resolved i will have to re-open.). There is definitely a bug here. And the problem is not resolved for me. I have also discovered another problem caused by this:You say the builds are marked 'unbuildable' you just dont see it in the UI. However it is possible to manually start the build. After the build has run, but polling still does not work. *This is inconsistant and is causing serious problems in our workflow! The builds are not running when the git repo is updated *I would say it is not a bug if- the job does not exist until you click the 'save' button- the job is disabled- the job visually says it is 'unbuildable' (and you cannot start the build manually)However this is *not the case*. Therefore (!) BUG (!) Also... if you restart jenkins. All those previously 'unbuildable' jobs suddenly become magically buildable and start running ;) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [envinject-plugin] (JENKINS-18714) SVN_URL and SVN_REVISION environment variables are missing when repository url contains a variable

2015-10-06 Thread slawo...@ezono.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Slawomir Czarko commented on  JENKINS-18714 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: SVN_URL and SVN_REVISION environment variables are missing when repository url contains a variable  
 
 
 
 
 
 
 
 
 
 
Still happens with Subversion Plugin 2.5.3 and EnvInject Plugin 1.92.1 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [build-pipeline-plugin] (JENKINS-30813) Build pipeline plugin view display no job boxes at all

2015-10-06 Thread martin.danjo...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Martin d'Anjou created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30813 
 
 
 
  Build pipeline plugin view display no job boxes at all  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Attachments:
 

 BuildPipelineCorruptedView.png 
 
 
 

Components:
 

 build-pipeline-plugin 
 
 
 

Created:
 

 06/Oct/15 2:50 PM 
 
 
 

Environment:
 

 Jenkins LTS 1.609.3  Build Pipeline 1.4.8  jQuery 1.11.2-0  Firefox 38.3.0 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Martin d'Anjou 
 
 
 
 
 
 
 
 
 
 
I have attached a picture of the problem. The job boxes are missing all together, but the arrows between them are there. I do not know how it got to that point. When I create a build pipeline on a different instance of Jenkins, it displays the job boxes. On the problematic jenkins instance, all the pipelines look desperately empty, as in the attached picture. 
 
 
 
 
 
 
 
 
   

[JIRA] [logfilesizechecker-plugin] (JENKINS-30797) Activate the plugin at Jenkins Global level (not per job)

2015-10-06 Thread stefan.brau...@1und1.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Stefan Brausch commented on  JENKINS-30797 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Activate the plugin at Jenkins Global level (not per job)  
 
 
 
 
 
 
 
 
 
 
Thanks for your request. I see no option for a global activation of this check. But maybe you could use the configuration slicing plugin to configure a group of jobs easily.  https://wiki.jenkins-ci.org/display/JENKINS/Configuration+Slicing+Plugin 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [github-plugin] (JENKINS-17240) GitHub Web Hook API Key configuration is not documented

2015-10-06 Thread gentoo.inte...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kanstantsin Shautsou resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Documentation and help files enhanced. Thanks to Kirill Merkushev 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-17240 
 
 
 
  GitHub Web Hook API Key configuration is not documented  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kanstantsin Shautsou 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Fixed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [github-plugin] (JENKINS-24690) Report failures to attach hook in UI

2015-10-06 Thread gentoo.inte...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kanstantsin Shautsou commented on  JENKINS-24690 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Report failures to attach hook in UI  
 
 
 
 
 
 
 
 
 
 
Such problem with UI indication exists for all plugins.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [github-plugin] (JENKINS-18079) GitHub Push always builds if workspace is on offline slave node

2015-10-06 Thread gentoo.inte...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kanstantsin Shautsou commented on  JENKINS-18079 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: GitHub Push always builds if workspace is on offline slave node  
 
 
 
 
 
 
 
 
 
 
But first of all it's git-plugin issue. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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.


Urgent need for Senior Selenium Tester for Cincinnati OH location

2015-10-06 Thread andr...@virattechnologiesinc.com
Good Morning –

Do you have any Selenium Tester’s available for long term
contracts?



*Senior Selenium Tester*

*Cincinnati OH*

*Duration: 12mos+*

*Hire Method: Phone / Skype*

*Rate: $50/hr*



· *Selenium*

· *Risk Based Testing*

· *3+ years of experience writing and maintaining scripts in
Selenium WebDriver, using Java and modular frameworks (TestNG)*



*Requirements:*

   - 8+ years of relevant experience in software quality assurance
   - Preferred experience with testing e-commerce web sites
   - 3+ years of experience writing and maintaining scripts in Selenium
   WebDriver, using Java and modular frameworks (TestNG)
   - Prior experience in Agile software development methodology (SAFe
   approach preferred)
   - Strong understanding of test case creation and execution concepts and
   best practices
   - Prior experience testing system integrations/data flows
   - Strong troubleshooting skills
   - Able to discern between issues in the front end application as well as
   downstream systems
   - Prior experience using Quality Center for test case management
   - Prior experience using Jira for defect tracking
   - Good understanding of regression testing concepts and best practices


*Thanks,*Andrews
___
*Andrews Race*| Professional Recruiter
*Virat* *Technologies,*
*Inc.*IT STAFFING & CONSULTING

andr...@virattechnologiesinc.com
17205 Rookery ct, Princeton Junction, NJ
08550
*(**: *732.414.8578
* Direct*Please consider the environment and do not print this email unless
absolutely necessary. Save Earth
This message is intended for recruiting and consulting professionals only
and is not intended as a solicitation.  If you received this email in error
and/or you wish to be removed from our list for any reason, please REPLY
with REMOVE in the subject

-- 
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] [docker-custom-build-environment-plugin] (JENKINS-30692) Can't use the default command from an image

2015-10-06 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-30692 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Can't use the default command from an image  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Daniel Spilker Path: src/main/java/com/cloudbees/jenkins/plugins/docker_build_env/DockerBuildWrapper.java http://jenkins-ci.org/commit/docker-custom-build-environment-plugin/03a153e94915945a80da295965e4f06ca2806c9e Log: do not append command if not set 
[FIXES JENKINS-30692] 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [docker-custom-build-environment-plugin] (JENKINS-30692) Can't use the default command from an image

2015-10-06 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30692 
 
 
 
  Can't use the default command from an image  
 
 
 
 
 
 
 
 
 

Change By:
 
 SCM/JIRA link daemon 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Fixed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [github-plugin] (JENKINS-26886) Variables not being substituted in github URLs for $JOB_NAME

2015-10-06 Thread gentoo.inte...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kanstantsin Shautsou commented on  JENKINS-26886 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Variables not being substituted in github URLs for $JOB_NAME  
 
 
 
 
 
 
 
 
 
 
Have you tried 

 

 ${JOB_NAME} 
 

 
? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [docker-custom-build-environment-plugin] (JENKINS-30692) Can't use the default command from an image

2015-10-06 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-30692 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Can't use the default command from an image  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Nicolas De loof Path: src/main/java/com/cloudbees/jenkins/plugins/docker_build_env/DockerBuildWrapper.java http://jenkins-ci.org/commit/docker-custom-build-environment-plugin/c3c2b667fcace7f3a0902432dac4b151296d9123 Log: Merge pull request #33 from daspilker/

JENKINS-30692
 


JENKINS-30692
 do not append command if not set 
Compare: https://github.com/jenkinsci/docker-custom-build-environment-plugin/compare/102768ae51f3...c3c2b667fcac 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [github-plugin] (JENKINS-27692) Webhooks do not work if using parameter in git address

2015-10-06 Thread gentoo.inte...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kanstantsin Shautsou commented on  JENKINS-27692 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Webhooks do not work if using parameter in git address  
 
 
 
 
 
 
 
 
 
 
Not all variables are available for expansion. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [github-plugin] (JENKINS-27692) Webhooks do not work if using parameter in git address

2015-10-06 Thread gentoo.inte...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kanstantsin Shautsou commented on  JENKINS-27692 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Webhooks do not work if using parameter in git address  
 
 
 
 
 
 
 
 
 
 
Ah, found related issue JENKINS-26886 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [core] (JENKINS-26657) File context menu missing when installing Slave under windows with jnlp

2015-10-06 Thread sebastien.bon...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sebastien Bonami commented on  JENKINS-26657 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: File context menu missing when installing Slave under windows with jnlp  
 
 
 
 
 
 
 
 
 
 
Thanks vlad guan. I followed this guide and it looks good: https://wiki.jenkins-ci.org/display/JENKINS/Launch+Java+Web+Start+slave+agent+via+Windows+Scheduler 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [github-plugin] (JENKINS-27154) Make the github-plugin commit status configurable instead of tied to the project name

2015-10-06 Thread gentoo.inte...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kanstantsin Shautsou commented on  JENKINS-27154 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Make the github-plugin commit status configurable instead of tied to the project name  
 
 
 
 
 
 
 
 
 
 
I think universal message calculation/ui configuration can be migrated from github-pullrequest-plugin, but default values for this Describables under question. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [ec2-plugin] (JENKINS-14110) plugin download: http://updates.jenkins-ci.org/latest/github.hpi *not found* resulting in failed chef runs.

2015-10-06 Thread gentoo.inte...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kanstantsin Shautsou closed an issue as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-14110 
 
 
 
  plugin download: http://updates.jenkins-ci.org/latest/github.hpi *not found* resulting in failed chef runs.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kanstantsin Shautsou 
 
 
 

Status:
 
 Resolved Closed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [github-plugin] (JENKINS-30811) Issue with configuring global security/Grant READ permissions for /github-webhook

2015-10-06 Thread gentoo.inte...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kanstantsin Shautsou reopened an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Don't remember such options. Reassigned to Kirill Merkushev  
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-30811 
 
 
 
  Issue with configuring global security/Grant READ permissions for /github-webhook  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kanstantsin Shautsou 
 
 
 

Resolution:
 
 Not A Defect 
 
 
 

Status:
 
 Resolved Reopened 
 
 
 

Assignee:
 
 Kanstantsin Shautsou Kirill Merkushev 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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 

[JIRA] [github-plugin] (JENKINS-30811) Issue with configuring global security/Grant READ permissions for /github-webhook

2015-10-06 Thread gentoo.inte...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kanstantsin Shautsou updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30811 
 
 
 
  Issue with configuring global security/Grant READ permissions for /github-webhook  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kanstantsin Shautsou 
 
 
 

Priority:
 
 Blocker Minor 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [github-plugin] (JENKINS-27154) Make the github-plugin commit status configurable instead of tied to the project name

2015-10-06 Thread lan...@yandex.ru (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kirill Merkushev commented on  JENKINS-27154 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Make the github-plugin commit status configurable instead of tied to the project name  
 
 
 
 
 
 
 
 
 
 
Good point. Will think about it next 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [github-plugin] (JENKINS-30811) Issue with configuring global security/Grant READ permissions for /github-webhook

2015-10-06 Thread ilhomdjala...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ilhom Djalalov commented on  JENKINS-30811 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Issue with configuring global security/Grant READ permissions for /github-webhook  
 
 
 
 
 
 
 
 
 
 
As I've mentioned, Step 3, it reads as following: 
Step 3. Open "Manage Jenkins > Configure Global Security" page and make sure that "Grant READ permissions for /github-webhook" is enabled in the "GitHub Authorization Settings" section. (If you are using the latest version of the plugin, you may not see the Github option on "Configure Global Security" page. Just go to the project configure page, in section "Build Triggers", check "Build when a change is pushed to GitHub") 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [github-plugin] (JENKINS-27041) Thousands of threads created by thousands of GitHub pushes

2015-10-06 Thread gentoo.inte...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kanstantsin Shautsou commented on  JENKINS-27041 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Thousands of threads created by thousands of GitHub pushes  
 
 
 
 
 
 
 
 
 
 
Is it still actual? We have in TODO change polling algo that will be lighter. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [github-plugin] (JENKINS-28238) Github Plugin Failing to re-register for hooks

2015-10-06 Thread gentoo.inte...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kanstantsin Shautsou updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-28238 
 
 
 
  Github Plugin Failing to re-register for hooks  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kanstantsin Shautsou 
 
 
 
 
 
 
 
 
 
  I'm trying to have Jenkins automatically manage github webhooks.My automated jenkins user has a github oauth token with "repo" and "repo:status"  permissions that its using. I click on "re-register hooks for all jobs" and this is the output from the jenkins log: {code} May 05, 2015 11:15:48 AM com.cloudbees.jenkins.GitHubPushTrigger$2 runWARNING: Failed to add GitHub webhook for GitHubRepository[host=github.com,username=DemandCube,repository=NeverwinterDP]org.kohsuke.github.GHException: Failed to update jenkins hooks at com.cloudbees.jenkins.GitHubPushTrigger.createJenkinsHook(GitHubPushTrigger.java:182) at com.cloudbees.jenkins.GitHubPushTrigger.access$700(GitHubPushTrigger.java:55) at com.cloudbees.jenkins.GitHubPushTrigger$2.run(GitHubPushTrigger.java:165) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744)Caused by: java.io.FileNotFoundException: {"message":"Not Found","documentation_url":"https://developer.github.com/v3"} at org.kohsuke.github.Requester.handleApiError(Requester.java:494) at org.kohsuke.github.Requester._to(Requester.java:245) at org.kohsuke.github.Requester.to(Requester.java:191) at org.kohsuke.github.GHRepository.createHook(GHRepository.java:880) at com.cloudbees.jenkins.GitHubPushTrigger.createJenkinsHook(GitHubPushTrigger.java:179) ... 9 moreCaused by: java.io.FileNotFoundException: https://api.github.com/repos/DemandCube/NeverwinterDP/hooks at sun.reflect.GeneratedConstructorAccessor135.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:526) at sun.net.www.protocol.http.HttpURLConnection$6.run(HttpURLConnection.java:1675) at sun.net.www.protocol.http.HttpURLConnection$6.run(HttpURLConnection.java:1673) at java.security.AccessController.doPrivileged(Native Method) at sun.net.www.protocol.http.HttpURLConnection.getChainedException(HttpURLConnection.java:1671) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1244) at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:254) at org.kohsuke.github.Requester.parse(Requester.java:451) at org.kohsuke.github.Requester._to(Requester.java:224) ... 12 moreCaused by: java.io.FileNotFoundException: https://api.github.com/repos/DemandCube/NeverwinterDP/hooks at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1624) at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:468) at sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:338) at org.kohsuke.github.Request

[JIRA] [github-plugin] (JENKINS-28238) Github Plugin Failing to re-register for hooks

2015-10-06 Thread gentoo.inte...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kanstantsin Shautsou resolved as Incomplete 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
No replies, closing. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-28238 
 
 
 
  Github Plugin Failing to re-register for hooks  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kanstantsin Shautsou 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Incomplete 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [github-plugin] (JENKINS-28320) GitHub plugins store access tokens in config files as plain text

2015-10-06 Thread gentoo.inte...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kanstantsin Shautsou resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
starting from some version gh plugin uses credentials 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-28320 
 
 
 
  GitHub plugins store access tokens in config files as plain text  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kanstantsin Shautsou 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Fixed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [github-plugin] (JENKINS-22456) github plugin too many open files unclosed github-polling.log filehandles causes all builds to fail

2015-10-06 Thread gentoo.inte...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kanstantsin Shautsou resolved as Cannot Reproduce 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-22456 
 
 
 
  github plugin too many open files unclosed github-polling.log filehandles causes all builds to fail  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kanstantsin Shautsou 
 
 
 

Status:
 
 Reopened Resolved 
 
 
 

Resolution:
 
 Cannot Reproduce 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [github-plugin] (JENKINS-24122) github service being removed when saving on the "configure jenkins" page

2015-10-06 Thread gentoo.inte...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kanstantsin Shautsou resolved as Incomplete 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-24122 
 
 
 
  github service being removed when saving on the "configure jenkins" page  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kanstantsin Shautsou 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Incomplete 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [github-plugin] (JENKINS-26202) Can't save project configurations

2015-10-06 Thread gentoo.inte...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kanstantsin Shautsou updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-26202 
 
 
 
  Can't save project configurations  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kanstantsin Shautsou 
 
 
 
 
 
 
 
 
 
 After upgrading Jenkins to the latest versions, I can no longer save project configurations. {code} An error page with the following exception is show:javax.servlet.ServletException: java.lang.AssertionError: class com.cloudbees.jenkins.GitHubPushTrigger is missing its descriptor at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) 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 jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93) 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.d

[JIRA] [github-plugin] (JENKINS-26202) Can't save project configurations

2015-10-06 Thread gentoo.inte...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kanstantsin Shautsou resolved as Incomplete 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Too old, no replies. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-26202 
 
 
 
  Can't save project configurations  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kanstantsin Shautsou 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Incomplete 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [github-plugin] (JENKINS-27692) Webhooks do not work if using parameter in git address

2015-10-06 Thread gentoo.inte...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kanstantsin Shautsou resolved as Not A Defect 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Project url must be static, this is PROJECT configuration and it has no variables. Variables appears only during build. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-27692 
 
 
 
  Webhooks do not work if using parameter in git address  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kanstantsin Shautsou 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Not A Defect 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [github-plugin] (JENKINS-28898) Updating to GitHub plugin 1.11.3 causes Cannot get property 'extensions' on null object

2015-10-06 Thread gentoo.inte...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kanstantsin Shautsou resolved as Incomplete 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-28898 
 
 
 
  Updating to GitHub plugin 1.11.3 causes Cannot get property 'extensions' on null object   
 
 
 
 
 
 
 
 
 

Change By:
 
 Kanstantsin Shautsou 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Incomplete 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [pretested-integration-plugin] (JENKINS-30603) Re-use commit message if the changeset only contains one commit (Praqma case 13636)

2015-10-06 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-30603 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Re-use commit message if the changeset only contains one commit (Praqma case 13636)  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Mads Nielsen Path: pom.xml http://jenkins-ci.org/commit/pretested-integration-plugin/49616c8aa75f82213811531decbb64d7819efef3 Log: JENKINS-30603 Updated JavaNCSS for Multicatch in Java 1.7 
Compare: https://github.com/jenkinsci/pretested-integration-plugin/compare/e93ad80e393c...49616c8aa75f 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [pretested-integration-plugin] (JENKINS-30603) Re-use commit message if the changeset only contains one commit (Praqma case 13636)

2015-10-06 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-30603 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Re-use commit message if the changeset only contains one commit (Praqma case 13636)  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Thierry Lacour Path: src/main/java/org/jenkinsci/plugins/pretestedintegration/scm/git/GetCommitCountFromBranchCallback.java src/main/java/org/jenkinsci/plugins/pretestedintegration/scm/git/GitBridge.java src/main/java/org/jenkinsci/plugins/pretestedintegration/scm/git/SquashCommitStrategy.java src/test/java/org/jenkinsci/plugins/pretestedintegration/integration/scm/git/GetCommitCountFromBranchCallbackIT.java src/test/java/org/jenkinsci/plugins/pretestedintegration/integration/scm/git/SquashCommitStrategyIT.java src/test/java/org/jenkinsci/plugins/pretestedintegration/integration/scm/git/TestCommit.java src/test/java/org/jenkinsci/plugins/pretestedintegration/integration/scm/git/TestUtilsFactory.java src/test/java/org/jenkinsci/plugins/pretestedintegration/integration/scm/git/UniqueBranchGenerator.java http://jenkins-ci.org/commit/pretested-integration-plugin/9b6d14d13a44b848c756e5157fba4f3743b1b3fe Log: JENKINS-30603 Squash strategy now respects single commit messages. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [github-plugin] (JENKINS-21172) Github Plugin triggers duplicate builds

2015-10-06 Thread gentoo.inte...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kanstantsin Shautsou resolved as Incomplete 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-21172 
 
 
 
  Github Plugin triggers duplicate builds  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kanstantsin Shautsou 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Incomplete 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [core] (JENKINS-30807) SecretWriter.recursionDetection Test Failing

2015-10-06 Thread justin.feh...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Justin Fehr updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30807 
 
 
 
  SecretWriter.recursionDetection Test Failing  
 
 
 
 
 
 
 
 
 

Change By:
 
 Justin Fehr 
 
 
 

Priority:
 
 Minor Critical 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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   >